HPE Content Manager SDK 8.3
|
Accessing a Record is discussed briefly in the help but there are a variety of ways to get a TrimMainObject.
As discussed in the help use the Name or Uri to instantiate the object.
This example fetches a Classification by number.
As can be seen a certain knowledge of the object type is required to fetch by name. For example the name property for each object type is different, for most object types the name property is Name, here is a list of those object types where that rule does not apply:
Object Types | Name Property |
---|---|
ActionDef | ActionName |
AgendaItem | Number |
Alert | Description |
Classification | Title |
Communication | Description |
Consignment | Number |
ConsignmentApprover | Record |
ConsignmentIssue | Record |
History | EventDescription |
Location | SortName |
MinuteItem | Description |
Notification | Description |
OfflineRecord | Title |
Record | Number |
RecordAction | ActionName |
Request | Record |
SavedSearch | FullName |
ScheduledTask | Description |
SharePointItem | UniqueId |
Space | Number |
TodoItem | Description |
UserLabel | FullName |
ZipCode | Postcode |
Even with this information there are still things to be aware of, for example:
There are a number of methods available on the Database object. They key difference between these and the object constructors is that these return null if the object cannot be found where the object constructors throw an exception. These methods are:
Note: The URN property is typically used when you need to persist a database and object type independent identifier for the object.
TrimMainObjectSearch may be used in place of the constructor and Database methods of fetching a document. One benefit when fetching by name, where the name may not be unique, is that you can respond better to the various scenarios.
There are a variety of ways to retrieve an electronic document attached to a Record (or other object type), these are:
Record.GetDocument is the primary way to get an electronic document from a Record and will be used for most .Net SDK applications. It allows the user to fetch a copy of the document from the document store to their local hard drive. If the document is already in the user's cache then it will be retrieved from their rather than from the store.
You may wish to set the Record edit status to checked out without fetching the Record, in this case simply call GetDocument with a null outputDocumentName. For example:
This method of fetching documents was added to better support web services. The advantage it has over Record.GetDocument is that it does not require you to store a new copy of the document, copying it from your local cache to the path in the outputDocumentName parameter. If document store caching is disabled this property will be empty, unless your application is running as a service or web service.
If your workgroup server has document caching enabled an application running on that server (not on a client machines) can use this property to get the Location of the document in the workgroup cache. The benefit of this is that the workgroup server cache can be pre-emptively loaded so the document can be in the cache before event the first time you ask for it.
The DocumentStream class has two advantages over the other methods of getting documents:
DocumentStream is of particular use in web applications where you will want to start downloading the file to the end user as soon as possible rather than waiting until the entire file has been fetched from the document store, and also where you may wish to have a resumable download.
This sample wraps the DocumentStream in a .Net Stream, once you have done this you can use it like any other stream, for example copy it to another stream.
The essential part of using DocumentStream is calling GetAvailabelData(). Remember to use Thread.Sleep() to wait until data has actually returned, the background thread that pulls the document from the document store is probably fractionally slower than your code.
While this document has focused primarily on Records other main and child objects also implement ITrimDocument and therefore also support electronic documents. These objects will at least support the Client Cache method of getting the document and may also implement a method returning an ExtactDocument (such as LocationEAddress )