Division-based Action Validation¶

During activity processing and rule execution, the RCX system enforces strict division validation for actions that reference entities or policies.

Action Division Validation¶

Actions that reference specific entities or policies validate division compatibility before execution. If the referenced entity doesn't belong to the user's division or the activity's priority-based division, the action fails with a division validation error.

Validated Entity Types¶

• Policies: TierPolicy, PursePolicy, RewardPolicy, StreakPolicy references
• Entities: Reward, Offer, Segment, Member references
• Configuration: Custom actions that reference division-specific configurations

Division Priority for Validation¶

The system uses the following priority order to determine valid divisions for action validation:

1. User Division: Primary division of the user executing the action
2. Activity Division: Division assigned to the current activity being processed
3. Priority-Based Division: Division determined by the division assignment priority rules

Validation Behavior¶

Error Handling¶

• Error Type: Division validation error
• Action Result: Action execution is blocked
• Processing Impact: Activity processing might fail or continue based on error handling configuration
• Logging: Division validation failures are logged for audit purposes

See also:

• Division Validation Rules