3775560 - Workflow behavior for Custom MDF records when a Dynamic Role approver is not assigned - SAP SuccessFactors Platform

In a Custom MDF Object scenario, you want to prevent users from submitting a record when one or more workflow steps use a Dynamic Role that does not resolve to an approver.

You would like to implement this validation using a Business Rule so that record submission is blocked if any workflow step (for example, Step 2) has no resolved user.

SAP SuccessFactors HCM Suite

1. Configure a workflow for a Custom MDF Object with one or more approval steps using Dynamic Roles.
2. Open record submission notice that only the first approver step is displayed, i.e. any other Dynamic Roles step does not resolve to any user.
3. Attempt to use a Business Rule to prevent submission when a workflow step has no resolved approver.

This behavior is expected.

Business Rules do not provide access to workflow runtime information that indicates whether workflow steps resolve to assigned users. The workflow-related parameters available within Business Rules are limited and do not support evaluating approver resolution for individual workflow steps.

As a result, it is not possible to configure a Business Rule that prevents submission of a Custom MDF record based on unresolved Dynamic Role assignments or insufficient workflow approval levels.

Preventing submission of a Custom MDF record because a workflow step does not resolve to an approver is not supported.

There is currently no supported configuration that allows Business Rules to validate whether all workflow approval steps have successfully resolved to users before submission.

Workaround

If the business requirement is to stop workflow processing when no approver can be determined, configure the No Approver Behavior setting in Manage Organization, Pay and Job Structures.

Set No Approver Behavior to Stop the Workflow. With this configuration, if a Dynamic Role does not resolve to an approver during workflow processing, the workflow will stop instead of continuing.

Note: This workaround does not prevent the initial submission of the Custom MDF record. It only controls how the workflow behaves after submission when no approver is resolved.

• KBA 2277529 - How to Create a Workflow
• KBA 2768151 - Triggering workflows on MDF objects using business rule
• KBA 2090228 - How to submit enhancement ideas for SAP SuccessFactors Products

custom mdf, dynamic role, workflow, no approver behavior, skip this step, stop the workflow, unresolved approver, elt manager, line manager, manage organization pay and job structure, approval step skipped, auto approve, prevent submission, business rule limitation, employee central , KBA , LOD-SF-MDF-WFL , Custom Object based Workflows , Problem