For example, if a company called M圜orp is building a payroll system, it could use the prefix McPR on all elements added. Consider using a prefix that identifies the company and the solution. This additional prefix will help prevent name conflicts if your solution is combined with work from other sources. When building add-on functionality, in addition to following this naming convention, you should add another prefix that uniquely identifies the solution. The name CustPaymReconciliationImport describes a similar functional area and action for the Customer business area. For example, in the name VendPaymReconciliationImport, the prefix Vend is an abbreviation of the business area name (Vendor), PaymReconciliation describes the functional area (payment reconciliation), and Import lists the action performed (import). Prefixes are commonly used to indicate the team responsible for an element. The business area name is also often referred to as the prefix. With this naming convention, similar elements are placed next to each other. Because there are thousands of elements, it’s important to understand the naming conventions and adhere to them to use the AOT effectively.Īll element names in the AOT use the following structure: Pressing the Right Arrow key expands a node if it has any children.Įlements are arranged alphabetically.
You can navigate through the AOT by using the arrow keys on the keyboard.
0 kommentar(er)
