...
Moreover, a major option is "The relations" (between entities). You can observe these relations on a report graph where they are depicted with yellow arrows.
...
In this option, you define the following settings: "Source Attribute,” "The relation type" — one or many.
...
"The link query type," which is used to link entities. It's a strict matching or you can use the regular expression (regex). More detailed information can be found in the OpenSearch Lucene syntax documentation.
...
Here you can apply one of the post-processing functions to parse the value you need.
...
With this switcher, you enable or disable the post-processing option. You can also enable linking entities by exact date_time values to get results, for example, only from the same snapshot.
...
For "The Destination Entity" you need to define an entity from a secondary link. And "Destination Attribute" together with "The relationship type."
...
Let's look at this example closer by opening one of the requests in the History Browser. You can find the attribute "nrfsourcedn" and see it contains the direct DN of a role.
...
It has the same format as the role attribute DN. In this case, you don't need to do any transformations.
...
Let's assume you want to link requests with a list of approvers. The DN of approvers is located inside of an XML file, and thus you need to use a post-processing function to parse it. The next step is to paste it and use it as a link from one side. So, you must create a regular expression on the other side.
...
You can see that from the side of requests the "term" query is used, and the "regex" query is used to link secondary entities with the primary/main one. Additionally, the post-processing option is enabled to transform and parse values from the attribute you defined as a link. Let's go to "Filters."
...
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
Should you have any questions or require any assistance, please do not hesitate to contact us at any time swsupport.skypro@skypro.ch