Workflow start form - dynamic asset type and user group filter
Summary: laurenzhiller1 asked two questions regarding workflow development in Workflow Designer. Firstly, they inquired about dynamically passing asset type filters to an asset data entry field in a start form using a configuration variable, without the use of a script task beforehand. Secondly, they wanted to know if it's possible to restrict a user data entry field in a start form to users belonging to a certain group, preferably by dynamically passing the resource ID of the group to the filter. SeanPyle responded by suggesting that for the first question, one could use a call activity to pass variables, though this may affect the form display timing. For the second question, they proposed using conditional logic to dynamically show or hide fields based on configuration properties, although they noted this was a speculative suggestion.
Hi guys,
I have two questions regarding workflow development in Workflwo Designer.
- Is it possible to dynamically pass asset type filters (UUID of the relevant asset type(s)) to an asset data entry field in a start form, e.g. from a configuration variable? Please note that I am talking about a start form and therefore have no option to use a script task beforehand.
- Can I restrict an user data entry field in a start form to users who belong to a certain group? I don't see any way to specify a group filter. Ideally, I would like to dynamically pass the resource ID of the group to the filter from a configuration variable.
Thanks for your help!
Sean Pyle
·1 year agoHey Laurenz,
Hope you are well! As for #1, you might be able to do this by calling the workflow in question from a call activity. Then you could pass the variable from the call activity to your configuration variables in the workflow you need the asset type filters. However, I think you'll lose the option to have the form associated with the start event to automatically pop up when the second workflow starts.
For #2, instead of restricting the field, you may be able to write conditional logic that makes it visible or hidden based on a boolean variable from your configuration properties. (just thinking extemporaneously here though).