Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-129960

Create an API to add the ability to wait for the end of the workflow's parallel processing

    Details

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rafael.praxedes Rafael Praxedes
              Reporter:
              rafael.praxedes Rafael Praxedes
              Engineering Assignee:
              Rafael Praxedes
              Recent user:
              Ana Buchmann
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master