Changing a catalog varible to "required" using Flow Designer

[Joe Trimble]

Is there a way, using Flow Designer, to change a catalog variable's 'Required' flag?

I have some catalog variables that are not required or wanted from the user making a request, but that need to be set by the assigned ITIL user during the fulfillment process.  They need to fill in date fields indicating when borrowed equipment is loaned out, due back, and then actually returned to the service desk.  These fields mean nothing to the user requesting to borrow equipment but are needed by those processing the request.  I'd like to be able to set the 'Required' flag to true in the Flow.  Any way to do this?

Thanks!

[Jerick I]

@Joe Trimble I don't think you'll be able to accomplish this using the flow designer; instead, I'd recommend using a business rule to verify the information before the user closes the task and display an error message requesting that they fill up the missing field. You can even dotwalk the field using a parent field.

Regards,

Jeff

Hope this helps. Please mark the answer as correct/helpful based on impact.

[Joe Trimble]

Thanks, Jeff.

So, would this be a Business Rule (server side) OR would it be done as a UI Policy (client side)?  We have UI policies that require an assignee is designated before closing the task, for instance, so this seems like the right direction.  Can I use a UI policy and enforce it based on catalog variables?

We're relatively new at SN so I really appreciate the feedback!

Joe

[Jerick I]

@Joe Trimble As far as I can recall, you cannot dot walk the variable on the ui policy condition; you can try to create a business rules, which check the field value before triggering and deciding whether to accept or abort an action if the task is closed. See also the basic business rule below on how to execute this on sc task.  

[Joe Trimble · Accepted solution]

Thanks, @Jerick I, for your notes.   The final solution is a variation of your suggestion. Rather than using "current.parent.variables.my_variable" I took out the "parent" part and used "current.variables.my_variable" to read the variables on the form before they are saved to the database.