Completed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Rafael PraxedesRafael PraxedesReporter
Rafael PraxedesRafael Praxedes
Details
Details
Assignee
Rafael Praxedes
Rafael PraxedesReporter
Rafael Praxedes
Rafael PraxedesZendesk Support
Zendesk Support
Zendesk Support
Created March 31, 2021 at 10:40 AM
Updated October 26, 2021 at 2:03 AM
Resolved August 24, 2021 at 10:44 AM
As a Liferay Developer, I want to be able to wait for the end of the workflow's parallel processing, so that I can execute code that depends on the end of this processing
Given a code that uses the workflow api,
when the code calls the WorkflowHandlerRegistryUtil.startWorkflowInstance method,
then the code should be able to wait for the end of parallel processing and retrieve informations that depends on this.
The code must be able to retrieve the next transitions if, after starting, the workflow instance is in a task;
Given a code that uses the workflow api,
when the code calls the WorkflowInstanceManager.startWorkflowInstance method,
then the code should be able to wait for the end of parallel processing and retrieve informations that depends on this.
The code must be able to retrieve the next transitions if, after starting, the workflow instance is in a task;
Given a code that uses the workflow api,
when the code calls the WorkflowTaskManager.completeWorkflowTask method,
then the code should be able to wait for the end of parallel processing and retrieve informations that depends on this.
The code must be able to retrieve the next transitions if, after transition, the workflow instance is in a task;
Given a code that uses the workflow api,
when the code calls the WorkflowInstanceManager.signalWorkflowInstance method,
then the code should be able to wait for the end of parallel processing and retrieve informations that depends on this.
The code must be able to retrieve the next transitions if, after transition, the workflow instance is in a task;
Definition of Done (DoD):
All Acceptance Criteria were passed;
Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
Code with peer review completed;
Validated by QA, Product Designer and/or PM;
No critical bug related to Story scope (ex.: similar of FP4, FP5);
Make sure that all system documentation were updated (if necessary)
Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)
PS: this solution should help to fix all tickets with the wf-parallel-processing-effect label, see.