having that only specific to a certain task may not be easy. A couple of thoughts from my end:
1. You could perhaps create a custom flex UI for that task and in there only list the relevant fields that need to be updated.
2. Finishing an object in such a task step could trigger a set of DQ rules that check specifically for the relevant fields whether a value has been set. In case not BPM could send the object back into the original task
Thank you for the information.
At this moment I have created the workflow into ActiveVos Designer, created a custom flexUI that includes the needed fields that must e completed, I have DQ rules for each usergroup and is working.
My question is now, can I develop this flow in another way in order not to use the DQ rules anymore?
I will have into the workflow 5 different usergroups with different DQrules. I do not know how will be the performance after creating the 5 different usergroups into different Loop.
The only alternative to DQ is setting the field globally mandatory in the repository which I think is not what you want to do here.
I do not know the exact data and user load you expect but to some extend I think your current solution should be fine then.
Do you know if I can make the fields mandatory, somehow in the UITemplate that I use for the FlexUI items for that specific task/loop from the workflow?
Not that I would be aware of it, sorry.