CentraSite 10.7 | CentraSite User’s Guide | Asset Management | Managing Assets through CentraSite Business UI | General Procedures across Assets | Attaching Supporting Documents to Asset
 
Attaching Supporting Documents to Asset
 
Attaching Asset Definition Files
Attaching Documents Using URL
Attaching Documents from Computer's File System
Attaching Documents from Supporting Document Library
Removing Supporting Documents from Asset
Assets include attributes that allow you to associate documents such as a WSDL or schema and supporting documents such as programming guides, sample code and project plan with the asset.
For example, Service assets include the Specification profile. This profile contains several file-related attributes representing external documents such as Functional Requirements, Error Messages, Release Notes, and so forth.
You can attach a document to an asset instance in the following ways:
*You can attach any document on the network that is accessible via a URL.
*You can attach a document from the computer's file system.
*You can attach a document from your organization's supporting document library. The supporting document library is a collection of shareable documents that members of your organization have uploaded to CentraSite's document repository. For more information about the supporting document library, see the CentraSite User’s Guide.
When attaching a document to an asset, keep the following points in mind:
*If you are not the owner of the asset, you cannot attach a document to the asset unless you have Modify permission on the asset (granted though either a role-based permission or an instance-level permission).
*CentraSite relies on file extensions to determine a file's type. When you upload a file from your local machine to the asset, be sure the name of the file on your local machine includes a file extension so that CentraSite can determine the file's type and mark it correctly in the repository.
*When you attach a document to the asset using a URL, CentraSite retrieves the document from the URL and place it in its document repository.
*Make sure that you attach the appropriate type-specific files.