Important Note

This space contains files and text snippets that are used throughout the Scheer PAS documentation.
This content is not meant to be read independently from the rest of the documentation.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

ChapterNameExcerpt
Analysis - Filterattribute_filter

Once the basis for filtering has been defined, individual attribute filters can be created:

  • Use the button to create a new attribute filter.
  • Click on the symbol to link attribute filters.

To select an instance attribute, expand the Field selection list.

Analysis - Axis allocationaxis_aggregation

For key indicators on the y-axis the aggregation required can be set using a selection list. An exception here is the number of processes as aggregating these is not appropriate.

Analysis - Axis allocationaxis_aggregation_unit

The choices available are:

  • number
  • total
  • average
  • minimum
  • maximum

Analysis - Axis allocationaxis_allocation_drag

To use an attribute, drag it from the list onto the area of ​​the corresponding axis. Only instance attributes with the matching symbol can be dragged onto the corresponding axis.

Analysis - Axis allocationaxis_allocation_error

If instance attributes of differing levels are mixed, the resulting chart is not meaningful. The wizard therefore displays the following message:

You have combined process level attributes with step level attributes. This allocation does not lead to meaningful results.

Please change your selection of instance attributes. Attributes which match are highlighted in color.

Analysis - Axis allocationaxis_allocation_green

A green frame signals to the user that they are saving the selected instance attribute in the correct axis area.

Analysis - Axis allocationaxis_allocation_intro

You can determine which instance attributes should be displayed in the chart in the axis allocation step. The instance attributes available are listed on the left.

Individual instance attributes are explained in more detail in the Process Mining Glossary.

Analysis - Axis allocationaxis_allocation_list

The two areas for the content of the x and y axis are located on the right hand side of the pop-up window.

  • Dimensions are displayed on the x-axis. They are marked with the symbol .
  • Key indicators are displayed on the y-axis. They can be identified by the symbol.

In distribution charts (all chart types except tachometer), key indicators can also be displayed as a dimension on the x-axis.

Analysis - Axis allocationaxis_allocation_red

The correct allocation of dimensions and key indicators is visually supported. If the user tries to place an instance attribute on the wrong axis, the area will be framed in red.

Analysis - Axis allocationaxis_allocation_time

The unit of time can be set for time-based dimensions. This is applicable to the following instance attributes:

  • end date
  • last update
  • start date

Analysis - Axis allocationaxis_allocation_time_units

The following units of time can be set:

  • year
  • month
  • day
  • hour
  • minute
  • second

Installationcollection_level
Collection LevelDescriptionRestrictions
Custom

Collects everything that has been logged to the transaction log with transaction log level Custom:

Logs everything that is written by the logger adapter (for more details, see BRIDGE Documentation > Log Adapter).

All other logs in the transaction log will be ignored.

Service must at least have transaction log level Custom.
Service

Collects everything that has been logged to the transaction log with transaction log level Service:

Logs the start and the end of calls to a service operation (service interface). For example, calls to SOAP, SAPRFC, or HTTP operations.

All other logs in the transaction log will be ignored.

Service must at least have transaction log level Service.
IO

Collects everything that has been logged to the transaction log with transaction log level IOExternal and IOInternal:

Logs calls of adapters that communicate with external systems like SAP, SQL, SOAP, etc. For instance, the SQL queries that are sent to the database will be logged as well. Calls via the file system and system adapter are excluded.

Logs also calls of adapters to internal (local) resources (file system adapter and system adapter).

Service must have transaction log level IOExternal or IOInternal.

The higher the collection level the more information will be collected and the more data will be stored in the database of Scheer PAS Process Mining. If you do not need to analyze your processes and services down to all IO operations, it is sufficient to set your collection level to e.g. Service to take load of your database server.

However, in case you need to analyze a process or service further down than the collected data allows, you could easily upload the corresponding transaction logs manually with a higher collection level (given that the transaction log level of the service allows that).

But keep the following in mind: If you manually upload a transaction log of a service with collection level e.g. IO whose data has already been collected with collection log level e.g. Service, the already collected data will be doubled. For these cases, we recommend to distinct the manually uploaded logs by e.g. a different host. Otherwise your process or service statistics could get distorted.



Analysis - Filterfilter_basis

In the first field, the selection list is the basis for determining filtering:

  • All: All rules must be met.
  • Any: At least one rule must be met.

Analysis - Filterfilter_contains

Example: Step contains %end%

All instances containing the string end in the step instance attribute will be displayed. Steps in which additional characters appear before or after the string end are also taken into account.

Analysis - Filterfilter_create

If you change the option on the create following filter function, the filter entry is displayed.

Analysis - Filterfilter_duration

Duration periods (process duration, step duration) are entered as whole numbers. A single number is interpreted as meaning a time unit of seconds.

Analysis - Filterfilter_duration_display

After completing the entry, the time units applied are written out automatically.

Analysis - Filterfilter_duration_no

If a time unit entry is not clearly defined, a corresponding message will be shown.

Analysis - Filterfilter_operator_contains

If the contains operator is used, wildcards can be used for entries in the value field. The following placeholders are allowed:

  • _ (underscore): An underscore can be used as a placeholder for any character.
  • % (percentage sign): The percentage sign can be used as a placeholder for any set of character strings.

Analysis - Filterfilter_operator_table

A distinction is made between four groups of instance attributes and the operators belonging to them:

OperatorsInstance Attributes
Value Input

Current step

End event

Host

Process name

Process ID

Start event

Step

manual input*

* Except when operators is defined / not defined

Process time

Step duration

Process count

manual input*

* Except when operators is defined / not defined

End date

Last update

Start date

Calendar (date picker) and manual input of the time *

* Except when operators is defined / not defined and relative filtering

If relative filtering is selected, the following options are available via an additional selection list:

  • last minute
  • last hour
  • last day
  • last week
  • last month
  • last year

user-defined (manual input, see relative filtering )

Event

Steps

Manual input

Analysis - Filterfilter_operators

Depending on the instance attribute selected, various operators become subsequently available. The operators available can be displayed via a selection list.

Analysis - Filterfilter_time_units

Weeks, days, hours and minutes can also be entered using the corresponding abbreviations:

Time units

Permitted entries
(upper and lower case scripts are allowed)

Weekw, week, weeks
Dayd, day, days
Hourh, hr, hour, hours
Minutem, min, minute, minutes
Seconds, sec, second, seconds

The use the abbreviation h for the entry of hours as a unit of time is preferable in order to avoid confusion with the entry of seconds (s).

Analysis - Filterfilter_value

If an operator was selected, the related value can be entered.

The user interfaceload_all

The instance data for all analyses in the Process Analyzer will be reloaded ...

  • ...when the user logs into Process Mining.
  • ...when the F5 key on the keyboard is pressed whilst the user interface is open.

Analysis - Filtermanage_filter

Verwalten Sie Ihre Filter mit Hilfe der drei eingeblendeten Buttons:

  • Drücken Sie den Button , um einen neuen Merkmalsfilter anzulegen.
  • Verwenden Sie den Button , um Merkmalsfilter zu verknüpfen.
  • Löschen Sie einen Filter über den Button .

General tipsmining_authorization

Ein Benutzer von Process Mining ist berechtigt, Analysen für alle Prozesse anzulegen, die in seinen Profilen abgespeichert sind. Wenn einem Benutzer die Berechtigung für ein Profil entzogen wird, kann er auch die darin gespeicherten Prozesse nicht mehr analysieren. Hat er bereits Analysen angelegt, wenn er die Berechtigung für ein Profil verliert, wird die Analyse im Inhaltsbereich mit dem Hinweis Keine Berechtigung, um diesen Prozess zu analysieren versehen.

Hinweis für Administratoren: Das Zuordnen von Berechtigungen und Profilen wird im Administration Guide ausführlich erläutert.

Analysisnote_axis_allocation

The settings possible for axis allocation are explained in detail on the Configuring Axis Allocation page.

Analysisnote_filter_config

Auf der Seite Configuring Filters werden alle Filtereinstellungen näher erklärt.

Installationpa_prerequisites

Parts of Process Mining and of the Platform Services are delivered as a Node.js package. In order to run these, you need a specific Node.js version. Additionally, Process Mining runs some xUML services on a BRIDGE installation.

Please respect the following dependencies:

Process Mining VersionPlatform Services VersionNode.js VersionBRIDGE Version
18.2PAS 1.0 (18.1)8.x7.0.0
18.1.317.46.x6.0.64



Installationplatform_services

Scheer PAS Process Mining will only run if the platform services have been installed and configured. The Platform Services Installation Guide explains how to do this.

Analysisprocess_list

Der gesuchte Prozess wird in der Liste nicht angezeigt? Damit Daten von Scheer PAS BRIDGE bzw. Scheer PAS BPaaS an Process Mining übergeben werden können, muss der entsprechende Prozess mindestens einmal ausgeführt worden sein.

The user interfacereload

Die Instanzdaten einer Analyse werden neu geladen...

  • ...wenn der Filter einer Analyse geändert wird.
  • ...wenn die Achszuordnung einer Analyse geändert wird.
  • ...wenn der Button  gedrückt wird.
  • ...wenn das automatische Neuladen aktiviert ist.









  • No labels