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

    Details

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

      Description

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

      Context
      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)
      https://www.figma.com/file/Jnb2XPEBvyziBYZbjbVTMG/10-sla-errors?node-id=201%3A12146

      Draft Documentation
      See Workflow Changes section

        Attachments

          Issue Links

          1.
          Wireframe Creation LPS-89910 Technical Task Closed Nathália Moura (Inactive)  
          2.
          Mockups Creation LPS-90125 Technical Task Closed Nathália Moura (Inactive)  
          3.
          Mockups Creation LPS-90298 Technical Task Closed Nathália Moura (Inactive)  
          4.
          Tech Review LPS-90301 Technical Task Closed Rafael Praxedes  
          5.
          QA Review LPS-90302 Technical Task Closed Diego Furtado  
          6.
          Add endpoint LPS-93689 Technical Task Closed Rafael Praxedes  
          7.
          Check if SLA definition is according the workflow definition LPS-93691 Technical Task Closed Rafael Praxedes  
          8.
          Product QA Test Creation LPS-93745 Technical Testing Closed Manoel Cyreno  
          9.
          Product QA Test Validation - Round 1 LPS-93746 Technical Testing Closed Cleyton Magalhaes  
          10.
          Frontend adjusts to new data structure LPS-94474 Technical Task Closed Rafael Praxedes  
          11.
          Add frontend validation LPS-94927 Technical Task Closed Brian Chan  
          12.
          Rebase Language LPS-95205 Technical Task Closed Brian Chan  
          13.
          Design Review LPS-95247 Technical Task Closed Nathália Moura (Inactive)  
          14.
          [BUG] Warning message is being displayed at the wrong moment LPS-95368 Technical Task Closed Brian Chan  
          15.
          [BUG] When the SLA is blocked the system is counting on the previous SLA status for the process instance LPS-95369 Technical Task Closed Brian Chan  
          16.
          [BUG] The Workload by Step table is not counting pending tasks for instances initiated in previous workflow versions LPS-95373 Technical Task Closed Brian Chan  
          17.
          [BUG] Wrong error message on SLA definition form LPS-95376 Technical Task Closed Brian Chan  
          18.
          [Bug] SLAs are being blocked when a task not used in the SLA is changed for the first time LPS-95674 Technical Task Closed Cleyton Magalhaes  
          19.
          Product QA Test Validation - Round 2 LPS-95683 Technical Testing Closed Cleyton Magalhaes  

            Activity

              People

              Assignee:
              cleyton.magalhaes Cleyton Magalhaes
              Reporter:
              nathalia.moura Nathália Moura (Inactive)
              Recent user:
              Brian Wulbern
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.2.X
                  Master