A quick workflow with multiple target fields will take action only once when any of the multiple target fields are changed in a transaction (i.e. when the [Save] button is pressed on screen). This is to prevent duplicate records created in the system.
If a quick workflow has multiple target fields on the same table, it will fire only once when a row is updated even if the update changes multiple target fields on the table. In the below example, when the user updates the Start Date and the Relocation Phase fields that are on the Assignment Table and clicks saves, a QWF is fired only once. A second QWF is created when the user then updates the Hire Date field and clicks saves. This is because when making the changes, a different transaction took place.
In the case where an EAFH import changes all three of the target fields, the QWF will trigger only once per assignment per transaction even though the QWF has multiple target fields across different tables, This is because the EAFH import changes tracked fields on both the Employee and Assignment tables.
To ensure that QWFs are not triggered inappropriately, it is highly recommended to add additional conditions.
