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

As a Developer, I want to Implement the color field type


    • Sprint:
      Data_Engine_7.3_6, Data_Engine_7.3_7, Data_Engine_7.3_8, Data_Engine_7.3_9, Data_Engine_7.3_10, Data_Engine_7.3_11, Data_Engine_7.3_12, Data_Engine_7.3_13


      As an Developer, I want to implement the color field type, so that I can create applications that can get colors as input from users


      WEM & DM Requests:
      Currently, the Web Content and Documents & Media components leverage on the DDM to create Web Content Structures and Documents Types (Metadata fields) and as part of our product strategic planning, we want to migrate those dependencies of the DDM to the Data Engine, but ir oder to do that, we need to prepare the Data Engine to support all requirements that those two products currently has, including missing field types, missing features and an upgrade path to support all structures already created by the customers.

      The Color Field Type:
      The color field type is one of the fields that DDM has, but is missing in the Data Engine. This field is mostly used by the Web Content component, to let users choose colors as input for their contents. That being said, we need to create this new field type and make sure that all requirements that are currently supported by the DDM for this field, will also be covered in the Data Engine. Including:

      • Ability to define a Field Label;
      • Ability to Hide/Show the Label;
      • Ability to set as Required or not;
      • Ability to define the Name of the field;
      • Ability to set a Predefined Value;
      • Ability to define a Tip for the field;
      • Ability to set the Localizable and Indexable options;
      • Ability to set as "Repeatable";

      When being rendered/used, the field should:

      • Allow users to choose the colors from a palette (just as DDM does);
      • Provide an "advanced" option to let users choose any color they want with:
        • Alpha color picker;
        • Hex color picker;
        • RGB color picker;
        • HSV color picker;
        • Lightness color picker;

      Obs: The values should be stored as hexadecimal colors in the backend.

      Acceptance Criteria

      • Given a developer using the Data Engine to create an application, when the user is defining the Data Definition, then he should be able to include a color picker field type in the Data Definition;
      • Given a developer using the Data Engine to create an application, when the user is defining a color picker field in the Data Definition, then the Data Engine must give him the option to define all configurations that DDM does;
      • Given a Data Definition that has a Color Field type, when the user decides to render it using the taglib, then the Color Field type rendered should give the users the same option to pick a color that DDM does;

      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)


          Issue Links



              alex.candido Alex Candido
              eduardo.zoby Eduardo Zoby
              Engineering Assignee:
              Felipe Pires
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              0 Vote for this issue
              0 Start watching this issue




                  Version Package
                  7.3.0 CE GA1