Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-124440

As an App Adm, I want to define object's fields to be required at Object Level

    Details

      Description

      As an App Adm, I want to define object's fields to be required at Object Level or View Level

      Design Deliverable:

      Mockups

      Context: The Required Property

      Today, all fields in App Builder already has a property capable of determining if it should be required or not to be filled during a new entry submission. However, this property is only applicable to the view level, meaning that a same Object's field can be required in one Form View, but not in another. This is useful because depending on the App and business need, makes sense for a field to be required in one view, but not in another, once each view may have its own purpose. But this may also be a problem in others use cases, like:

      • When creating a new entry through the APIs: Once there is no view, no field is required, meaning that users can create entries without all necessary information.
      • When a user forgets to mark a field as required in a Form View. This way, people may also create new entries without all required information.

      To solve this problem, we must allow users to define if the field should be required at Object Level or at View Level. When required at Object level, all Form Views of this object must have this field as required as well. If required only at view level, the field will only be required in specific Form Views.

      Acceptance Criteria

      1- Given a user in the Form View of a Object with one or more fields in it,
      when a user clicks in a field and checks its properties,
      then the system must allow the user to define if the field should be required at Object Level, View Level or Non required.

      • The default value when marking the switch as required must be at ''View level''

      2- Given a user in the Form View of a Object with one or more fields in it,
      when a user clicks in a field and marks it as required at Object Level,
      then the field should now be required in any entry submission for the Object (be it through an App Builder Form View or APIs).

      3 Given a user in the Form View of a Object with one or more fields in it,
      when a user clicks in a field and marks it as required at Form View Level,
      then the field should only be required in entry submissions made through that specific Form View.

      4 Given a user in the Form View of a Object with one or more fields in it,
      when a field is marked as required at a form view level and the user marks it as not required,
      then the field should not be required in entry submissions made through that specific Form View.

      5- Given a user in the Form View of a Object with one or more fields in it,
      when a field is marked as required at an object level and the user marks it as not required,
      then the field should not be required in any entry submissions for this Object.

      6- Given an Object with one or more field marked as required at Object Level,
      when the user looks at the Object sidebar of a Form View screen,
      then the user must be able to identify which are the fields required at Object Level.

      7- Given a fieldset with one or more fields set as required,
      when the includes the fieldset in a Form View of an Object,
      then the fields set as required in the fieldset should be treated as required at Object Level.

      8 - Given field required at object level,
      when duplicating the field,
      then the system should also copy the required at object level setting.

      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              adriano.interaminense Adriano Interaminense
              Reporter:
              luiz.jardim Luiz Jardim
              Recent user:
              Sophia Zhang
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.13 DXP GA1
                  Master