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

As an App Admin, I want to deploy a Workflow App with just Starting and Ending steps

    Details

      Description

      As an App Admin, I want to deploy a Workflow App with just Starting and Ending steps.

      Design Deliverables

      Mockups

      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, Table and a simple Workflow, with just start and end steps.

      In this Story's scope, users should be able to:

      1. Define the name of the Start-Type step;
      2. Define the name of the End-Type step;
      3. Configure the Main Object, Form View and Table View for the Start step;
      4. Deploy the Workflow Powered App with a two-steps workflow (Start and End).

      Acceptance Criteria

      1- Given that a user wants to create an App to automate a business process,
      when the user enters the Workflow Powered App creation experience,
      then the system should provide the configuration of a two-steps Workflow in the App creation.

      • The first step must be a Start-type node;
      • The final step must be an End-type node.

      2- Given that a user successfully configured all the required configs of the Workflow App Creation,
      when the user deploys the Workflow App,
      then the system should create a new Workflow Process according to the Users configurations and attach it to the new App created.

      • At this moment, the Workflow Process created through the App Builder creation experience should not appear in the Workflow Builder portlet (this shall change when the LPS-114359 gets implemented).

      3- Given that the user has set a name for the Start-step of the Workflow App,
      when the user deploys the Workflow Powered App,
      then the first status of the entries submitted in the App should have the name configure in the Start node of the App.

      • The name of the Start-step must be a required field.

      4- Given that the user has set a name for the End-step of the Workflow App,
      when the user deploys the Workflow Powered App,
      then the final status of the entries submitted in the App should have the name configure in the End-step of the App.

      • The name of the End-step must be a required field.

      5- Given that a user has configured a Form View for the Start-step of the Workflow App and successfully published the App,
      when a user enters the running App and clicks in the "+" button of the Table View to submit a new entry;
      then the Form displayed for the user should be the same Form View configured in the Start-step of the App creation.

      6- Given that a user has configured a Table View for the Start-step of the Workflow App and successfully published the App,
      when a user enters the running App;
      then the Table listing the entries of the running App should be the same that the user configured in the Start-step of the App creation.

      7- Given that a user published a Workflow App having only the Start and End steps,
      when a user enters the App and successfully submits a new record,
      then the system should automatically transition the new record from the Start-step to the End-step.

      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 (If applicable)

        Attachments

          Issue Links

          1.
          [DS] Mockups LPS-111635 Technical Task Closed Matheus Xavier  
          2.
          [PM] Acceptance Criteria LPS-111727 Technical Task Closed Matheus Xavier  
          3.
          [DS] Mockups adjustments LPS-111995 Technical Task Closed Matheus Xavier  
          4.
          [DS] Mockups Adjustments LPS-113752 Technical Task Closed Felipe Pires  
          5.
          Add ability to a new record triggers a workflow instance LPS-114371 Technical Task Closed Brian Chan  
          6.
          Create a workflow definition for each workflow app LPS-114372 Technical Task Closed Brian Chan  
          7.
          Display a workflow app entry according to app definition LPS-114373 Technical Task Closed Brian Chan  
          8.
          Add new workflow related columns to table view LPS-114374 Technical Task Closed Brian Chan  
          9.
          Hide app-builder workflow in the process builder LPS-114382 Technical Task Closed Brian Chan  
          10.
          Add ability to save a workflowed app with its steps/configuration LPS-114453 Technical Task Closed Brian Chan  
          11.
          Data Visualization LPS-114994 Technical Task Closed Brian Chan  
          12.
          Create workflow steps css markup LPS-115007 Technical Task Closed Gabriel Ramos  
          13.
          Show Data Object on Workflow Builder's step LPS-115575 Technical Task Closed Inácio Nery  
          14.
          [QA] Review ACs and Draft TCs LPS-115773 Technical Task Closed Rodrigo Cunha  
          15.
          [QA] Manual validation - Round 1 LPS-116307 Technical Testing Closed Rodrigo Cunha  
          16.
          It's possible to create a Workflow App without naming the "Start" and "End" steps making the App to crash LPS-116311 Impedibug Closed Brian Chan  
          17.
          When creating a second Workflow App, The "End" step is not displayed and the "Data Object" is not displayed inside the "Start" step and App crashes LPS-116312 Impedibug Closed Brian Chan  
          18.
          The "Status" and "Step" columns are not displaying "Pending" and "Start-step's name" when an entry is added LPS-116313 Impedibug Closed Rodrigo Cunha  
          19.
          "Start" and "End" step names are being recovered from a canceled creation of a Workflow App LPS-116314 Impedibug Closed Brian Chan  
          20.
          Layout is broken on the Workflow App creation screen for Firefox, Edge, Safari and IE11 LPS-116373 Impedibug Closed Albino Júnior  
          21.
          [QA] Manual validation - Round 2 LPS-116460 Technical Testing Closed Rodrigo Cunha  

            Activity

              People

              Assignee:
              rodrigo.cunha Rodrigo Cunha
              Reporter:
              matheus.xavier Matheus Xavier
              Engineering Assignee:
              Jon Wood
              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