Guest

Preview Tool

Cisco Bug: CSCul78403 - Enhancement: Dynamic Due Date Calculation

Last Modified

Jan 23, 2017

Products (1)

  • Cisco Prime Service Catalog

Known Affected Releases

tbd

Description (partial)

Symptom:
The due date is not getting altered dynamically based on the previous task completion. The due date should be calculated based on the individual Task Duration and Task actual Start Date, rather than being calculated only once, when the workflow starts.

Conditions:
Currently the Due Date is calculated at the start of the Delivery Plan and NOT recomputed.
For example, 
Task A1 (Service Team A) and Task B2 (Service Team B) both have an SLA of three days to complete.
The Delivery Plan starts on Aug. 1st and calculates the Due Dates for Task A1 to be Aug. 4th and Task B2 to be Aug. 7th.
Scenario 1
If Service Team A meets the SLA for Task A1 by completing on Aug. 2nd, two days earlier than the Due Date, Service Team B will have five days to complete the task. Since the Task B2 Due Date wasn't recomputed, Service Team B could fail to meet the SLA by completing Task B2 on Aug. 6th, taking four instead of three days, but according to the system Service Team B still met the Task B2 SLA Due Date of Aug. 7th and is NOT flagged for missing the SLA.

With Enhancement: the Due Date for Task B2 is recalculated to Aug. 5th, based on the Task Start Date of Aug. 2nd and the Task duration of three days. Service Team B completes Task B2 on Aug. 6th and IS flagged for missing the SLA.

Scenario 2
If Service Team A is flagged for failing to meet the SLA for Task A1 by completing on Aug. 6th, two days after the Due Date, Service Team B only has one day to complete the Task B2 by Aug. 7th. Since the Task B2 Due Date wasn't recomputed, Service Team B could meet the SLA by completing Task B2 on Aug. 8th, taking two instead of three days, but according to the system Service Team B failed to meet the Task B2 SLA Due Date of Aug. 7th and IS flagged for missing the SLA.

With Enhancement: the Due Date for Task B2 is recalculated to Aug. 9th, based on the Task Start Date of Aug. 6th and the Task duration of three days. Service Team B completes Task B2 on Aug. 8th, meets the SLA and is NOT flagged for missing the SLA.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.