Business rule on MDF object for HR manager

[haisamiqbal]

Hi guys,

We have created an MDF object and have linked it with a workflow. The HR manager role would initiate the changes which triggers the workflow, which also ends up with the HR manager role. So the workflow is like below:

HR manager --> Department Manager --> Division Head --> CHRO --> HR manager

We would also like to configure a rule that does not trigger at the time of initiating the change (by HR manager), but it should only trigger at the time when the workflow comes back to HR manager for his final approval at the end of the cycle.

Will appreciate guidance in this regard.

Thanks.

Haisam

[haisamiqbal]

Thanks Jasper for your quick and detailed response.

But, let me explain the scenario in a little more detail.

We need to configure a rule which requires the HR manager to fill out a field (i.e. Status) only at the end of the workflow, otherwise the workflow cannot be approved. The same field (i.e. Status) does not need to be populated in the beginning while the changes are being initiated by the HR manager.

And yes we have configured the rule and it works fine, but it also stops the HR manager from saving the changes in the beginning unless he populates the field (i.e. Status).

[nlgro023]

How would you then like the workflow to take place if it shouldn't trigger when initially submitted by the HR Manager?

I mean with a business rule we can exclude that the submitting of a workflow by a specific role (i.e. HR Manager) is prevented, but starting a new workflow at the end of an existing workflow is not possible by my knowledge. At best (although very difficult to achieve) the actual save of a record could be used to trigger intelligent services and then write another entry into (for instance) job info so that another workflow is triggered, but that would naturally no longer display changes (as the prior record has already been processed).