Running into problems with INSERT before/after rules not seeming to run in the order they are set.
For example, on our onboarding order guide the main onboard RITM has a variable for START DATE that I copy to the RITM field ONBOARD START DATE on insert before order 50. I then cascade that to all other RITM in the same REQ on insert before order 60 (I could not use order guide condition as the order guide is NOT SET yet on the other RITM at this point somehow),
Finally, at insert before order 100 is where all RITM get their DUE DATE calculated against the DEFAULT SLA field that exists on the ITEM that the form uses. The whole point of this is to make the DUE DATE = START DATE so long as the START DATE is further out than what the SLA would otherwise provide; we have it now on the super rare case a manager actually fills it out ahead of time, that the tickets will breach before the person shows up.
My script to do this though, when the insert before 100 runs to set the due date, the START DATE is not there yet on all except the first RITM (log statements), which makes no sense to me. I can see on the INSERTED record that there is already 3-4 updates done, and things are not going in the order that I show on the rules.
I need to get the DUE DATE correct before the SLAs get attached, but things are not going in the order I expect.
