Our Hire BP has a conditional 'Request Compensation Change' step gated on a calculated field that checks the job profile's compensation grade. For one supervisory org it never fires, even though the grades are populated. Same job profiles work fine elsewhere. I've checked the condition rule, the security groups on the step, and the org's staffing model. Stuck.
Members answer here — the people who actually run these systems.
Request to joinWhen you say 'never fires' — does the step show as skipped in the BP history, or does it not appear at all? If it's skipped, the condition is evaluating false. If it's absent, it's a security group problem on that org's initiator.
Skipped, with 'condition not met'. But the grade IS on the position.
Calculated fields that read compensation grade evaluate against the grade as of the BP effective date. If that org did a bulk grade reload with a later effective date than your test hires, the field returns blank for the earlier date. Try a hire dated after the reload.
That was it. The grade assignments for that org were loaded effective the 1st of next month. Hires dated before that see no grade. Re-dated the test and the comp step fired. Good catch.