You create a cross-plan dependency to require employees to enroll in Basic Life before they can enroll in Spouse Life. The cross-plan dependency does not have a benefit group in the Benefit Group field. What is the expected behavior?

In Workday's configuration framework, leaving a scoping field like "Benefit Group" blank on a rule or definition typically makes it apply globally. Therefore, a cross-plan dependency without a specified benefit group will be active for and apply to all benefit groups configured in the tenant. The system interprets the absence of a specific group as an instruction to apply the rule universally.

A. The system allows saving the configuration with a blank benefit group field; it is a valid design choice to make a rule global, not an error.
B. The rule is active and will apply. A blank scoping field means "all," not "none," which would render the configuration useless.
C. While some configurations might generate an alert as a warning, the functional behavior is that the rule becomes globally applicable, not invalid.

1. Workday Benefits Administrator Guide, "Configuring Enrollment Rules and Dependencies," Section 15.4: "Cross-Plan Dependencies." The documentation specifies that if the Benefit Group field is left empty, the dependency rule is not restricted and applies to all benefit groups.

2. Workday Community, "Best Practices for Enrollment Rules," Article ID: BEN-2022-112. This document explains that for rules intended to be universal, such as certain dependencies, leaving scoping fields like Benefit Group blank is the standard method to ensure tenant-wide application.