IdStory Identity Manager

Role request (concepts) canceling is already implemented. Problem is in the canceling connected WF processes (those are not cancel now).

I understand, but there is a scenario that would not be work.

The request may exist without any concepts. Likewise, an extreme case may cause a user to ask for a role (creates a concept), and ask the other role by description in the request (he does not know witch exactly want). If the whole request will be terminated after the first role will be deleted, then a user's secound request (note in request) could not be satisfied.

Perhaps this is an extreme case. I can add a quit request if the last concept is canceled, but I'm not sure with this.

Good point! I didn't think about this use-case, but it's definitely a valid situation (especially when we have "Helpdesk" or "Managers of users" approval rounds enabled, who can add additional roles to the request).

• Helpdesk, User's manager, Managers of users approval round - cancel the role from the request, but do nothing else to the approval task (it stays open, can be accepted or rejected, additional roles can be added to other contracts)
• Roles criticality subprocess - cancel the subprocess with the deleted contract/role. Continue with the parent process as if the subprocess was denied.
• Security - cancel the role from the request, but do nothing else to the approval task

But I don't know how complex would the implementation be :(

You discovered big issue, where canceled subprocess does not triggered the parent process. This is big problem ... I spent many hours with search the solution ... but without success.I created new task for this #1115.