+6
Qualified

Ability to make an attachment field required based on a form field picklist selection

Greg Milosovic 8 months ago in System Administration updated by Rob Tuffly 3 months ago 5

Attachment field should have the ability to become required dynamically based on a form field picklist selection. 


E.g., I ask a requester via a single select picklist form field to tell me if an email they want to send to customers already exists. They have 2 options:

1.) No, but a zip file is attached

2.) Yes, it has been created in marketing automation platform


If the user selects #1 above, then the attachment field at the bottom of the form should become required. If they select #2, then the attachment field is either optional or, ideally, it would disappear. 

Attachments Configuration

Anthem Medicare as a similar ask. We need the ability to append an extra 4-digit code to the main material ID code for select workflows. If a select workflow was chosen, this EA -- which exists on the HTML 5 New Attachment Screen -- would become required for uploading any document.

Qualified

I understand the business use case but the configuration for this could be complicated to configure and validate.  Your example actually would want to force a document upload to be required based on a field value selection.  Would be interested in hearing from more customers on this.

Understood. Will you be reaching out to other customers for feedback or are they expected to proactively find this request and comment?

It is a bit of both.  As I see ideas like this when talking with customers I will solicit feedback from them but also will look to see what other feedback or comments are made on this thread in Voice as well. 

We requested a similar enhancement for attachments: https://voice.aprimo.com/communities/42/topics/1181-dynamic-attachment-type-display. Any ability to dynamically show/restrict attachment types being displayed in a task will help us to clean up the Task Inbox for our users. Currently using a shared WF for multiple groups/channels results in a large number of unneeded attachment type upload options in each Task.