Validate Rule with Error Message for Payment Info MDF object being called in Workflow Step Approvals

[former_member38738]

Hi Experts,

We have configured a Validate Rule for Payment Information MDF object to throw an Error Message if Login User (initiator) is not a Worker and don't allow to save.

Rule is called perfectly when clicked on Save button and throw the error message. While if Initiator and Worker are same then no error message received.

Then another on Save Rule trigger the workflow for the approval.

The Problem is, the same rule that checks Initiator and Worker (which is on Validate in MDF Object Definition screen) also gets triggered during Workflow approval final step and not allowing to save the record even when it was initiated by the worker itself.

So this is kind of a deadlock situation where Initiator and Worker are never going to be same for a Workflow evaluation perspective.

Kindly suggest what could be the problem and how we can bypass this Validate rule from the Workflow step approvals.

We tried with On Save and Validate and both way not working.

Just to mention The Rule type for Error Message Validation is a Basic Rule...trying a Rule for MDF Based objects with Validate as a Purpose can help..??

Thanks & Regards

Varun

[former_member38738]

Hi Harold,

Thank you so much for sharing the views and workable solutions.

Glad to see someone thinking and proposing the same way as we also thought of.

But really appreciate your thoughts and help.

So what we did is basically workaround 1.

since it is a two step process and last step workflow participants were facing the issue, we put them all in a permission group and bypassed from the rule. Since none of them have access to Edit Payment Information anyways, that secured the whole design and without any flaw this workaround worked out.

However the 2nd that you have proposed, we thought somewhat similar approach to have 1 filed that will get updated like a counter once 1st step is approved and based on that counter field the rule will be bypassed for the 2nd step approver to proceed. While saving the record, value will remain 0 for the counter and thus rule will throw error but not when approved by the 1st step approver.

Though this one is a bit complicated and involve lot of change, business is happy with the 1st approach and that's how we have designed.

Still Thank you so much mate for sharing your views and all assistance.

Cheers!

Varun

[haroldyrureta]

Hi!

Hope you're good. I see two workarounds that could help you with this issue, since the rule will be executing every time.

1. If all the approver belong to the same authorization group you can exclude them for your rule so no error will be shown for them, but they will also be able to create new registers for other users.

2. Create a new field to save the "progress" of the workflow, then create 2 rules, 1st one to complete the field progress with the the value "COMPLETE" in case the initiator is the worker and the 2nd one to validate if the value is not "COMPLETE" the error message will be shown.

So, if the initiator is not the same as the worker the new field wouldn't have the value "COMPLETE" so the error will be shown, but if it's indeed the same the field would be complete and no error will be shown, also no error should be shown in the approval workflow.

Feel free to reach out to me in case you need it.

Kind regards.