Query Forms

Query forms can be created either directly in the AIM-A dashboard or using ISM. For the ISM option, please define a nomenclature for query forms, add node views under information interface, add node lists under views, add node for query forms under the lists which you wish to be displayed in AIM-A, configure query forms and do the class and attribute mappings.

Register configuration

Query Forms go inside Views >> Lists.

For tag query forms, Dataset ="Operational Dataset" needs to be specified and use the dataset and metadata. In this case, we can simply reuse the columns of the tags primary register which are present under InfoInterface->DataSources. ClassCriteria="FCL00014" will take care to bring all the sub classes present under FCL00014 (cable) as well.

For document query forms, use publishQueryForm="true" at the parent level to publish the query forms, use Nomenclature as "QueryForm" for identification purpose. The node names which appear under Lists are the query forms which appear in the AIM-A dashboard. In this case, a query form called "Documents" would appear in AIM-A. Columns may optionally specify Metadata ="id|class|name". ClassCriteria must be set to a class ID otherwise the query form will not be instantiated. In this case, we can simply reuse the columns in the tags primary register which are present under InfoInterface->DataSources. ClassCriteria="GEN_ROOT_DOCUMENT" will bring all of the classes present under GEN_ROOT_DOCUMENT as well.

Example Configuration for Events and Task Query forms:

ISM configuration

For each query form, have a class mapping. In the configurations of the query form we have given classCriteria= classId. Go to the same classId and map QueryForm nomenclature with this classId.

We have given the classId of the Document class and cable class as part of the configurations in the ClassCriteria. With the same classId we are doing the class mappings against the QueryForm Nomenclature.

Attributes you want to bring out in the Query forms need to be mapped too.