Workflow: RoundRobin can assign to inactive users

[alasdaircr]

Hello,

If a User is not 'Is Active' they shouldn't be assigned an entity as a result of a RoundRobin process.

[yuri]

Hi,

Will be fixed. Thank you.

[alasdaircr]

Hi Yuri - another thing I noticed is that when a workflow assignment is triggered after creating an entity - two notes are created once assigning to null and then assigning to the user:




Ideally the note hook would run after 'Create' workflows have been processed.

[alasdaircr]

Hi Yuri - another thing I noticed is that when a workflow assignment is triggered after creating an entity - two notes are created once assigning to null and then assigning to the user:




Ideally the note hook would run after 'Create' workflows have been processed.

Not sure if you saw this yuri ? Is it better to use cases for this sort of bug in an extension, post in the Extensions forum, or in the Bug Reports forum? Because ideally we would have a grasp of it being acknowledged and when we could expect a fix.

[yuri]

This will be fixed soon. Maybe today.

Extension forum is fine for reporting.

[alasdaircr]

Amazing!