[SLA] Create new SLA for total process resolution

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.X, Master
• Component/s: Workflow
• Labels:
  • fw_test_backend
  • fw_test_js
  • fw_test_manual
  • fw_test_testray
  • must-have
• Branch Version/s:
  7.2.x
• Backported to Branch:
  Committed
• Epic Link: SLA Settings
• Sprint: Workflow_7.2_05, Workflow_7.2_06, Workflow_7.2_07, Workflow_7.2_08, Workflow_7.2_09, Workflow_7.2_10

As a process owner, I want to create a new SLA, so I can define duration time for total process resolution.

Acceptance Criteria

• When there are no SLAs defined, the table should display the specific empty state;
• An SLA will have a name (required), a description (optional) and a duration time (required);
• For Duration Time section:
  • Only one of the fields are required (Day or Hours);
  • The fields should only accept numeric characters;
  • The “Hours” field will consider both hour and minutes as units. Users will provide input for each unit separately;
  • For hours, it should accept 23 as maximum value. The numeric control should block users from inputing a value bigger than 23. If a bigger value is typed in the field, the specific error message should be displayed;
  • For minutes, it should accept 59 as maximum value. The numeric control should block users from inputing a value bigger than 59. If a bigger value is typed in the field, the specific error message should be displayed;
• If the user leaves a required field in blank the specific error message should be displayed;
• SLAs within the same process can't have the same name. A specific error message should be displayed for this situation;
• All field validations should occurs on the fly, while the user fills in the form. It doesn't require the user to fill in the entire form or the form to be submitted to see it;
• The SLA metric will consider the total process resolution by default, so Start and Stop parameters are:
  • Start: Instance created;
  • End: Instance completed;
• The duration time will consider a 24/7 calendar by default;
• When displaying Duration Time on the SLA data table, we should shorten the time units by using the biggest measurement possible (See documentation for reference on displaying time);
• When an SLA is saved or updated, all instances In Progress for the current workflow version should recalculate time to reflect the duration time established;
  • An info alert should be embedded at the SLA dataset display informing there might be a delay for the updates to be fully processed (as specified on Figma mockup). The alert is temporary (disappear after 5sec) and dismissible;
  • It doesn’t recalculate time for completed instances;
• For the Reports table:
  • The sum for items On time + Overdue should be equal to the Total Open. (this criteria is not valid, cause some items may not have SLAs triggered)
  • When there is no SLAs set for a process, the columns On Time and Overdue should return an empty value (use dash "-");

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/JFaDDwXeKzCIfqbCwa5u3suU/06-create-sla-nm?node-id=1%3A205

Documentation
https://docs.google.com/document/d/1IsUguBBSI3swGZu7SSdADa8rpNWN6sfoCAt7YEgq0OI/edit?usp=sharing