As an App Adm, I want to publish my app as a widget

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: App Builder
• Labels:
  • 7.3-app_builder_must_have
  • 7.3-ce-ga1
  • appbuilder_test_manual
  • appbuilder_test_poshi_sanity
  • appbuilder_test_spira
• Story Points: 5
• Epic Link: App Builder - Create Custom Objects
• Sprint: App_Builder_7.3_4, App_Builder_7.3_5, App_Builder_7.3_6, App_Builder_7.3_8, App_Builder_7.3_7
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/78733

As an App Adm, I want to publish my app as a widget, so that I can publish my App's features embedded in my Liferay DXP Pages.

Design Deliverables:

Mockups

Context

In this Story, we aim to create the feature that will allow users to deploy their apps (composed of a Form View and a Table View) as a Widget inside his Liferay DXP instance.

Obs: In this Story, we don't need to have the previews for the Form View and Table View when deploying a new App. There is a specific Story for the preview feature.

Acceptance Criteria:

• 1- Given an object with at least one Form View and a Table View, when the user accesses the App tab of the object, then the user must be able to create a new App using the Form View and/or the Table Views available for the Object and deploy it as a Widget of his Liferay DXP.

• 2- Given an object with two or more Form Views, when the user is in the action of deploying a new App for this object, then the user must be able to choice which Form View he wishes to be deployed in the App.

• 3- Given an object with two or more Table Views, when the user is in the action of deploying a new App for this object, then the user must be able to choice which Table View he wishes to be deployed in the App.

• 4- Given an object with two or more Form Views, when the user is in the action of deploying a new App for this object, then the user must be able to deploy the App with only the Form View (and no Table View).

• 5- Given an object with two or more Table Views, when the user is in the action of deploying a new App for this object, then the user must be able to deploy the App with only the Table View (and no Form View).

• 6-Given an object with two or more Form Views, when the user accesses the App tab of the object, then the user must be able to deploy more than one App for this object.

• 7- Given an object with a App deployed using a specific Form or Table View, when the user decides to deploy a new App for this object, then the user must be able to deploy this new App using the same view (table or form) that was used in the other App of the object.

• 8- Given a user deploying a new App for an Object, when the users gets to the third step of the deploy action (choose deployment method), then the system must allow the user to choose if he wants to deploy it as a Widget of the Liferay DXP Instance.

• 9- Given an object with an App successfully deployed as a Widget, when the user accesses is creating a page and accesses the list of Widgets available, then the system must show the App as a Widget option.

• 10- Given an object with an App successfully deployed and added to a page as Widget, when a user accesses the page containing that Widget, then the system must display for the user the App with the Form and/or Table view chosen in the deployment.

• 11- Given an Object with one or more Apps deployed as Widgets, when the user properly fills and submits the form of any of those Apps' Widgets, then the entry that was submitted by the user must be stored in that App's Object.

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)