Foundation Objects (like Job Classification, Location, Department, etc.) are the core building blocks used to define organizational structure and employee attributes. Business rules for benefits eligibility are typically triggered based on values stored in these foundation objects, making their correct configuration the primary prerequisite.

Hiring Templates store default data for new hires. Correcting the template ensures all future hires using that template will have the accurate default value. This is efficient and targeted, avoiding manual updates to existing records or altering foundational data that might impact other rules.

A Legal Entity in Employee Central represents a distinct, legally recognized company (like an acquired subsidiary) within the corporate structure. It allows for the configuration and management of unique employment laws, pay groups, benefits plans, and other rules specific to that entity, separate from the parent company.

Ad Hoc Reporting within the People Profile allows authorized users to dynamically filter, search, and build lists of employees based on a wide range of criteria (like department, employment type, and date fields) directly in the UI. It’s designed for flexible, self-service queries without needing pre-built analytic reports.

A Workflow is the mechanism that automates business processes by defining a sequence of steps, actions (like approvals), and responsible parties (users or roles). It controls the routing of transactions like promotions, transfers, or terminations through the required approval chains.

This requires combining Permission Groups (which define what actions/users can do/see) with Dynamic Groups or Population Groups (which define the set of employees, e.g., ‘all employees in EMEA region’). By associating a permission group with a specific dynamic group, you restrict data access to only those employees within the defined population.

Business Rules in Employee Central, especially those using the Advanced Formula Engine, are designed to implement complex, conditional logic and calculations. They can reference dates (like hire date), other field values (salary, bonus target), and perform mathematical operations to automate proration and other derived calculations.

To capture new data points not present in standard fields, you must create a custom field (MDF object). You would define this field (e.g., ‘Ethics Training Completion Date’) on a relevant portlet (like ‘Certifications’ or a custom section) to allow for data entry and storage for each employee.

A Business Rule configured with a ‘Field Derivation’ action is used to automatically populate (derive) the value of one field based on the value of another field or a set of conditions. In this case, it would watch for a change to the location field and set the time zone accordingly.

Foundation Objects (like Job Classification, Location, Department, etc.) are the core building blocks used to define organizational structure and employee attributes. Business rules for benefits eligibility are typically triggered based on values stored in these foundation objects, making their correct configuration the primary prerequisite.0