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

[SLA] Be informed when errors occurs on SLA configurations


    • Branch Version/s:
    • Backported to Branch:
    • Epic Link:
    • Sprint:
      Workflow_7.2_10, Workflow_7.2_11, Workflow_7.2_12


      As a process owner, I want to be informed when errors occurs on SLAs configurations.

      SLAs are informed by workflow steps (start events, end events and tasks) in order to define when time should be tracked. If a workflow change happens, such as removing nodes or editing a task name, it may cause errors on the SLA definition.

      Acceptance Criteria

      • The SLA table should have the following columns:
        • SLA Name;
        • Description;
        • Duration;
        • Status: Running or Blocked;
        • Last Modified (the entries should be ordered from old to new by default);
      • Users should be able to click on SLA Name to go to the edit SLA page;
      • When there are SLA with errors in one or multiple processes:
        • At the report page, an alert message should be displayed indicating how many SLAs are blocked;
        • At the SLA list, an alert message should be displayed that there are blocked SLAs;
          • The SLA list should group SLAs into Blocked and Running sections;
        • At the SLA definition page, an alert message should be displayed indicating that errors are happening.
          • All fields with errors should have an error message;
      • When there are no errors on SLAs, the SLA list should not group the items into Blocked and Running sections;
      • If an SLA is blocked, the system can't count on any deadlines for the process instances until the error is fixed;
      • If there are active instances running in a previous workflow version with different nodes/paths or transitions from the most recent workflow version, the SLA may not be valid for them;
      • When users click to save/update an SLA, the system should check on workflow updates to make sure all options selected for Time frame fields are still valid; if one or multiple options are no longer available the appropriate error message should be displayed.
      • An SLA should be considered blocked when a change on the workflow definition completely remove the options selected for the Start and/or Stop fields, that are required fields for the SLA definition to work;

      Definitions of Done

      • Related tests created and passed successfully;
      • All Acceptance Criteria were passed;
      • Make sure that all system documentation were updated (if necessary);
      • Validated by QA, Product Designer and/or PM;
      • No critical issue related to Story scope (ex.: similar of a FP4, FP5 bug);
      • Code with peer review completed.

      Design Deliverable (See mockup page on Figma)

      Draft Documentation
      See Workflow Changes section


          Issue Links



              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created:


                  Version Package