[concept] Concept for User Task Management

[xdoo]

High Level Architecture view

This is our architecture goal:

Picture for the PoC setup:

• Sync between Camunda and task service
• Message transport via Event Bus (so we can use the task service in a transactional manner from any service)
• Task Management inside Task Service

Requirements for the task service

• ... What are the requirements for the task service to get a "as is" functionality?

@dominikhorn93 can you please provide here a bullet list with all requirements, that we need?

Current state:

• Assign tasks to one individual users
• Assign tasks to a group of users
• Assign tasks to a group of user-groups
• Schedule a task for a specific date
• Task-Level Variables (Description, Name, Created At)
• Restrict the view to certain data that are present in the json schema
• Restrict the writing of data to the definition in the json schema
• Load tasks that are processed in a process instance
• Load tasks that are currently open in a process instance

Current requirements:

• assign tasks in a group
• Move tasks between groups
• Filter by individual task data
• ...

Questions for the taskana guys

• ...

[xdoo]

@dominikhorn93

• Move tasks between groups
• Filter by individual task data

Where can we do these 2 things? Do we need a kind of admin gui here?

[dominikhorn93]

@xdoo I think of a specific inbox authoriztation: User is allowed to reassign tasks in / for a specific group or inbox

[xdoo]

@a-m-zill do you have a new state?