Skip to content

Commit ea6d63d

Browse files
Create README.md
CreateD README file
1 parent 4ae02a1 commit ea6d63d

File tree

1 file changed

+22
-0
lines changed
  • Server-Side Components/Business Rules/Set Due Date on Request and RITM based on Delivery Time

1 file changed

+22
-0
lines changed
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
**Use Case:**
2+
3+
When using generic request flows for catalog items, the catalog items have different delivery time. However, flow stages are not flexible enough to dynamically set the due dates based on catalog item's delivery time. This limitation can lead to inaccurate due dates, affecting SLAs and user expectations.
4+
5+
**Proposed Solution:**
6+
7+
To address this, create two business rules to set due dates of RITM and Request:
8+
1. Requested Item (RITM) Due Date:
9+
- Implement a Before Business Rule on the "sc_req_item" table.
10+
- This rule will calculate the due date by adding the delivery time (in days) from the associated catalog item record to the current date.
11+
- The calculated due date will then be set on the RITM.
12+
13+
2. Request Due Date:
14+
- Implement a Before Business Rule on the "sc_request" table.
15+
- It will then determine the maximum (farthest) due date among all RITMs associated with the request and set it as the due date for the request.
16+
- Since RITMs are created before the request record, this logic ensures accurate aggregation of due dates.
17+
18+
**Benefits:**
19+
- Ensures accurate due dates for both RITMs and Requests.
20+
- Improves SLA tracking and reporting.
21+
- Enhances user satisfaction by aligning expectations with actual delivery timelines.
22+
- Reduces manual intervention and customization in flows.

0 commit comments

Comments
 (0)