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

As an App Admin, I want to Liferay to handle multiple running versions of my App every time I make an update on a existing App

Details

    Description

      As an App Admin, I want Liferay to handle multiple running versions of my App every time I make an update on a existing App.

      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 this Story's scope, users should be able to:

      1. Understand that modifications made in a running Workflow App should impact only new instances/entries;
      2. Understand in which App version is each of the instances of the modified Workflow App.

      Acceptance Criteria

      1- Given that a user is editing a deployed Workflow App,
      when a user makes a modification in the App that changes the workflow process or views of the App,
      then the system must warn the user that the modifications made will generate a new version of the App and impact only new submissions in the App.

      • Update Actions that should generate new versions:
        • Add, change or remove steps or transitions of the Workflow Process (in general, actions that would normally generate new version of a Workflow Process);
        • Add, update or remove a Form View of one of the Workflow Steps;
        • Add, remove or update the assignees of a Workflow Process Step;
      • Actions that should not generate new versions ("Timeless" updates)
        • Change App Name;
        • Change Table View;
        • Change Deployment methods.

      2- Given a deployed Workflow App that has two or more versions already,
      when the user opens an instance in that running workflow App,
      then the user should be able to understand in which version of the Workflow App the instance is running in.

      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)

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Packages

                  Version Package
                  Master