| Appanvil karma designer | ||||
|---|---|---|---|---|
|
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
...
This is a complex report that has many entities, linkages, and all kinds of filters as well as enabled postprocessing. Let's start from "Report properties".
...
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
So, in this tab you can define "The Report ID", "Display Name", and "Description".
...
Tags can also be added. With tags you will be able to filter reports and put them into custom reports submenus.
...
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
One of the most important settings is "The Main index name".
...
Okay, the entity here, which will be used as the main one, can be defined only when you create at least one entity in the "Entities" tab. This main entity serves as the root of all reports.
...
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
"Default sort attribute" and "The Sort order - ascending or descending. Here you define the number of objects which will be displayed on the page. It's required for the pagination. And here you can enable or disable the "Show Flat result" option. You can learn more about this option in our previous videos.
For the setup of "The default time shift" are used the following values: days, weeks, months, and years. "Days" is set as a default time shift which will be applied to a date picker in the filtering stage. Here are "Round date-time value", "The default round date-time metric" and "The Slice load". If you have a report that includes many secondary entities and you need to display a large number of attributes with long strings, as well as you have many post-processing functions to transform results, then you will benefit from using "The Slice load" option which increases performance and prevents the reporting system from crashing. With this option enabled, records will be loaded to the resulting table by bulks the size of which you define in the setting right next to this one. Moreover, you can also limit the size of data to be shown on the front-end, since some browsers don't process big sizes of data on front-end. Let's go to the second tab "Entities".
...
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
"Entities" is a powerful tool that allows you to link different objects not only from types of indices but also from different indices. For example, for snapshots from eDirectory and Active Directory to link data from snapshots with data from events, from events changes, and so on.
...
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."
...
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
In ACDI there is a plethora of basic filters. Let's go through all of them.
...
Let's go to the "Result Table Attributes."
| Anchor | ||||||
|---|---|---|---|---|---|---|
|
| Appanvil karma designer | ||||
|---|---|---|---|---|
|
Here you need to define a list of attributes to be displayed in the final report.
...
OK, here is the list of entities for the final report and its values.
...
Please take into account one small thing: for secondary entities to be displayed in the final report, you must add a special attribute for an entity and enable the "Use attribute for entity object" option using the switcher here.
...
With enabling this option, you will get a column with the alias name and all data for secondary entities, but it will be divided into different columns if you enable the flat format. Now let's go through all settings for "Result Table Attributes."
...
The first setting is "Name of the Attribute." Then it's followed by "The Entity Name" from which the attribute will be taken. Here you also see "The Alias name for the attribute" which will be displayed in the header of a column. Switcher for enabling "Use attribute for entity object. "Data source name" — currently there is only the "OpenSearch" option available. The "Hide from the result" option works by hiding this value from the results table, but it can be used later for post-processing if you need the values of this attribute to make some calculations and display the outcome based on the values of this attribute.
Here is the post-processing function switcher, and the option for "Pass full record object to the postprocess function." You can learn about post-processing in the respective video on the SKyPRO Academy page. "Field width" in pixels — here you define the minimum width of a column in the web interface in the report results table. There is also the "Achieve left side fixed columns by setting fixed property" option.
...
The last tab — post-processing — is described in one of our previous videos.
...
Thank you for your attention and take care.
Should you have any questions or require any assistance, please do not hesitate to contact us at any time swsupport.skypro@skypro.ch