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

Verify the necessary tasks which need to be done to make Forms use the Data Engine Form Builder

    Details

    • Type: Spike
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Forms
    • Labels:
      None

      Description

      The documentation which provides an overview of Data Layout Builder Taglib (e.g. Data Engine Form Builder) makes clear what should and what shouldn't be expected from the Builder Taglib, for example, the data persistence isn't handled by it. Therefore, it's important to understand the Taglib's scope to define which tasks will be handled by it and which ones should be done on Forms' side. This Spike aims to answer the following questions:

      1. What are the necessary tasks to allow Forms render the Data Engine Form Builder instead of the current Form Builder?
      2. Will the use of Data Engine Form Builder affect the existent UI to create/edit Forms? If so, what are the side effects? Management Bar? Navigation Bar? Translation Manager (e.g. the UI to select languages)? Forms' title and description?
      3. Which tasks should be done on Forms' side to allow it be persisted on database using the Data Engine Form Builder?

        Attachments

        There are no Sub-Tasks for this issue.

          Activity

            People

            Assignee:
            marcos.martins Marcos Martins
            Reporter:
            renato.rego Renato RĂªgo
            Engineering Assignee:
            Marcos Martins
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package