Skip to main content
Close announcements banner

Qlik Sense application rules

Use rule name as top level: If using more than one rule in each category, use rule name as top level to separate them. This will add a new parent node that will contain all entries targeted in the rule as children nodes (or subnodes). Create a containing node, i.e.: you create a rule per stream in Sense and can see them grouped per stream in NodeGraph.

Streams: Name of the stream. Can be “;”-separated and wild-carded.

Tags: Name of the tag. Can be “;”-separated and wild-carded.

Applications: Must be the exact AppID. These can be “;”-separated and wild-carded.

Exclude Applications: Must be the exact AppID. These can be “;”-separated and wild-carded.

Application Category: Choose from the categories created in Categories or create a new category via the built-in sub-menu.

Unmapped data source category: Choose from the categories created in Categories or create a new category via the built-in sub-menu.

Unmapped file source category: Choose from the categories created in Categories or create a new category via the built-in sub-menu.

Add Inline Tables: When enabled, inline tables become visible in the Dependency Explorer.

Include content: When enabled, NodeGraph will gather all sheets, object definitions, master dimensions and expressions through your Sense engine. You can select to community sheets and/or private sheets. Choose from the categories created in Categories or create a new category via the built-in sub-menu.

Information noteA note about Streams, Tags and Applications: these are treated as logically OR. For example, if Streams is *Sales* and Tags is *Europe*, all applications in Sales_NorthAmerica, Sales, Purchase_Europe, and Europe will be matched.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!