Aegis ‘Depot’ Activity – Aegis Namespace Query

Aegis ‘Depot’ Activity – Aegis Namespace Query

The Aegis Namespace Query Activity runs the same type of query as in the Namespace Browser, only as part of an Aegis Workflow.  If you haven’t used or don’t know how to use Namespace Queries, this Activity isn't for you!  This activity is to be used with caution.

Ordinarily, the Aegis Find Objects activity is used to find objects and their attributes in the Aegis Namespace.  However, not all attributes in the Namespace are available in the find Objects.  However you've possibly like me hit situations where the object classes which are hidden from Find Objects are just what you need!

Please note – Namespace Query Syntax is a topic in itself and isn't covered here.

For Example for the PG Namespace :  (incomplete … the list can't fit on my screen…)


The corresponding objects are not all available under Find Objects:


So clearly if we wanted to pull auditing info for example, we can't do it via find objects.

Of course this is by design, but sometimes a use case does come up where you need to access the data.  For the PG example you could run SQL queries to access the data … there is nearly always an alternative in Aegis.

So lets say for example that for a given event, you want to return a list of workitems it is associated with, and the type of association – was it initiated / appended etc.

The Namespace Query used in the activity which you can build and test in Namespace Browser is:

SELECT PG_Event2WorkItemAssociation.iqcimRhsAssociate, PG_Event2WorkItemAssociation.pgMappingFlags FROM PG_Event2WorkItemAssociation (PG:'/PG_TopLevelContainer=PG')  WHERE PG_Event2WorkItemAssociation.iqcimLhsAssociate -EQ 'SIGEA-MULTI2##QDB:16527';

Please note - this is NOT SQL 🙂

The value ‘SIGEA-MULTI2##QDB:16527' is the unique event identifier, in this case an event from NetIQ AppManager, and would be a variable value in a workflow.

The results are returned to Aegis in Table format:


As you are access namespace data directly, it may not always be in exactly the format you want.   For the above results neither the workitemid or the association type is in the format we want.  Typically we would use the 'Match Nth Match of Regular Expression' to parse the workitemid from the namespace path.  The association type is data needs to be mapped to its corresponding text value - check out the 'Value Map' activity for how to handle this.

Any query you can run in Namespace Browser you should be able to run in the activity – If you can’t let me know – Have fun!

Activity Installation Instructions are here:


NetIQ does not test or validate any software, code or other materials provided in, on or through NetIQ Cool Solutions (collectively, "Materials"), so please use caution when downloading or accessing any Materials from Cool Solutions and ensure that you have reasonable and current security, spyware and anti-virus measures in place on your computer and/or network prior to downloading. Additionally, do not use any Materials downloaded from Cool Solutions in any production environment without first testing the Materials to ensure they are compatible with your version of NetIQ software or any other hardware or software present in your network or environment. Cool Solutions is not a substitute for authorized NetIQ support and should not be used as such. NETIQ COOL SOLUTIONS AND ANY MATERIALS ARE PROVIDED ON AN AS-IS, AS-AVAILABLE BASIS WITHOUT ANY WARRANTY OF ANY KIND. By downloading this file, you are agreeing to these terms of use. To report a problem please contact: Your use of Cool Solutions is governed by the Cool Solutions Terms and Conditions.
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.