icon-arrow-downicon-arrow-cerulean-lefticon-arrow-cerulean-righticon-arrow-downicon-arrow-lefticon-arrow-righticon-arrowicon-backicon-closeicon-commentsicon-correct-answericon-tickicon-downloadicon-facebookicon-flagicon-google-plusicon-hamburgericon-inicon-infoicon-instagramicon-login-trueicon-loginicon-mail-notificationicon-mailicon-mortarboardicon-newslettericon-notificationicon-pinteresticon-plusicon-rssicon-searchicon-shareicon-shieldicon-snapchaticon-staricon-tutorialsicon-twittericon-universities icon-videosicon-viewsicon-whatsappicon-xingicon-youtubeicon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboardinghelp-archivehelp-risk icon-arrow-downicon-arrow-cerulean-lefticon-arrow-cerulean-righticon-arrow-downicon-arrow-lefticon-arrow-righticon-arrowicon-backicon-closeicon-commentsicon-downloadicon-external-linkicon-facebookicon-flagicon-google-plusicon-hamburgericon-hearticon-inicon-infoicon-instagramicon-login-trueicon-loginicon-mail-notificationicon-mailicon-moreicon-mortarboardicon-newslettericon-notificationicon-pinteresticon-plusicon-rssicon-searchicon-shareicon-shieldicon-snapchaticon-staricon-tutorialsicon-twittericon-videosicon-viewsicon-whatsappicon-xingicon-youtubeicon-knowledgeicon-questionicon-events icon-message

View all
Advanced search


This video tutorial provides you with an overview of the structure and functionality of the design view in ARIS Script Editor.

You can define your own ARIS report scripts with the Script Editor. A source code view and the design view shown here are available for this. You don't need any special programming knowledge to create your own report scripts in the design view.

You can use report scripts to define the structure, content, and layout of a report. To do so, the design view provides the columns "Structure" and "Contents". The"Structure" column shows the structure of the report script and the set queries.

In the "Contents" column you define all of the content you wish to output in your report later. Content and layout are displayed schematically in the report script definition with for example, placeholders for the individual query components. The corresponding data is extracted from the respective database items while running the report script and output in the final report.

A report script definition provides headers and footers to display general information about the report. You can insert your own graphics, texts, or text boxes here. Text boxes are placeholders and are automatically replaced by the corresponding content when the report is run, for example, by the current date or the page number. You can insert and arrange the individual items with the help of formatting tables, similar to working with HTML tables.

The main structural elements of a report are sections. In addition to layout components and text boxes, you can insert definable queries, data fields or data tables in sections. You can insert further subsections and thus, structure and link content such as queries hierarchically. For a better overview you can hide individual sections. As a rule, a section has two static areas and a repetition area. The content of a static area is displayed only once when the report script is run. The content of the repetition area is output as often as a query set in this section returns data elements. This means a query for certain data elements can be iterated in the repetition area.

Each section on the top level has a specific query, the so-called context. The context indicates which database elements the other queries in this section can be run on. Thus, the context specifies the database elements that can be queried for this section. In this example the context is "Selected groups". This means, the queries in this section can only be run on groups. You can then select the corresponding groups when running the report.

A subsection inherits the queries from the superior section. In this example, the inserted section inherits the context "Selected groups". Each new subsection is given another query defined by the user. This way, the query of the subsection restricts the queried database elements further. In this example, the model lists are queried for all selected groups. The model lists can be filtered further according to their type. The set filter type is only displayed in the query properties. Here, filtering occurs according to the model type EPC.

The data fields are used to output the relevant values of the queried data elements. A data field consists of several variables that are each separated by a period. The data field starts with the context followed by the individual queries of the subsection and ends with the output value that is then displayed in the report created.

In this example, the data field in the repetition area of the main section outputs the group path for each selected group. The first data field in the repetition area of the subsection outputs the model name for each model found in the respective group. That means, the names of the EPCs found are output by the filter set. The second data field in the subsection outputs the corresponding graphic for each EPC found.

A data table is used to output the values of queried data elements in table format. When you create a data table you define a further query with which the queried data elements are filtered further. In this example, the object definitions for the respective EPCs are queried and filtered according to the type "Function".

The static area of the table is used as a header and is output only once per page. The repetition area of the table is displayed while the report runs as often as the query returns data elements. Thus, in this example, all of the functions of each EPC are listed in a table. In the cells of the repetition area in the data table you can insert the data fields for the relevant output values. Here, the data field in the first column outputs the name of all of the functions of the respective EPC. In the following columns various attributes of each function are output, such as, for example, the description of the function, the average processing time and the costs.

This simple example of a report script definition illustrates the structure and functionality of the design view in ARIS Script Editor. The resulting report could look like this. The report starts with its own cover page followed by a table of content. You can insert both into the report script definition optionally and output them in the report.

Here, you see a section of the report that was output. The heading of the main section outputs the respective group path. The heading with the process names follows in the subsection. The associated EPC is output as a graphic and the functions contained in the EPC are output as a table with the corresponding specified values.

You just learned more about the design view of ARIS Script Editor and saw what a report output based on the example report script definition could look like.