Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
42 views

<(RM) Support tip> Iron Mountain Warehouse integration data file configuration syntax

Incident description :  

Sites using the HPE RM and Iron Mountain Warehouse integration may need to design the ORD file to ensure it includes the information such as locations who performed the request,  the storage provider locations ect in the ORD file so that the information can be passed to other parties for any further purposes.

Resolution                :

This can be done via editing the content of IromMountain.XML file  >  IMLink section.

 General Rules :

 1, Expression

The syntax for the integration to retrieve different DB data to be put in the ORD file are formed by the delimiters , such as  @(...)  and  @wh(...)@WH(...), and the object name.

The object name is from the TRIM object name in SDK. 

When generating content for the .ORD files, any text enclosed with the delimiters @(...)  is evaluated as C# expressions in the context of each TRIM record request.  The @wh(...)@WH(...) syntax can be used to reference properties of current warehouse as defined in the <warehouse> nodes of the XML config file.

 2,  Details of the TRIM object model and available object properties

Details of the TRIM object model and available object properties, can be found in TRIM SDK documentation. A full list of TRIM objects and properties can be viewed in Visual Studio by analysing the HP.HPTRIM.SDK namespace in the Object Browser. You can also use the @wh(...) syntax to reference properties of the current warehouse as defined in the <warehouse> nodes of the XML config file.@WH(...) syntax to reference properties of the current warehouse as defined in the <warehouse> nodes of the XML config file.

3,  It doesn’t work for User Defined Fields(Additional Fields data)

This only works for property references.  Calling functions will NOT work, and hence it is not possible to access the value of user defined fields on any of the HPE RM objects because that requires use of the GetFieldValue() function.  

4, Examples

@(Requestor.FormattedName)                Requester’s full name

@(Requestor.NickName)                           Requester’s unique name

@(Requestor.PhoneNumber)                   Requester’s phone number

@(Notes)                                                     Notes on request

@(Priority)                                                  Request priority

@(Record.OwnerLocation.NickName)    Requested record’s owner location’s unique name

@(Requestor.Committee.NickName )     Requester’s Committee location’s unique name

@(Requestor.Unit.NickName )                 Requester’s Organization location’s unique name

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.