As an App Adm, I want to be warned when a Form View cannot be used to create new records for a Native Object.
- Native Field: Fields that comes OOTB with the Liferay Native Objects (e.g. Screen Name of Users);
- Custom Field: A custom field created by the user to extend a Native Object through App Builder.
- Required Native Fields: A Field that is both Native and required at Object level (e.g. Email of Users);
- Required Custom Field: A field that is both Custom and required at Object level.
If a user creates a Form View for a Native Object that doesn't include all required Native Fields of the Object, this Form View should still be saved and stored as an Object Form View, however, it cannot be used in features aiming to create new records for the Object.
Features that cannot allow Form View without all Required Native Fields (record creation):
- Form View selection for Standard Apps (CRUD) deployment.
Features that can use Form Views without all Required Native Fields:
- Taglib rendering in other parts of the DXP or outside the portal.
That being said, the system must validate and warn the user when he tries to use a Form View that doesn't contain all Required Native Fields in a non-allowed feature context.
1- Given that a Form View is being used by a deployed Native Object Standard App,
when update the Form View without including all the Native Object's Required Native Fields,
then the system should not allow the user to save the modifications while Apps that are using that Form Views to create new records are deployed.
2- Given that a user undeployed a Standard App and updated it's Form Views without including all the Native Object's Required Native Fields,
when the user tries to Deploy de App again,
then the system should not allow the user to re-deploy the App again and warn the user that the Form View of the App cannot be used to create new records for the Native Object.
3- Given that a Native Object has one or more deployed Apps,
when a user updates the Native Object to include a new Required Custom Field,
then the system must allow the user to include the new field, even if the doesn't include the Required Custom Field in the Form View.
- 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