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

Analyze existing code to validate possible ways to allow the rendering of custom conditions

    Details

    • Type: Spike
    • Status: Closed
    • Priority: Major
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Forms
    • Labels:
      None
    • Spike Type:
      Technical
    • Sprint:
      Forms_7.4_14, Forms_7.4_15

      Description

      Before start the implementation of the LPS-129417, Forms Team realized that would be necessary perform some investigation/code analysis through the Spike LPS-129671 in order to kick-off the implementation. However, during the refinement sessions of LPS-129417, the team raised the following questions that must be answered before we move on with the refinement session:

      • Can we use the existing tracker named DDMExpressionFunctionTracker instead of creating a new one to collect the custom conditions? If so, how can we propagate the custom conditions to the classes ConditionExpressionVisitor, DDMFormRuleConverterImpl and DDMExpressionFunctionMetadataHelper?
      • Do we really need to have the conditions hard coded in the front-end (BINARY_OPERATORS)? Is there any drawback to keep all the conditions only on the back-end?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              carolina.barbosa Carolina Barbosa
              Reporter:
              renato.rego Renato RĂªgo
              Engineering Assignee:
              Carolina Barbosa
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package