The current system behaviour is that when a Work Order Sub-status is updated on a Work Order, the System Status value is updated even if it is not different to the existing value.
This causes multiple triggers of Processes and Flows that are triggered by the change of the System Status field in the Work Order entity.
Our use case is that we have 2 x sub-status records with System Status = Posted.
- Issued for Invoicing - default value
- Invoiced - updated later by data
When the 'Invoiced' sub-status is set, all Processes and Flows that are triggered by System Status = Posted are re-triggered, and the Closed On, and Closed By fields are also updated.
We do not believe these fields should be updated, as they were already set.
The requested change is that when a sub-status lookup is changed on a Work Order record, IF the System Status of the new Sub-status is the same as the existing Work Order (System Status) then the System Status value should not be re-written as it is not changed.
It is not possible to set a direct filtered trigger in a Flow based on a sub-status value as it is a lookup.