AnsweredAssumed Answered

Multi-Valued Attribute - Force Requirement

Question asked by AndreaMcVey on Aug 16, 2010
Latest reply on Aug 18, 2010 by Chris_Hackett
I have a custom object that has a multi-valued attribute called 'Impacted Applications'.
The look-up uses a dynamic query to pull all the applications we have entered in the application.

Clarity does not allow us to make this attribute a required field at the Object level.

I am trying to build a process which sends an Action Item to the creator if they leave this field blank.
But the process step is demanding a constant.
Obviously that isn't feasible since the list is constantly in flux.
We can't be updating the constant list in the process everytime there is a new application added in Clarity.

This is the only solution I can come up with...
Create a 'secret' field for Apps and another that is just a Boolean.
Use a gel script to populate the field with all values for Impacted Applications, concatenated together.
Use another to check off the Boolean field if there is something in Apps field.
Use the boolean as the step post-condition.

Anything simpler??
Thanks,
Andrea

Outcomes