The Asset Manager includes comprehensive applications for creating and updating items designed to accommodate a variety of usages and internal users. Not only do the functions performed in the application vary by user, but the most efficient process for performing that function may also vary. To that end, the Asset Manager provides several ways to perform certain tasks and permits you to hide the ways that aren’t useful for you.
There are two ways to think about UI customization: exclude the UI elements you don’t need or include only the UI elements you do need. Consider the operation of creating an organization. You can create an organization in the following ways:
In Organizations and Roles view, use the Create New button and select Organizations from the drop-down list.
In Organizations view, use the Create New button and select Organizations from the drop-down list.
From the Users view, select a user, then use the controls on the Orgs & Roles tab to create a parent organization.
Although each operation performs a slightly different function, all assist in creating organizations. Once you have determined the preferred way to perform this operation, you can remove any views, buttons and text boxes that won’t assist you. You can make this change for all users of ATG Personalization or for a specific use, for example, a specific task in a specific workflow.
A second way to think about UI customization is to consider building the UI to offer only the elements that users must use to perform a specific task, workflow, or activity. For a task called Edit Targeting Rules, for example, you might define a UI that removes the User Segments and Content Groups views so only Targeters remains. You might also remove the Basics tab for targeters, so users see the Rules tab in the Details pane only. If you do this, users won’t be able to rename targeters or create new targeters because the controls for those actions are associated with the Basics tab. By building the UI to meet the specific uses of a given task, you reduce complexity and the likelihood of user mistakes.
