How to Assign a Task to the CREATOR in CaseMap

shizuka-hashida

Hello everyone in the community.
I'd like to ask about the Lending application that uses the CaseMap feature provided in the Workflow Demos and portal-user-examples.

In the current implementation, all tasks are assigned either to the System user or to Everybody.

For example, if I want to generate a task for the CREATOR to confirm that the contract has been finalized, how should I configure this?

In Task Events and User Task activities, the Task tab clearly provides a Responsible field.
However, I cannot find the Responsible field in the Task tab of the Start event.

I noticed that when I set a timeout in the Expiry tab, a Responsible field appears, but tasks are not actually assigned to the role configured there.

Could you please advise me on how to achieve this?

Thank you very much.

Jens Hartmann

Hi @shizuka-hashida

You have to set the responsible role in the register Request > Permission (on a Startevent).
In your screenshot, you are in the expiry tab, this means that this start-task is forwarded to this role after an expiry condition has been met. This role therefore only becomes responsible once the expiry condition has been met.

Take a look here:

shizuka-hashida

Thank you very much for your reply.
As you pointed out, I tried to select CREATOR from the Permission section in the Request tab, but only roles were available as options.

For example, if I modify the Lending app and add a new “Confirm Contract Completion” task, I believe it should be assigned not to a role, but specifically to the CREATOR.
How can I assign a task directly to the CREATOR?

I also noticed that the "Check Company Register" task, which is assigned to the System user, has its Responsible defined in the Trigger tab of the Start event.

Is this the correct place to configure the Responsible user?

Lukas Lieb

The request permission is to define which user can start a process. Defining the CREATOR here would not make any sense, as in a normal process, the CREATOR is not defined at the start.
The trigger case is different, as this means that the process is triggered by another process. So here the CREATOR is clear and can be chosen as responsible.

In the case of the casemap the trigger definition is used to define the task. So if you choose here the CREATOR and run the casemap the next task should have the user of the first task as responsible.

shizuka-hashida

Thank you very much!
For CaseMap, I will configure it in the Trigger tab.