Top Menu

Jump to content

Content

Improvement
Re-evaluate constraints when starting "spun off" approval process
#4264: Created by Pavol MederlyLast updated on 11/17/2017 12:49 PM.

From MID-4200:

When using e.g. <deltaFrom><itemValue>inducement</itemValue></deltaFrom> and making multiple changes to the role object, WF is split in inducement as desired. Other actions are included using includeActionIfPresent, also works nice. But - those incluced actions contraints are triggered by the objectstate before the split, so it e.g. triggers upon changes not contained in individual WF threads. Not sure if its feasability to change it to after split object state, but would make more sense.

I.e. when using processSpecification in approvalAction, new process instance can be created for a sub-delta. However, not all constraints triggered for the original action are relevant for this partial (spun off) approval process. We should do something like re-evaluation of the constraints there.

People

Assignee
PM
Pavol Mederly
Accountable
-

Details

Priority
Minor
Version
backlog
Affects Version/s
-
Components
Policies and approvals
Backport Version
-
Milestone
-
Fix Version/s
backlog
Git Revision
-
Subscription
Unknown
Jira key
MID-4264
Customer ID
-
Labels
-
Environment
-
You are on the Activity tab for Improvement Re-evaluate constraints when starting "spun off" approval process.