How You Test Autocomplete Events

You can test these events for correctness before implementing autocomplete rules.

• Object Default: Use the Advanced Debugger tool to test the Object Defaulting event. This is the only way to test the event. You can also use this tool for any type of rule.

• Object Validation: Use a simple rule that unconditionally shows an error message to test whether an object validation rule triggers. You can run the application in the sandbox to test if this works.

• Field Modification: Use a simple rule that unconditionally shows a warning message to test whether a field modification rule triggers. You can run the application in the sandbox to test if this works. You also need to check if the Auto Submit property is enabled for the given field.

• Field Validation: Use a simple rule that unconditionally shows an error message to test whether a field validation rule triggers. You can run the application in the sandbox to test if this works. You also need to check if the Auto Submit property is enabled for the given field.

Test Using Display Variables

After testing the event, you can add an error message that shows the values of various variables in an error unconditionally. This enables you to test if autocomplete rules fetch the correct values of all variables required as criteria for defaulting or validation. You must do this before writing complex IF logic, to use variables to determine precisely when you want the rule to trigger. It's a good practice to always build your rule incrementally.

Assignment as Criteria

You need to check for IF WorkTermsAssignmentId NOT NULL condition when you're using the Assignment business object as criteria within another object such as Salary or Payroll. You must do this before declaring another subsequent row variable to fetch related attributes of Assignment such as Job Level.