You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
Whet someone wants to implement it's own DefaultAuthorizationProvider.newProcessInstance() when new process instance is created, this method is called multiple times. Once for the process instance itself, but also for all executions (links) from the start event element defined in the process definition.
Steps to reproduce (Required on creation)
Observed Behavior (Required on creation)
Expected behavior (Required on creation)
Root Cause (Required on prioritization)
Reason is that when execution is being created (process instance is also an execution) it is first sent to be stored into the storage and only later process instance specific fields are being assigned to the java object. One of the reason is that ID of the execution is generating during the storing of the execution.
Solution Ideas
Hints
Links
Breakdown
The content you are editing has changed. Please copy your edits and refresh the page.
Environment (Required on creation)
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
Whet someone wants to implement it's own DefaultAuthorizationProvider.newProcessInstance() when new process instance is created, this method is called multiple times. Once for the process instance itself, but also for all executions (links) from the start event element defined in the process definition.
Steps to reproduce (Required on creation)
Observed Behavior (Required on creation)
Expected behavior (Required on creation)
Root Cause (Required on prioritization)
Reason is that when execution is being created (process instance is also an execution) it is first sent to be stored into the storage and only later process instance specific fields are being assigned to the java object. One of the reason is that ID of the execution is generating during the storing of the execution.
Solution Ideas
Hints
Links
Breakdown
Pull Requests
Dev2QA handover
The text was updated successfully, but these errors were encountered: