[CFAMX-7257] Spike - Investigate and Document the Order Schedule Arcitecture - HotSchedules JIRA

Details

Type: Story
Status: Closed (View Workflow)
Resolution: Completed
Affects Version/s: None
Fix Version/s: CFA 2020R1
Component/s: Ordering
Labels:
- AutoOrder

Sprint:
CFAMX 2020R1 Sprint 5
SCRUM Team:
Brotherhood of Mutants
Story Points:
2
SOW (Time Tracking) Project:
44918
Work Type Classification:
Sustaining

Description

As a developer I want to document the architecture behind the scheduled order functionality so that I can build a new configuration page in MxC to replace the Store Calendar

Notes

This is story is to dig into, document and get an understanding of how the process works to:
- Create an order schedule
- Edit an order schedule
- Delete an order schedule

Acceptance Criteria

Confirm that the overall architecture driving scheduled orders, and the schedules is documented

Notes from Will
Queries to get data:

select * from tbActionItem where ActionItemID in (8585)
select top 10 * from tbActionItemInstance where ActionItemID in (8585)
select top 10 * from tbOrderActionItem where ActionItemID in (8585)
select * from tbWorkFlowDatePattern where DatePatternID = 8731

What have I figured out?
When a schedule is created a record is inserted into:

tbActionItem
tbOrderActionItem
tbWorkFlowDatePattern
When an order is created and associated to that schedule, a record is created in tbActionItemInstance

Somehow the UI knows to show Order Schedules for specific days, using the data in these tables, I presume!

Document with more stuff that Will Englefield learned:
https://docs.google.com/document/d/1UKx8fXerygkksba3hHaDHmFPBMi1tRFnUcA9tG7joF8/edit?usp=sharing

Attachments

Issue Links

implements

CFAMX-5961 SC - Scheduled Ordering - Ability to AUTO-CREATE a suggested order for specific items from within InFORM, and place automatically at scheduled time