As an Objects Admin, I want to add custom validations using the Groovy

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Objects
• Labels:
  • fc_22_04
  • givi-must
  • good-to-go
  • low-code-milestone
  • now-dxp-latam
  • qa_test_mapped
  • team-zulu
• Epic Link: Objects Data Validation

Context 

Liferay, with the Objects Framework has been working in providing customers with a no/low-code experience to customize the portal without changing its core code.. Even trying covering many different use cases out of the box (no-code), it is not possible to cover all of all customers use case without giving them a low-code experience to add their more specific business rules, in order to solve that, the goal of this story is to provide a way of allowing users to add validations with Groovy scripts.

Design Deliverables

Mockup

Acceptance Criteria

1 - Given an admin user,
when modeling my Object,
then I must be able to add validations using Groovy

2 - Given an admin user,
when managing my Object validation,
then I must be able to define if that validation is active or not

3 - Given a user adding a new entry in a object with validations,
when adding a new entry in the Object,
then I must only be able to submit the entry succesfully if it passes for all validations from that Object

4 - Given a user adding a new entry in a object with validations,
when editing an entry in an Object,
then I must only be able to update the entry succesfully if it passes for all validations from that Object

5 - Given an admin user,
when updating an existing validation,
then this validation must only affect the entries added or updated after the validation update

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 and Product;
• No critical bug related to Story scope (ex.: similar of FP4, FP5);
• Make sure that all system documentation were updated;