Change Working Hours

This topic lists the implementation considerations for the Change Working Hours process.

You can typically use field value defaulting and validation in these cases.

• Default action to first date of the month.
• Default Assignment Category to Part Time Regular and Full or Part Time to Part Time if FTE is less than 1. If FTE is 1 default Assignment Category to Full Time Regular and Full or Part Time to Full Time.
• Validate that when frequency is weekly, working hours aren't more than 40 hours.
• Validate if FTE exceeds 1 based on working hours .

This table lists the supported attributes, exceptions, and the implementation recommendations for the Change Working Hours process.

It applies to both pages under My Team and My Client Groups tabs.

In the Conditions for Defaulting and Validation	To Default Field Values	To Validate Field Values	Implementation Guidelines
Reference Objects supported in conditions employmentWorkers (If validation or defaulting involves data from multiple work relationships of the worker, then use this object. You can access one or all assignments from each of the work relationships within this object. All data returned by this object is retrieved directly from the database, reflecting the existing data rather than any modifications made in the current transaction.) employmentWorkerWorkRelationships (If validation or defaulting involves data from multiple assignments of the selected work relationship of the worker, then use this object. You can access one or all assignments of the selected work relationship within this object. All data returned by this object is retrieved directly from the database, reflecting the existing data rather than any modifications made by the user in the current transaction.) employmentWorkerAssignments (This object contains data of the selected assignment from database. This will be useful while defining defaulting or validation rules within When and Why section.All data returned by this object is retrieved directly from the database, reflecting the existing data rather than any modifications made in the current transaction.) JobLov - For the selected values on the Assignment section Job DFF LocationLov LocationsDFF - For the selected values on the Assignment section GradeLaddersLov GradeLov - For the selected values on the Assignment section Grade DFF DepartmentLov - For the selected values on the Assignment section Department DFF PositionLov Position Valid grades Position DFF - For the selected values on the Assignment section Action Action DFF - For the selected values on the Assignment section Action Reason - For the selected values on the Assignment section Action Reason DFF personsLov personProfile - For the selected values on the Assignment section CertificationItems - For the selected values on the Assignment section selfEmploymentDetail (This object contains the primary assignment information of the logged-in user.) Assignment EFF	Sections supporting Defaulting When and why (employmentWhenAndWhy) Assignment (employmentAssignments) Additional Assignment Info Fields in When and why section that support defaulting Action Action Reason Effective date Business Unit Position	Sections supporting Validations When and why (employmentWhenAndWhy) Assignment (employmentAssignments) Additional Assignment Info	Fields in When and why that aren’t supported ManageDirectsActionReasonId ManageDirectsActionId Fields in When and why that aren’t supported in the conditions ManageDirectsActionCode ManageDirectsActionReasonCode ManageDirectsActionTypeCode Fields in Assignment section that don’t support defaulting using BR Default Expense account People Group Flags like Primary assignment flag, Primary work relationship and Primary flag Business Unit and Position as they are taken from When and why Assignment Notes Assignment Type Standard working hours and frequency Synchronize from position Flag

Refer to Change Assignment for tips and considerations.