Worker Assignment: Exceptions and Adaptations

There are situations when the Worker Assignment object doesn't act according to the general principles of Autocomplete Rules.

In some other situations when this object doesn't act according to the general principles, you can adapt it by adding a unique additional condition (or coding style, in some cases). These may not be functionally obvious per your requirement but instead, technically required to control for the specific requirement.

Exceptions

This table lists rules that can't be currently implemented for the Worker Assignment object.

Number	Rule	Rule Type	Actions Impacted	Sections Impacted	Fields Impacted	Comments
1	May not use HC as criteria from Work Measure object	Any	All	All	HC	Fix for Work Measure Object coming in upcoming release
2	Cannot set default Assignment Status in Change Assignment	Any Default	Change Assignment	Assignment Details	Assignment Status
3	Cannot Default Working Hours	Object Default	Working Hours	Assignment Details	Working Hours	You may override application default of Working Hours in a Field Modification Rule type but not during first time entry into section with Business Object Default.
4	Cannot Default FTE, HC	Any Default	Any Employment Action	Employment Details	FTE, HC	These fields come from a different object which doesn't support default of these values. you may read FTE from hcmParam FteValue to use as criteria for validation. Work Measure Object fix coming in upcoming release.
5	Several LOV fields don't support Warnings	Field Modification	All Employment Flows	Employment Details	Worker Category, Business Unit, Location, Assignment Status
6	Object Validation doesn't trigger if no flexfield in the section and no field is changed during Global Transfer	Object Validation	Global Transfer Only	Transfer	Absence of flexfield, no predefined field modified	Validation occurs if any seeded field modified; validation occurs if Local Transfer; validation occurs even for Global Transfer if flexfield exists in the section and no field is modified. Oracle reviewing possible fix.

Adaptations

This table lists rules where you can vary the rule logic to achieve the result.

Number	Rule	Rule Type	Actions Impacted	Sections Impacted	Fields Impacted	Comments
1	Must start every rule with "IF WorkTermsAssignmentId NOT NULL"	All	All	All	All	The entire rule must be inside the IF condition. This is to avoid the rule triggering on the deprecated 3-tier employment data model involving Work Terms. Even if you're accessing Assignment from another object. The rest of the rule immediately after declaring row variable access to Assignment must be encapsulated inside this IF condition, even if declaring another onward row variable for lookup info such as Position, Job, BU, Location, and so on..
2	May not use FTE as criteria from Work Measure object	Any	All	All	FTE	must use fteValue hcmParam
3	Fires on multiple records	Any	Convert Pending Worker	Assignment Details	Any	Must select Assignment Type "C", "E", "N", "O", "P" to restrict the record on which you want the rule to trigger.
4	Determining Update vs Correction	Any	All	All	Any	Requires comparison with Existing Assignment including sequence number to differentiate between an Update vs a Correction