When an estimate is rejected, it is crucial to provide a mechanism for adding a reject reason.
Initially, in the workflow action, “Go to record” was chosen, and the “open in edit mode” checkbox was selected to allow users to modify the current record. Additionally, the reject reason field was designated as mandatory.
However, a problem arose when clients clicked the reject button but failed to input a reject reason. Upon clicking the cancel button, the record was saved without the required reject reason.
To address this issue, a transition was introduced from the reject state to the pending approval state, creating a loop. This transition was triggered “Before Record Load” and was contingent upon the condition that the reject reason field is empty. Furthermore, a new state, “permanently rejected,” was established, and a transition from the reject state to this new state was set up “After Record Submit.” This transition was dependent on the condition that the reject reason field is not empty. In the newly created state, the status value “Rejected” was assigned to clearly indicate the outcome of the rejection process.
In this situation, if the Reject button is activated followed by clicking the Cancel button without including the reject reason, the estimate will transition to the pending approval state, resulting in a loop.