As an User, I want to render a Native Object details view using the taglib

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Discarded
• Affects Version/s: None
• Fix Version/s: None
• Component/s: App Builder
• Labels:
  • 7.3-app_builder_must_have
  • 7.4-ce-ga2
  • 7.4-must
  • fc_20_02
• Story Points: 8
• Epic Link: App Builder - Extend Native Objects

As a DXP Developer, I want to render a Native Object Details View using the taglib

Design Deliverables

Mockups

Context

One of the App Builder's Native Objects value is the capability to extend and create custom views for Liferay's native objects. However, users may not want to just have those custom views available on the DXP Apps created through the App Builder, they also may want to render the Views and Apps somewhere, to substitute the Object's OOTB views or even to render it outside the DXP.

To achieve that, we need to allow users to render Native Objects Details Views created using the Data Engine taglib.

Acceptance Criteria

1- Given a Native Object with one or more Table Views created in the App Builder,
when the user decides to substitute the Native Object OOTB record details screen with one created in App Builder,
then the user must be able to use Data Engine taglib to render the Details Views created for that Native Object.

• Considering that the Native Object already has a storage adapter implemented.
• The behaviour when rendering is the same as the one rendered in the view entries deployed as widget

2- Given a Native Object with one or more Table Views created in the App Builder,
when the user decides to put the Details View created for that native object somewhere else,
then the user must be able to use Data Engine taglib to render the Details Views created for that Native Object.

• Considering that the Native Object already has a storage adapter implemented.

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