What's the difference between Autocomplete Rules and Transaction Design Studio

The Transaction Design Studio enables you to configure the display of fields and sections in the responsive pages based on a fixed set of parameters. Autocomplete Rules is a data model layer-driven application that enables you to default values or validate fields irrespective of whether the fields actually appear in the user interface or not.

Though there are many differences between the Transaction Design Studio and Autocomplete Rules, there is one overlapping functional feature. Transaction Design Studio enables you to specify if a field is required unconditionally or conditionally based on parameters such as business unit, legal entity, and so on. However, Autocomplete Rules can’t determine when to show or hide a field like the Transaction Design Studio, it can simulate the field requirement by enforcing a validation rule with an error message.

This table summarizes the differences between Autocomplete Rules and the Transaction Design Studio.

Autocomplete Rules	Transaction Design Studio
Autocomplete Rules is a data model-driven application.	Transaction Design Studio is based on the UI components.
Autocomplete rules are written based on the underlying business object	Transaction Design Studio is used to configure fields and sections based on an action.
A single rule applies for all actions that use that business object. For example, the When and Why business object applies to Transfer, Hire, Promote, and so on.	You can write a rule only for one action at a time.
There are over a hundred different criteria that you can define in a rule.	There are about 8-10 predefined criteria that apply for each action.