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

As an App Adm, I want my App's submissions to be able to trigger a Workflow process

Details

    Description

      As an App Adm, I want my App's submissions to be able to trigger a Workflow process, so that I can use a workflow to approve content submitted in my App.

      Design Deliverables

      Mockups

      Components

      Context

      Just as it works on Forms and others DXP Portlets, Apps created through App Builder also needs to be supported by Workflow, so people can trigger workflow and approve submissions after a new entry is submitted on the App.

      To allow this, we should:

      • Include an option to select an existing Workflow to be associate to the App in the deployment experience;
      • Trigger the selected workflow when a new submission is made on a App that has a workflow configured.
        • The experience should be similar to the usage of Forms with Workflow.

      Obs:

      1. Users should be able to select a different workflow for each deployed App in App Builder.
      2. User should still be able to create Apps without workflow.

      Acceptance Criterias

      1- Include a step in the Standard deployment wizard to select a Workflow
      Given that a user is deploying a new App in App Builder,
      when the user reaches the Workflow Configuration step,
      then the system should list for the user all available Workflows in the DXP instance.

      • It should be displayed the Name, Created Date and Modified Date of each Workflow in the list.

      2- Search for a Workflow in the Standard App deployment wizard
      Given that a user is in the Workflow Step of the App deployment experience,
      when searches for a Workflow in the search field,
      then the system should load only the Workflow that attends the terms searched by the user.

      3- Trigger the Workflow when a new submission is made
      Given that a user is in the Workflow Step of the App deployment experience,
      when the user selects a Workflow in the list, clicks next and finishes the App's deployment,
      then any submission made in the App should trigger the selected Workflow.

      • The experience should be similar to the usage of Forms with Workflow, where the submissions are kept as "Draft" until approved in the Workflow.

      4- Deploy an Standard App without Workflow
      Given that a user is in the Workflow Step of the App deployment experience,
      when the user selects the "No Workflow" option, clicks next and finishes the App's deployment,
      then the App should be created and deployed without workflow.

      5- Track the submission status in the Workflow process
      Given a Standard App with an Approval Workflow attached to it and it has one or more submissions,
      when a user accesses the Table View of the App,
      then he should be able to identify the Approval status of the entry (Draft or Approved).

      • Nice to have: Also allow users to see the current step of the submission in the Approval Workflow Process.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Verify if the test labels were added;
      • 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

      Attachments

        Issue Links

          1.
          Add a new step to associate a workflow process in the flow of creating a standard app LPS-122373 Technical Task Closed Albino Júnior (Inactive)  
          2.
          List workflow processes and allow the selection of one item to deploy the app LPS-122374 Technical Task Closed Albino Júnior (Inactive)  
          3.
          Add status column in the list of entries of deployed app LPS-122375 Technical Task Closed Gabriel Ramos (Inactive)  
          4.
          Show workflow info in standard app View Entry, if any LPS-122377 Technical Task Closed Rafael Praxedes  
          5.
          Add new scenarios to increase test coverage LPS-122379 Technical Task Closed Gabriel Ramos (Inactive)  
          6.
          Provide endpoint to return list of definitions LPS-122380 Technical Task Closed Product Team Zulu (Inactive)  
          7.
          Trigger workflow when submitting an entry LPS-122381 Technical Task Closed Rafael Praxedes  
          8.
          Provide "status" and "version" attributes for each entry (Data Engine) LPS-122382 Technical Task Closed Brian Chan  
          9.
          Store link between the App and Workflow Definition LPS-122476 Technical Task Closed Product Team Zulu (Inactive)  
          10.
          Add ability to search by the workflow definition Title LPS-122655 Technical Task Closed Rafael Praxedes  
          11.
          View Entry's preview in My Workflow Tasks LPS-122656 Technical Task Closed Product Team Zulu (Inactive)  
          12.
          Adjust "no results found" state layout LPS-122712 Technical Task Closed Product Team Zulu (Inactive)  
          13.
          Increase coverage of Entry files LPS-122713 Technical Task Closed Product Team Zulu (Inactive)  
          14.
          Update tests to cover search empty state in all steps LPS-122833 Technical Task Closed Product Team Zulu (Inactive)  
          15.
          [QA] Review ACs and Draft TCs LPS-122838 Technical Task Closed Rodrigo Cunha (Inactive)  
          16.
          [PM] Product Review and Validation LPS-123055 Technical Task Closed Matheus Xavier (Inactive)  
          17.
          [UX] Design Review and Validation LPS-123056 Technical Task Closed Jon Wood  
          18.
          [QA] Manual validation - Round 1 LPS-123190 Technical Testing Closed Rodrigo Cunha (Inactive)  
          19.
          UI elements (list + footer buttons) are broken LPS-123201 Impedibug Closed Product Team Zulu (Inactive)  
          20.
          Standard App entry is being moved to "Approved" status when edited LPS-123223 Impedibug Closed Product Team Zulu (Inactive)  
          21.
          The status is changed to "Approved" after editing an entry that was withdrawn LPS-123225 Impedibug Closed Product Team Zulu (Inactive)  
          22.
          [QA] Manual validation - Round 2 LPS-123380 Technical Testing Closed Rodrigo Cunha (Inactive)  

          Activity

            People

              rodrigo.cunha Rodrigo Cunha (Inactive)
              matheus.xavier Matheus Xavier (Inactive)
              SE Support SE Support
              Kiyoshi Lee Kiyoshi Lee
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Packages

                  Version Package
                  7.4.13 DXP GA1
                  Master