Add Assignment

This topic lists the implementation considerations for the Add Assignment process.

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

• Default union member based on bargaining unit.
• Default assignment descriptive flexfield (DFF) when position is changed.
• Validate that assignment context sensitive DFF has 4 numeric fields and that the sum of all numeric values must be 100 or 0.
• Validate that the permanent/temporary field based on the person type.

This table lists the supported attributes, exceptions, and the implementation recommendations for the Add Assignment process.

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

In the Conditions for both Defaulting and Validation	To Default Field Values	To Validate Field Values	Implementation Guidelines
Reference Objects supported in conditions employmentWorkers employmentWorkerWorkRelationships employmentWorkerAssignment JobLov Job DFF LocationLov LocationsDFF GradeLaddersLov GradeLov Grade DFF DepartmentLov Department DFF PositionLov Position Valid grades Position DFF Action Action DFF Action Reason Action Reason DFF personsLov Assignment EFF Source Assignment Source Work Relationship Worker	Sections supporting Default from BR When and why (actionOccurrences) Assignment (addPersonWorkRelationships) Fields in When and why section that support defaulting Action Id Action Reason Id Business Unit Position Create new contract	Sections supporting Validations from BR When and why (actionOccurrences) Assignment (addPersonWorkRelationships)	Fields in When and why that don't support defaulting Effective Date Fields in Assignment that don’t support defaulting 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

Considerations for Implementing Add Assignment

• Any defaulting of Action Date isn't supported currently. It will be supported in a later release.
• Use employmentWhenAndWhy.ActionDate != null as the primary condition for the defaulting and validation rules in the When and why section (excluding Effective Date Defaulting).
• For rules involving Assignment attributes, use the following expression as the primary condition:
  • $fields.sourceAssignment.AssignmentId != null. This will help prevent the rule from being executed in previous sections like When and why.
• When defaulting using the value property, if the corresponding attribute LOV doesn't respond, you need to set the default value using the actual value (for example, Action Id, Action Reason Id, Position Id, Business Unit Id).
• A field-level warning message can't be displayed on a read-only field.
• Defining rules using User Defined Tables isn’t supported.
• Attribute LOVs don't function accurately in Design Time if the LOV contains dependent attributes or country tags as in the case of lookup LOVs.
• The null check with initialNumberValue isn't working.
• Any defaulting or validation of the transaction dates based on payroll periods can't be done in 25B. This will be supported in a later release.
• Weekly Working Hours section doesn't support Business Rules defaulting and validations.
• Field-level message support isn't available within the extensible flexfield (EFF) fragment.
• For object-level validation, it's recommended to use the ADF Autocomplete rules.
• The ADF Autocomplete rules for all the add flows will trigger on clicking Submit and not on Continue.
• Any defaulting or validation based on Person addresses isn't supported currently. It will be supported in a later release.
• For number fields, the rules are being created with .$numberValue() and if the value for them is null or undefined, the rule fails. You can modify the rule using Advance expression by replacing $numberValue() with $value().
• Any defaulting or validation based on key flexfields (KFF) isn't supported. This will be supported in a later release.