Add review steps business rule not executing during form routing when succession planning conditions are met

HCM SAP SuccessFactors
, , , , , , , ,
1

I’ve configured a business rule to dynamically add review steps to our succession planning forms based on specific conditions, but the rule isn’t executing during form routing. The rule should add an executive review step when the succession readiness rating is ‘Ready Now’ and the position is at director level or above.

The business rule syntax appears correct and validates successfully in the rule editor. However, when forms meet the criteria, the additional review step doesn’t appear in the route map. The hidden step is configured in the route map template, and I’ve verified the condition evaluation logic matches our requirements.

Here’s the rule structure I’m using:

<rule id="add-exec-review">
  <condition>readiness='Ready Now' AND level>=5</condition>
  <action>addStep('executive_review')</action>
</rule>

The route map shows the executive_review step as hidden by default. Has anyone encountered business rules not triggering step additions during succession form routing? I’m wondering if there’s a configuration issue with how hidden steps are managed or if the condition evaluation timing is off.

2

Let me walk through the complete configuration requirements for dynamically adding review steps via business rules in succession planning forms.

Business Rule Syntax Verification First, ensure your business rule uses the correct syntax for SuccessFactors. The proper structure should be:

<rule>
  <when>
    <![CDATA[
      form.readiness == 'Ready Now' &&
      form.positionLevel >= 5
    ]]>
  </when>
  <then>
    <![CDATA[
      routeMap.showStep('executive_review');
    ]]>
  </then>
</rule>

Note the key differences: use form.fieldName notation for field references, double equals == for comparison, double ampersand && for logical AND, and routeMap.showStep() method rather than addStep(). The CDATA sections are required for complex expressions.

Route Map Configuration for Hidden Steps Your executive_review step must be fully configured in the route map, not just marked as hidden. Required configurations include:

  1. Step Definition: Define the step with a unique ID (‘executive_review’) and descriptive name
  2. Role Assignment: Assign the executive reviewer role - typically a role-based permission group like ‘Executive Leadership’
  3. Form Sections: Specify which form sections are accessible during this review step
  4. Step Entry Conditions: This is critical - set entry conditions that mirror your business rule logic
  5. Visibility: Set initial visibility to ‘hidden’ but ensure the step is marked as ‘active’ in the route map

The step entry conditions should be:


readiness = 'Ready Now' AND positionLevel >= 5

This creates alignment between when your business rule triggers the step and when the step is eligible to be entered.

Hidden Step Management Hidden steps in SuccessFactors operate differently than inactive steps. A hidden step exists in the route map but doesn’t appear in the routing sequence unless explicitly shown by a business rule. Key points:

  • Hidden steps must have complete configuration (roles, permissions, sections) even though they’re not initially visible
  • The step must be marked ‘active’ in the route map - ‘inactive’ steps cannot be shown by business rules
  • Hidden steps still count toward the total step sequence numbering
  • Permissions for hidden steps should be configured as if the step were always visible

Condition Evaluation Timing Business rules for route map modifications evaluate at specific trigger points. For add/show step rules, evaluation occurs:

  1. When form transitions from completion to routing phase
  2. After each step completion when determining next step
  3. When explicit rule re-evaluation is triggered

Your readiness rating and position level fields must be populated and saved BEFORE the form enters routing. If these fields are populated during routing, the initial evaluation will miss them. Consider adding a pre-routing validation step that:

  • Confirms required fields are populated
  • Saves the form state
  • Then triggers routing

Debugging Steps To diagnose why your rule isn’t executing:

  1. Enable business rule logging in Admin Center > System Configuration > Business Rules
  2. Submit a test form that meets your criteria
  3. Check the business rule execution log for your specific rule
  4. Look for evaluation results showing whether the condition matched
  5. Check for any error messages about step not found or permission issues

Common issues revealed by logs:

  • Field values are null or empty at evaluation time
  • Step ID mismatch between rule and route map
  • Insufficient permissions for the step role assignment
  • Step marked as inactive rather than hidden

Testing Approach Create a test scenario:

  1. Create a succession form with readiness = ‘Ready Now’ and level = 5
  2. Save the form completely before initiating routing
  3. Check the route map preview - the executive_review step should appear if rule triggered
  4. If step doesn’t appear, check business rule logs for evaluation details
  5. Verify the hidden step configuration includes all required elements

If logs show the rule evaluated but step didn’t appear, the issue is in the step configuration. If logs show the rule didn’t evaluate, the issue is in rule syntax or trigger timing.

Advanced Configuration For complex scenarios, consider using a two-rule approach:

  1. First rule: Validates conditions and sets a flag field
  2. Second rule: Shows the step based on the flag field

This separates condition evaluation from step manipulation and can help isolate where issues occur.

Implement these corrections and the dynamic step addition should function correctly. The key is ensuring complete alignment between business rule conditions, step entry conditions, and step configuration status.

3

I’ve seen this exact issue before. The problem often lies in the route map step configuration rather than the business rule itself. When you mark a step as hidden, you also need to ensure the step entry conditions are properly configured. The hidden step should have entry conditions that align with your business rule conditions, otherwise there’s a mismatch between when the rule tries to add the step and when the step is eligible to be entered.

4

The XML syntax you’re using looks like pseudocode rather than actual SuccessFactors business rule syntax. The real syntax uses specific tags and attribute references. Your condition should reference form fields using proper notation like form.readiness and form.level. Also, the addStep action needs to specify the step ID exactly as defined in your route map. Double-check that ‘executive_review’ matches the step ID in the route map configuration.

5

You’re right - I simplified the syntax for the post. The actual rule uses proper field references. I checked the execution order and the add step rule is positioned correctly in the sequence. The step ID matches exactly between the rule and route map. I’m starting to think the issue might be with the hidden step configuration itself. Does the hidden step need specific permissions or visibility settings beyond just being marked as hidden?

6

Hidden steps require careful configuration. The step must be in the route map with visibility set to ‘hidden’ but the step definition itself needs to be complete - assigned roles, permissions, form sections accessible during that step. A common mistake is creating a hidden step placeholder without fully configuring the step properties. The business rule can’t add a step that isn’t properly defined. Check that your executive_review step has all required configurations as if it were a visible step.