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

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.4.13 DXP GA1, Master
• Component/s: App Builder, Workflow
• Labels:
  • 7.4-ce-ga1
  • 7.4-must
  • dev_reviewed
  • fc_20_10
  • qa_automation_ticket_created
  • qa_design_reviewed
  • qa_requirement_linked
  • qa_reviewed
• Epic Link: App Builder and Workflow CE Integration

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