Different profiles for different service categories

[HHH]

We are trying to enforce setting categories to each request when they are raised but we cannot use the Suspend awaiting category node since the various services are set to start in the middle of the "tree" and thus the system thinks that category has already been set.

guest.servicemanager.request.category.request.enforceLastItem has been set to true but that doesn't help.
Is there a way around this? Can for example totally different profiles be used for different services?

[HHH]

Bump

[Steve Giller]

On 24/04/2024 at 13:25, HHH said:

we cannot use the Suspend awaiting category node since the various services are set to start in the middle of the "tree" and thus the system thinks that category has already been set.

The "Suspend->Wait for Request Category" node waits for a category to be assigned.
If the Category is filtered this does not automatically apply a category, so if the "Suspend->Wait for Request Category" node is not suspending the workflow a Category has been explicitly set.

Some ways around this would be to not set a Category prior to this node, to clear the category before the Suspend node (forcing a new one to be selected), or to have a Human Task to remind the Owner to check that a suitable Category has been set.

[HHH]

Thanks @Steve Giller what I did after looking at your workarounds was to add a lock resolution node before the assign category and unlock resolve directly after, thus enforcing category before resolution