Skip to main content

The INCOMING_DATE in MO_WORKFLOW_STEPS is being overwritten when a step is reassigned

In this article, we explain why reassigning a step in Mosaic may overwrite the INCOMING_DATE field in MO_WORKFLOW_STEPS.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

This is fixed from Mosaic 22.2.1.0.
​
When a workstep is first created it will have an Incoming on date and Assignment date. The Incoming on date will remain static for that workstep. If a workstep is set to delay start (e.g. it is set in next actions with a future scheduled date) then the Delayed incoming date will be populated with the scheduled date.
​
If a workstep is re-assigned, the Assignment date will be updated and if the scheduled date is changed, the Delayed incoming date will either be updated (if it was previously recorded) or populated (where there was not previously a future scheduled date).

Did this answer your question?