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

As an App Adm, I want to overwrite the visual properties of my object's fields at view level

    Details

      Description

      Design Deliverable:

      Mockups

      As an App Adm, I want to overwrite the visual properties of my object's fields at view level, so that I can adapt my field's layout to each Form View purpose.

      Context: Field's Visual Properties

      On App Builder, Object's fields are shared across multiple Form Views. While some field's properties will always have the same value/configuration across all views, other properties may need to be adapted to each Form View purpose. For instance, a Form View made to gather B2C orders may use a predefined value "B2C" for a field named "Order Type", while another Form View made to gather B2B orders may use a different predefined value ("B2B") for the same field ("Order Type").

      To solve that, we need to allow users to define the visual properties of the fields at View Level, in a way that changing those properties in a Form View A, won't change the visual properties of this same field in another Form View B.

      Fields Visual Properties are:

      • Label;
      • Placeholder Text;
      • Help Text;
      • Predefined Value;
      • Show Label (On/Off) - This one can be always "On" at object level and overwrote to "Off" when added to a new view;
      • Selection Field Types Inline option (On/Off)
      • Multiple Selection Show as Switcher option (On/Off)
      • Required

      Requirements:

      • When a user changes one of the visual properties of a field in one Form View, it should not automatically propagate the updates to the other Form Views that also have the field. By default, it should be only applied to the current Form View that was updated.
      • When an existing field is first time added to a Field View, it should be added with the Visual Properties values/configurations that were most recently defined.
        • Meaning that the Field Visual Properties default value will be always the last update made on it;
        • The only exception should be the "Show Label" property. This one default value should be always "On" when first-time added to a Form View.

      Acceptance Criteria

      1- Given an Object with multiple Form Views containing one same Object field,
      when a user updates one of the visual properties of the shared field in one of the Form Views,
      then the updates made on the field visual property should be applied only to the current Form View (it should not be automatically updated on the other Form Views that also has the field).

      • To check the list of properties that are considered "Visual Property", please take a look at the "Context" section of this Story.

      2- Given that a user updated a visual property value of an existing Field from "X" to "Y" in a Form View;
      when a user adds this field for the first time in another Form View;
      then the default value of the visual property when added to the Form View should be "Y".

      • The only exception here is the "Show Label" property. This one default value should be always "On" when first-time added to a Form View.

      3- Given an Object with two or more Form Views with one or more Visual Properties edited/overwritten in just one of the Form Views
      when the user opens that Form View and selects one of the field that had a Visual Property edited/overwritten,
      then the system should show the Visual Properties of the field with the values relating to that Form View modifications.

      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 was updated (if necessary)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              Assignee:
              support-qa Support QA
              Reporter:
              matheus.xavier Matheus Xavier (Inactive)
              Recent user:
              Sophia Zhang
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.13 DXP GA1
                  Master