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

As an App Admin, I want to deploy a Workflow App with an existing Object, Form and Table View

    Details

      Description

      As an App Admin, I want to deploy a Workflow App with an existing Object, Form and Table View

      Design Deliverables

      Mockups: https://www.figma.com/file/q1hJM2UkM6J9DBHO6lf5xK/24-deploy-workflow-app-existing-object-form-table-views?node-id=1541%3A12840

      Context

      One of the main values provided by the App Builder is the automation of business operations. Once the creation of Standard Apps aren't well driven for this use case, we decided that we should offer a separate and special experience for users that wants to create Apps to automate a business process, in way that we can leverage on the Apps tools that we have (Data Objects, Form and Table Views) and enhance it with Workflow capabilities.

      The result is what we are calling "Workflow Powered Apps". A special type of App with an intuitive interface that can create Apps integrated to a Workflow, making any data gathered from Form Views flow through different steps of a process to be reviewed or even complemented with more information.

      In the scope of this Story, we want the feature to create the simplest App possible, with just an existing Object, Form and Table View.

      • The remaining features (workflow process, assignee, steps, etc.) will be implement incrementally along the following Stories of the backlog;
      • That being said, even though this is the same configuration as a Standard App, when created through here, the App should be already tagged as a 'Workflow App'.

      Acceptance Criteria

      1- Given a user in the App Builder's Apps screen,
      when the user clicks in the "+" button, selects "Workflow App" and clicks "Continue",
      then the user should be redirected to the Workflow App creation experience.

      2- Given that a user has entered the Workflow App Creation experience,
      when the user clicks in the App Name text box in the upper toolbar of the screen,
      then the user should be able to define/edit the name of App that is being created.

      3- Given that a user has entered the Workflow App Creation experience,
      when the user clicks in "Data and Views" (right sidebar) and clicks on the Main Data Object Choice Field,
      then the user should be able to see all available Objects in the DXP instance and choose the desired one to be the App's main Data Object.

      • The list of Objects should also inform the type of object (native or custom)
      • Users should be able to search for a Object in the dropdown component.

      4- Given that the user already selected the Main Data Object of the Workflow App,
      when the user clicks on the Form View Choice field,
      then the user should be able to see all available existing Form Views for the selected Object and choose the desired one to be the App's Form View.

      • Users should be able to search for a Form View in the dropdown component.

      5- Given that the user already selected the Main Data Object of the Workflow App,
      when the user clicks on the Table View Choice field,
      then the user should be able to see all available existing Table Views for the selected Object and choose the desired one to be the App's Table View.

      • Users should be able to search for a Table View in the dropdown component.

      6- Given that the user has named the App and selected a valid Main Data Object, Form View and Table View,
      when the user clicks in the "Deploy" button,
      then the user should be able to define the deployment types desired and deploy his new App.

      • The deployment should offer the same deployment options and experience as the Standard App (Standalone, Widget and Product Menu).
      • Users should not be allowed to deploy App without a Name, Main Data Object, Form View, Table View or Deployment Type selected.

      7- Given that a user has entered the Workflow App Creation experience,
      when the user clicks in the "Cancel" button,
      then the App creation should be canceled and any changes made should be dropped.

      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

            Activity

              People

              • Assignee:
                rodrigo.cunha Rodrigo Cunha
                Reporter:
                matheus.xavier Matheus Xavier
                Engineering Assignee:
                Product Team Workflow
                Recent user:
                Tayanna Sotero
                Participants of an Issue:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  Master