How the Manage Assets UI is assembled

The header is part of the solution template code. You can change the header according to your organization’s branding guidelines.

The toolbar in the Manage Assets UI is made up of building block and solution template components.

The New drop-down list in the toolbar is provided by the solution template. It enables users to create new assets.

The Action toolbar (adobe-amg-flex-presentation.swc) is part of the Asset Manager building block. It enables users who have appropriate permissions to take pre-configured actions on selected assets.

The Preview drop-down list is provided by the solution template. It is added to the toolbar by extending the standard Asset Manager toolbar. The Preview drop-down list appears only for letter assets.

The View drop-down list is provided by the solution template. It enables users to select the type of asset that they want to display in the search results viewer.

The basic search pod (adobe-amg-flex-presentation.swc) is part of the Asset Manager building block. It enables quick basic search on the currently selected asset type.

The Advanced search button is provided by the solution template. Clicking this button opens the Advanced Search pod.

The search results viewer (adobe-amg-flex-presentation.swc) is part of the Asset Manager building block. It is used to display search results.

The Advanced search pod (adobe-amg-flex-presentation.swc) is part of Asset Manager building block. It enables advanced search using multiple search criteria.

Clicking certain actions in the Manage Assets toolbar launches various editors. The Data Dictionary Editor (adobe-dct-widgets.swc) is part of the Data Dictionary building block. The other editors (adobe-acm- presentation.swc) are part of the Asset Composer building block.

Each building block provides its own styling SWC file:

• Asset Manager: adobe-amg-flex-presentation_styles.swc

• Asset Composer: adobe-acm_styles.swc

• Data Dictionary: adobe-dct-widgets_styles.swc

To change the style of building block components, replace the styles SWC file for that project with one containing new styles.

The Manage Assets UI interacts with the building block components in the following ways:

• Register asset handlers: The solution template registers AssetHandlers for various asset types in AssetHandlerRegistry when the application is initialized. These handlers are provided by the Asset Composer building block.

• Glue code to combine various Asset Manager UI pods: The solution template puts together Manage Assets UI by gluing together various Asset Manager, Asset Composer, and Data Dictionary building block components described earlier in this section. The solution template creates an overall toolbar as described in the “Toolbar” section.

  Whenever a user selects a different asset type from the View drop-down list, the UI changes the activeAssetType of the search results viewer, search pod, and toolbar so that these components can re-render as per the currently selected view.

  The Manage Assets UI also creates the instance of SearchManager and glues it into the search pod and search results viewer to enable search and display of search results.

• Action Handling and Event Propagation: Whenever a user selects assets in the search results viewer, gluing components pass this list of selected items to the AssetHandler of the current asset type through AssetHandlerRegistry. The asset handler can enable or disable certain actions based on the selected items.

  When the user clicks an action in the toolbar, the search results viewer dispatches an AssetActionEvent with selectedItems and action as event payload. The gluing code pushes this event into the appropriate handler with help of the handler registry.

  Once the event is in the handler, the handler creates the respective domain model and sets that as the working asset for that handler. Once the handler is finished processing, it dispatches a “launchEditor” event. The Manage Assets UI listens for this event and launches the EditorWindow. EditorWindow opens the appropriate editor which works on its domain model, prepared by the handler.