As an App Admin, I want to understand which Object was used on each App created using App Builder

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: App Builder, Workflow
• Labels:
  • 7.3-dxp-m4
  • fc_20_04
  • mvp_must_have
  • qa_design_reviewed
  • qa_reviewed
• Epic Link: Process-Driven Apps 7.3 MVP

As an App Admin, I want to manage in one place all my Apps created using any object from App Builder

Design Deliverables

Mockups: https://www.figma.com/file/ZmXPQW3tqYEeuz3kSki2AB/21-see-object-column-in-apps-table?node-id=1%3A61

Context

In App Builder's first version (MVP), we launched it allowing the creation of Apps with only one Object and, because of that, we placed the App creation experience inside the Data Object scope. However, now we are planning to launch a new feature (Process-Driven Apps) that will allow users to create Apps containing more than one Object. This means Apps cannot be inside an Object scope anymore.

To solve this, we need to create a new screen/space to allow users to manage Apps create to all and any Data Object. This screen should be inside the "App Builder" section of the Control Panel Menu and coexist with the "Object" screen that is already there.

In this story scope, users should be able to view which Data Objects are being used on each App.

Acceptance Criteria

Given a user in the App management screen of App Builder,
when the user checks the details of an App in the list,
then the user should be able to see which Data Object is being used by the App.

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