Best Practices for Defining Autocomplete Rules

Defining and implementing rules in Autocomplete doesn't have to be a challenging task. The key is to follow some of the best practices specified here.

• Start with the business object and rule type specified for approved use cases.

• Read key features and limitations of the rule type.

• Read the exceptions and adaptations for the selected business object for the specific business object.

• Restrict your rule logic for a specific action and channel (UI or HCM Data Loader).

• Don't define variables to only store values of fields of any business object as is.

• Most date validations must be done on the When and Why business object, if your action has this section.

• Think of the criteria for defaulting or validation Don't rely on fields on the business object. Always think of the UI, section in which the user needs to enter the value, the business object that supports that section, navigation to that business object from the one you're on. Refer to the chapter, Business Objects in Autocomplete for more information.

• Always build your rule incrementally. First test for event, then display values, including hcmParams.

• Avoid too many nested IF conditions. Consider using duplicate rule, descriptive flexfield setup, and object functions.

• Use debugging techniques, if necessary.