Aegis ‘Depot’ Activity – Value Map

Aegis ‘Depot’ Activity – Value Map

Translating data from one value to another is often a requirement in Aegis.  Aegis itself uses Value Maps in many places including Activities, Input Builder, Events etc. to display Raw data in a User-Friendly format.

For example an event from external system could return a severity field with value 4.  Severity 4 means something.  However if Aegis sends an e Mail to administrator saying an event of severity 4 occurred, does that actually mean anything to the end user?  Different systems will have different severity values, 4 may be high on one system or low on another.  Value Maps help to translate this raw data.

What you'll need:

#1  A Value Map Table, containing 2 columns with Key/Value pairs.     This could be a simple table you build yourself using the 'build data table' activity, or read from a CSV file, or result of SQL query etc.  There are no restrictions on column names.  Tables with more than 3 columns will have columns 3 and above ignored.

#2  The Depot Value Map Activity - Attached!

Here is a simple Aegis table which I will use as a value map for event severity.  It doesn't matter which way you order the columns, the Value Map activity allows you select which column (1 or 2) the Key value is in.


So now we can use the Depot Value Map to decode the event severity value (Screenshot at Run-time) to be presented to an end user:


The Aegis Table is used as input to the Value Map activity.   The 'Key Value' is a variable and comes from an event severity in this case.  'Key Column Number' tells the activity which column contains the Key values, in this case the second column - column names are always ignored.   'Default Value' is the value to be used if the Key is not found in the table - it will also set the 'Value Found' Output to False.

In this case the Key value 4 was supplied, and its corresponding Value 'Fatal' was found and placed in the 'Value' output.   Simple.

Activity Installation Instructions are here:
Labels (1)


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
9 of 9
Last update:
‎2020-01-09 16:45
Updated by:
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.