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

As an App User, I want to see all the past activities of a Workflow App instance

    Details

      Description

      As an App User, I want to see all the past activities of a Workflow App instance, so that I can audit an entry and understand what happened to it.

      Design Deliverables

      Mockups: https://www.figma.com/proto/q70IKvUbGPOUYD9cmEZLaE/12-LPS-119385-view-past-activities?node-id=1985%3A9146&viewport=-1057%2C-478%2C0.14110468327999115&scaling=min-zoom]
      Component: https://www.figma.com/file/q70IKvUbGPOUYD9cmEZLaE/12-LPS-119385-view-past-activities?node-id=2007%3A228

      Context

      Our Workflow Engine allow users to see all the past activities of an Workflow Instance. This audit feature is very valuable and should also be available when managing entries of a Workflow Powered App. With that being said, this Story aims to include this existing capability into the Workflow Apps.

      Acceptance Criteria

      1- Log a new Activity

      Given a deployed Workflow Powered App with one or more entries,
      when a user performs an action in one of the entries of the App that is valid to be logging in the Activities,
      then the action performed by the user should generate a new log into the activities section of the entry.

      • The Workflow Powered App should log the same actions that are considered valid by the Workflow Engine to generate new log in the activities of the My Workflow Tasks.
      2- See the log of Activities

      Given a deployed Workflow Powered App with one or more entries,
      when a user opens the Form/Details View of one of the entries,
      then the user should be able to see all the past activities that happened for that entry.

      • Each activity should inform a description and date that it happened.
      • Users can never erase or edit logs in the activities.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • 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:
              rodrigo.cunha Rodrigo Cunha
              Reporter:
              matheus.xavier Matheus Xavier
              Engineering Assignee:
              SE Support
              Recent user:
              Rodrigo Cunha
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master