Skip to main content
Skip table of contents

Custom reports via query console

The LUY query console provides a powerful way to analyze your data with iteraQL. Build personalized queries, traverse the meta model, filter by any attribute, and much more.

  1. Report category:

    1. Create new report

    2. Load existing report

    3. Save Report

    4. Subscribe to current report

  2. Filter category:

    1. Filter the result list

  3. View category:

    1. Add new columns to the result list

  4. Tracking category:

    1. Open the query history

  5. Use for category:

    1. Show result as a diagram. Only the resulting elements are transferred and not the filter or columns.

    2. Show result in list view. Only the resulting elements are transferred and not the filter or columns.

    3. Export result as CSV or Excel

    4. Share query with other users

  6. Text-area input

  7. Execute query and show result

  8. Result of executed query

The most recently executed query is automatically loaded from the user profile when the “query console” page is opened.

Result set

The result of the query is shown as a table at the bottom of the page. Depending on the result type, additional actions are possible similar to the building block list.

Query history

The five most recently executed queries are saved for the user in the query history menu. They can be deleted, copied, or directly executed.

Getting started with iteraQL

IteraQL is the internal programming language which can be used in the “query console” or the “query” REST API endpoint.

1) The elastic model

The iteraQL environment builds up on the elastic data model in LUY. Therefore, the objects appearing in iteraQL are building blocks, properties, and relations. While building blocks are the main elements, properties enhance building blocks with additional attributes and relations making it possible to have building blocks with relations to each other.

2) iteraQL query

IteraQL is used for building individual queries. The syntax tells LUY what part of the model needs to be shown. The list of operators defined for the iteraQL syntax allows to develop queries returning exactly the desired information.

3) The reference sections

The iteraQL reference provides detailed explanations and examples for every operator.

Building blocks, relations and properties

An iteraQL query uses parts of the meta model and combines them with filters and operators. The LUY meta model consists of certain building blocks and relation types. The iteraQL name of each building block or relation type is almost identical to its English name used in LUY, the only difference being the omission of all spaces. For example, the information system domain building block of LUY is depicted as 'InformationSystemDomain'.

The following list provides a reference of all building block and relation types including their attributes:

Building blocks

Building block
(iteraQL Name)

Properties*

Available relations
(iteraQL name)

All Building blbcks

  • id

  • name

  • description

  • lastModificationTime

  • lastModificationUser

  • position

  • $$hierarchy_level$$

BusinessDomain

  • [Accountability]

  • businessFunctionAssociations
    /businessFunction

  • businessObjectAssociations
    /businessObject

  • businessProcessAssociations
    /businessProcess

  • businessUnitAssociations
    /businessUnit

  • informationFlowAssociations
    /informationFlow

  • informationSystemAssociations
    /informationSystem

  • itServiceAssociations
    /itService

  • productAssociations
    /product

BusinessProcess

  • [Accountability]

  • [Strategic value]

  • businessDomainAssociations
    /businessDomain

  • businessMappings (see on the right)

  • informationSystemDomainAssociations
    /informationSystemDomain

  • projectAssociations
    /project

BusinessUnit

  • [Accountability]

  • businessDomainAssociations
    /businessDomain

  • businessMappings (see on the right)

  • informationSystemDomainAssociations
    /informationSystemDomain

  • projectAssociations
    /project

BusinessFunction

  • [Accountability]

  • [Strategic value]

  • businessDomainAssociations
    /businessDomain

  • informationSystemDomainAssociations
    /informationSystemDomain

  • businessMappings (see on the right)

  • projectAssociations
    /project

Product

  • [Rollout date]

  • [Accountability]

  • [Strategic value]

  • businessDomainAssociations
    /businessDomain

  • businessMappings (see on the right)

  • informationSystemDomainAssociations
    /informationSystemDomain

  • projectAssociations
    /project

BusinessObject

  • [Accountability]

  • architecturalDomainAssociations
    /architecturalDomain

  • businessDomainAssociations
    /businessDomain

  • businessMappings (see on the right)

  • informationSystemDomainAssociations
    /informationSystemDomain

  • informationSystemAssociations
    /informationSystem

  • informationFlowAssociations
    /informationFlow

  • projectAssociations
    /project

InformationSystem

  • [Status values]

  • [System size]

  • [Complexity]

  • [Maintenance activity]

  • [Accountability]

  • [State of health]

  • [Costs]

  • [Strategic drivers]

  • [Value added]

  • [Strategic value]

  • [Operating expenses]

  • architecturalDomainAssociations
    /architecturalDomain

  • businessDomainAssociations
    /businessDomain

  • businessMappings (see on the right)

  • informationFlow1Associations
    /informationFlow

  • informationFlow2Associations
    /informationFlow

  • informationSystemDomainAssociations
    /informationSystemDomain

  • infrastructureElementAssociations
    /infrastructureElement

  • projectAssociations
    /project

  • technicalComponentAssociations
    /technicalComponent

InformationFlow

  • [Complexity]

  • [Data exchange]

  • [Degree of automation]

  • architecturalDomainAssociations
    /architecturalDomain

  • businessDomainAssociations
    /businessDomain

  • businessObjectAssociations
    /businessObject

  • informationSystem1Associations
    /informationSystem

  • informationSystem2Associations
    /informationSystem

  • informationSystemDomainAssociations
    /informationSystemDomain

  • projectAssociations
    /project

  • technicalComponentAssociations
    /technicalComponent

ItService

  • [Accountability]

  • [Link to SLA]

  • architecturalDomainAssociations
    /architecturalDomain

  • businessDomainAssociations
    /businessDomain

  • businessMappings (see on the right)

  • informationSystemDomainAssociations
    /informationSystemDomain

  • infrastructureElementAssociations
    /infrastructureElement

  • projectAssociations
    /project

  • technicalComponentAssociations
    /technicalComponent

InformationSystemDomain

  • [Accountability]

  • businessFunctionAssociations
    /businessFunction

  • businessObjectAssociations
    /businessObject

  • businessProcessAssociations
    /businessProcess

  • informationFlowAssociations
    /informationFlow

  • businessUnitAssociations
    /businessUnit

  • informationSystemAssociations
    /informationSystem

  • infrastructureElementAssociations
    /infrastructureElement

  • itServiceAssociations
    /itService

  • productAssociations
    /product

  • technicalComponentAssociations
    /technicalComponent

ArchitecturalDomain

  • [Accountability]

  • businessObjectAssociations
    /businessObject

  • informationFlowAssociations
    /informationFlow

  • informationSystemAssociations
    /informationSystem

  • infrastructureElementAssociations
    /infrastructureElement

  • itServiceAssociations
    /itService

  • technicalComponentAssociations
    /technicalComponent

TechnicalComponent

  • [Available for Interfaces]

  • [Status values]

  • [Manufacturer]

  • [Accountability]

  • [Technical state of health]

  • [Compliance to guidelines]

  • architecturalDomainAssociations
    /architecturalDomain

  • informationFlowAssociations
    /informationFlow

  • informationSystemAssociations
    /informationSystem

  • informationSystemDomainAssociations
    /informationSystemDomain

  • infrastructureElementAssociations
    /infrastructureElement

  • itServiceAssociations
    /itService

  • projectAssociations
    /project

InfrastructureElement

  • [Accountability]

  • architecturalDomainAssociations
    /architecturalDomain

  • informationSystemAssociations
    /informationSystem

  • informationSystemDomainAssociations
    /informationSystemDomain

  • itServiceAssociations
    /itService

  • projectAssociations
    /project

  • technicalComponentAssociations
    /technicalComponent

Project

  • [Accountability]

  • [Costs]

  • [Strategic drivers]

  • [Value added]

  • [Strategic value]

  • businessFunctionAssociations
    /businessFunction

  • businessProcessAssociations
    /businessProcesse

  • businessObjectAssociations
    /businessObject

  • businessUnitAssociations
    /businessUnit

  • informationSystemAssociations
    /informationSystem

  • informationFlowAssociations
    /informationFlow

  • infrastructureElementAssociations
    /infrastructureElement

  • itServiceAssociations
    /itService

  • productAssociations
    /product

  • technicalComponentAssociations
    /technicalComponent

*Square brackets denote custom attributes present in the demo data set of LUY.

Relations

Relation
(iteraQL name)

properties

Available building blocks
(iteraQL name)

All relations below

  • id

  • lastModificationTime

  • lastModificationUser

BusinessMapping

  • businessFunction

  • businessProcess

  • businessObject

  • businessUnit

  • informationSystem

  • itService

  • product

Ad2BoAssociation

  • architecturalDomain

  • businessObject

Ad2IeAssociation

  • architecturalDomain

  • infrastructureElement

Ad2IsAssociation

  • architecturalDomain

  • informationSystem

Ad2ItsAssociation

  • architecturalDomain

  • itService

Ad2TcAssociation

  • architecturalDomain

  • technicalComponent

Bd2BuAssociation

  • businessDomain

  • businessUnit

Bd2IflAssociation

  • businessDomain

  • informationFlow

Bd2ItsAssociation

  • businessDomain

  • itService

Bf2BdAssociation

  • businessFunction

  • businessDomain

Bo2BdAssociation

  • businessObject

  • businessDomain

Bp2BdAssociation

  • businessProcess

  • businessDomain

Ifl2AdAssociation

  • informationFlow

  • architecturalDomain

Ifl2BoAssociation

  • informationFlow

  • businessObject

Ifl2Is1Association

  • informationFlow

  • informationSystem

Ifl2Is2Association

  • informationFlow

  • informationSystem

Ifl2ProjAssociation

  • informationFlow

  • project

Is2BdAssociation

  • informationSystem

  • businessDomain

Is2IeAssociation

  • informationSystem

  • infrastructureElement

Is2IsdAssociation

  • informationSystem

  • informationSystemDomain

Is2ProjAssociation

  • informationSystem

  • project

Is2TcAssociation

  • informationSystem

  • technicalComponent

Isd2BfAssociation

  • informationSystemDomain

  • businessFunction

Isd2BoAssociation

  • informationSystemDomain

  • businessObject

Isd2BpAssociation

  • informationSystemDomain

  • businessProcess

Isd2BuAssociation

  • informationSystemDomain

  • businessUnit

Isd2IeAssociation

  • informationSystemDomain

  • infrastructureElement

Isd2IflAssociation

  • informationSystemDomain

  • informationFlow

Isd2ItsAssociation

  • informationSystemDomain

  • itService

Isd2ProdAssociation

  • informationSystemDomain

  • product

Isd2TcAssociation

  • informationSystemDomain

  • technicalComponent

Its2IeAssociation

  • itService

  • infrastructureElement

Its2TcAssociation

  • itService

  • technicalComponent

Prod2BdAssociation

  • product

  • businessDomain

Proj2BfAssociation

  • project

  • businessFunction

Proj2BoAssociation

  • project

  • businessObject

Proj2BpAssociation

  • project

  • businessProcess

Proj2BuAssociation

  • project

  • businessUnit

Proj2IeAssociation

  • project

  • infrastrutureElement

Proj2ItsAssociation

  • project

  • itService

Proj2ProdAssociation

  • project

  • product

Proj2TcAssociation

  • project

  • technicalComponent

Tc2IeAssociation

  • technicalComponent

  • infrastructureElement

Tc2IflAssociation

  • technicalComponent

  • informationFlow


Self-Referencing Relations

The following table depicts the naming convention for each self-referencing relation in both directions.

Relation

Names in iteraQL

Hierarchy 

  • parent

  • children

Usage 

  • baseComponents

  • parentComponents

Specialization 

  • generalisation

  • specialisations

Successor 

  • successors

  • predecessor

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close