Chapter | Name | Excerpt |
---|
Analysis - Filter | attribute_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 allocation | axis_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 allocation | axis_aggregation_unit | The choices available are: - number
- total
- average
- minimum
- maximum
|
|
Analysis - Axis allocation | axis_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 allocation | axis_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 allocation | axis_allocation_green | A green frame signals to the user that they are saving the selected instance attribute in the correct axis area. |
|
Analysis - Axis allocation | axis_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. |
|
Analysis - Axis allocation | axis_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 allocation | axis_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 allocation | axis_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 allocation | axis_allocation_time_units | The following units of time can be set: - year
- month
- day
- hour
- minute
- second
|
|
Installation | collection_level | Collection Level | Description | Restrictions |
---|
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 - Filter | filter_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 - Filter | filter_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 - Filter | filter_create | If you change the option on the create following filter function, the filter entry is displayed. |
|
Analysis - Filter | filter_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 - Filter | filter_duration_display | After completing the entry, the time units applied are written out automatically. |
|
Analysis - Filter | filter_duration_no | If a time unit entry is not clearly defined, a corresponding message will be shown. |
|
Analysis - Filter | filter_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 - Filter | filter_operator_table | A distinction is made between four groups of instance attributes and the operators belonging to them: Operators | Instance 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 - Filter | filter_operators | Depending on the instance attribute selected, various operators become subsequently available. The operators available can be displayed via a selection list. |
|
Analysis - Filter | filter_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) |
---|
Week | w, week, weeks | Day | d, day, days | Hour | h, hr, hour, hours | Minute | m, min, minute, minutes | Second | s, 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 - Filter | filter_value | If an operator was selected, the related value can be entered. |
|
The user interface | load_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 - Filter | manage_filter | |
General tips | mining_authorization | A Process Mining user is authorized to create analyses for all processes that are saved against their profiles. If a user’s rights are removed from a profile, they can no longer analyse the processes stored in it. If they have already created analyses prior to the loss of authorization for a profile, the analysis in the content area is shown with the message No authorization to analyse this process (see Process Mining Support> Error Handling Process Mining ). Note for administrators: The allocation of authorizations and profiles is explained in detail in the Administration Guide. |
|
|
Analysis | note_axis_allocation | |
Analysis | note_filter_config | |
Installation | pa_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 Version | Platform Services Version | Node.js Version | BRIDGE Version |
---|
18.2 | PAS 1.0 (18.1) | 8.x | 7.0.0 | 18.1.3 | 17.4 | 6.x | 6.0.64 |
|
|
Installation | platform_services | |
Analysis | process_list | Is the process you are looking for not showing in the list? In order for data from Scheer PAS BRIDGE or Scheer PAS BPaaS to be transferred to process mining, the corresponding process must have been run at least once. |
|
|
The user interface | reload | The instance data for a single analysis will be reloaded ... |
|