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

As a Form Admin, I want to check the reports of my previously existing Forms

    Details

    • Epic Link:
    • Sprint:
      Forms_7.3_26, Forms_7.3_27, Forms_7.3_28, Forms_7.3_29, Forms_7.3_30

      Description

      As a Form Admin, I want to check the report of my previously existing Forms

      Context

      In this Story's scope, we should create a upgrade path and allow users to access the report of Forms that were created prior to the introduction of the feature.

      Acceptance Criteria

      Given that a user is using a DXP version that already has the Forms Reports feature,
      when the user opens a Form that was created prior to the introduction of the Report feature and clicks in the "Entries" tab,
      then the system should display a Report for that previously existing Form.

      Side effects care

      The Data Engine team is preparing an Upgrade Process which needs to be executed since the 7.3 release, therefore if this story demands the creation of an Upgrade Process that will generate a schema version upgrade, then it's mandatory to move the class UpgradeDDMStructure to the next available schema version, like in here. For example, if an Upgrade Process is implemented on this story and it needs to use the next available schema version, 3.8.0, then the class UpgradeDDMStructure should be adapted to use the schema version 3.9.0.

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              paloma.nunes Paloma Nunes (Inactive)
              Reporter:
              matheus.xavier Matheus Xavier (Inactive)
              Engineering Assignee:
              Marcos Martins
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master