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

As an App Adm, I want to able to define a field as read-only



      As an App Adm, I want to define in the UI a field as read-only at a form view level, so that I can give context to the user while filling a form.

      Design Deliverable:




      • An administrator may want to create a custom form view to allow users to change their name and screen name but not their email address. The administrator still wants to display the email address as a read-only field so the user can see what email is associated with their profile.
      • Field values like auto-generated ID, version, and last modified date cannot be edited, but administrators may want to display these values in read-only mode when editing a data record.
      • Calculation results as the partial value of the cart while shopping, today it is possible to use other fields to show the results, but they still are not read-only.

      Acceptance Criteria

      1- Given an app admin,
      when creating a form view to an object,
      then the system should allow me to define a field as read-only in a form view.

      • This read-only property should be available to the following field types:
        • Text
        • Select from List
        • Single Selection
        • Multiple Selection
        • Grid
        • Date
        • Numeric
        • Rich Text
        • Color
      • The field types that should not have the read-only property are:
        • Paragraph
        • Image
        • Upload
        • Separator

      2- Given an user,
      when filling a form,
      then I should not be able to edit a read-only field.

      3- Given an user,
      when filling a form,
      then I should be able to see the predefined value in the read-only field.

      4- Given an app admin,
      when creating a new form view to an object,
      then the read-only property must be marked as it was in the last form view created.

      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


          Issue Links



              luiz.jardim Luiz Jardim
              luiz.jardim Luiz Jardim
              Recent user:
              Leide Mangueira
              Participants of an Issue:
              0 Vote for this issue
              1 Start watching this issue




                  Version Package