Details
-
New Feature
-
Resolution: Unresolved
-
None
-
None
-
High
-
Introduction of a in workflow triggerable action to create additional jobs for tasks.
-
Empty show more show less
Description
problem
For specific workflow scenarios the task defaults are not sufficient to create all needed jobs on task creation.
Therefore a workflow action autocreateJobs should be added which can then be configured on the trigger handleAfterImport. When adding that to the workflow action table, the entry must be positioned before or after the already existing notifyAllAssociatedUsers on the same trigger. Just depending on the needs (with our without notification mails to the new jobs).
As configurable parameters the following structure should be used in the workflow action parameters field:
{ "steps":[{ "step": "WorkflowStepName", //Must be a valid value of the LEK_workflow_step table entries matching the workflow "state": "open", // a valid job state (open / waiting / finished / unconfirmed) "deadlineDate": "strtotime parsable string", //used as deadline Date then "user": { "type": "login", "login": "loginname" }, "user": { "type": "taskPm" }, "user": { //adds all users of the previous workflow step with given name "type": "previousWorkflowStep", "workflowStep": "translation" } }]}
Attention: This implies that the PM is always assigned to the task in the workflow, which implies that the PM will always get the task readonly on opening since mostly the workflow step for the PM is in status waiting. This is by purpose.
Attachments
Issue Links
- mentioned in
-
Page No Confluence page found with the given URL.
Activity
Workflow action to create Workflow Jobs
Details
-
New Feature
-
Resolution: Unresolved
-
None
-
None
-
High
-
Introduction of a in workflow triggerable action to create additional jobs for tasks.
-
Empty show more show less
Description
problem
For specific workflow scenarios the task defaults are not sufficient to create all needed jobs on task creation.
Therefore a workflow action autocreateJobs should be added which can then be configured on the trigger handleAfterImport. When adding that to the workflow action table, the entry must be positioned before or after the already existing notifyAllAssociatedUsers on the same trigger. Just depending on the needs (with our without notification mails to the new jobs).
As configurable parameters the following structure should be used in the workflow action parameters field:
{ "steps":[{ "step": "WorkflowStepName", //Must be a valid value of the LEK_workflow_step table entries matching the workflow "state": "open", // a valid job state (open / waiting / finished / unconfirmed) "deadlineDate": "strtotime parsable string", //used as deadline Date then "user": { "type": "login", "login": "loginname" }, "user": { "type": "taskPm" }, "user": { //adds all users of the previous workflow step with given name "type": "previousWorkflowStep", "workflowStep": "translation" } }]}
Attention: This implies that the PM is always assigned to the task in the workflow, which implies that the PM will always get the task readonly on opening since mostly the workflow step for the PM is in status waiting. This is by purpose.
Attachments
Issue Links
- mentioned in
-
Page Loading...