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

As a Liferay Developer, I want to understand what type of activities represents each node when viewing an instance on the workflow tracking component



      As a Liferay Developer, I want to retrieve and display the stages of a Workflow Process in a product or site page, so that my clients can follow up on what are the stages of the application workflow and where their submissions are on it. In this story, the Join, Fork and Condition node types will also have a detailed representation. The user will be able to see the label of the transitions of a specific node while hovering it.

      Design Deliverables



      For some applications that leverage Liferay Kaleo Workflow to orchestrate the steps of a business process, it's a very common need to display and allow the user to understand what are the steps (or stages) of that application workflow, as well as where in the workflow he is currently and the past and following steps/stages. This information should be made available by workflow so Liferay Developers can leverage it to put in sites or even other products screens. The most important use case for this is displaying the stages of the order management of the admin UI AND surfaced in a widget (portlet) so devs can use it in the context of a site.

      Mockups of this feature being used in Commerce can be found here: https://www.figma.com/file/E9WSalmKKax2a6kAXP3FVc/Commerce-Admin-UI-v7.3?node-id=6185%3A310.

      Acceptance Criteria

      Given a product or site that as a workflow tracking component for instances,
      when viewing the workflow tracking of an instance,
      then the user should be able to understand the kind of node of each step in the workflow tracking component.

      • The component should display the Join, Fork and Condition node types with specific styles;
      • The component will display the transition label of a specific node while hovering it.

      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)


          Issue Links



              pt-zulu Product Team Zulu
              matheus.xavier Matheus Xavier (Inactive)
              Engineering Assignee:
              Matheus Xavier (Inactive)
              Recent user:
              Sophia Zhang
              Participants of an Issue:
              0 Vote for this issue
              0 Start watching this issue




                  Version Package
                  7.4.13 DXP GA1
         CE GA4