Managing assets in the Central Management component

You can designate Central Management component administrators to manage the assets for your organization. They can manage the directory structure of assets and the remote services preferences for the users who are connected.
Review this list of tips and concepts helpful for managing the assets in the Central Management component:

Viewing asset lists in the administrative user interface

In the sidebar, the tree structure and the filter work together to provide you with a flexible view of the library assets.

Renaming the Central Management component

You can rename the Central Management component from RPE Central Library by clicking Library properties and entering a name in the Name field. When you rename the library, this name is visible to all of the users who connect to the Central Management component to submit or modify assets from the client applications.

Organizing asset folders in the administrative user interface

In the sidebar, when you hover over a folder, you can click the Edit icon to change the name or location of the folder in the tree. You cannot delete, rename, or move the predefined assets folder.

Predefined assets

The Central Management component comes with example assets for you to use actively in your organization or to serve as a model for the kinds of assets that can be submitted to the Central Management component. Predefined assets cannot be deleted or designated as private.

Private assets

In the Central Management component, you can limit the access for a user to certain assets by designating those assets as private. Private assets are assets that can only be viewed from the client applications by the user who created them and the Central Management component administrator.

Because the purpose of the Central Management component is reuse of assets across an organization, the concept of private assets is not that users can create their own personal assets that are only available to themselves, though managing personal assets is possible. The concept of private assets is to give users a process for delivering an asset to the Central Management component even though the asset is still in development. A user can work on multiple computers and still have access to the same asset files as the assets are being developed.

For example, an advanced JavaScript user might be working on a script for a template. As the script is being developed, the user can specify the asset as Private so other users cannot use the asset until the JavaScript has been written and tested.

Public assets

Assets that are not marked private are available to any user who has access to the Central Management component. If you modify an asset, the changes are visible to anyone who views or uses the asset. If you remove an asset from the Central Management component, the asset is no longer available to any user. If an asset is removed that has been used in a template or document specification, the asset cannot be accessed and the document generated is affected. Before removing assets, verify that Central Management component users remove the assets from their templates and document specifications first.

Feedback