Input tables of the Basic Connector

Introduction

This section contains an overview of the attributes for each of the input tables of the Basic Connector. For each attribute, the name, a description, the usage in AppOne, and an indication of whether the attribute is mandatory is displayed.

The Usage in AppOne column lists how the attribute is used in AppOne:

Selectors are used on dashboards to specify how the metrics are split up.
User filters can be added by end-users to further analyze the data.
Process graph indicates that the attribute is used to draw a process graph.
Details dashboard indicates that the attribute is used in the details dashboards.

Cases and Events

BasicConnector-SingleFile

The BasicConnector-SingleFile expects the data for cases and events both available in one input file which will be loaded into the Cases_events_Input table.

Below is a description of the attributes in the Cases_events_Input table.

Attribute name	Description	Usage in AppOne	Mandatory/Optional
Activity	Name of the activity which happen in an event. For example, pay invoice, or check contract conditions.	• Selector • User filter	Mandatory
Amount	An (often) numerical value associated with a case. For example, this could be the invoice amount in the case of invoices.	User filter	Optional
Case	While Case ID is used to track a case throughout the process it might not be a recognizable number. The Case attribute can be used to give a case a more end-user friendly number or name.	User filter	Optional
Case department	The department responsible for the case.	• Selector • User filter	Optional
Case ID	Case ID is a unique identifier per case, it is used to track a case throughout the process	• Selector • User filter	Mandatory
Case type	An attribute which allows for grouping or categorizing the Case or Case ID attribute, for example, simple cases, and complex cases.	• Selector • User filter	Optional
Case owner	The owner of the case, often the person or responsible for the case.	• Selector • User filter	Optional
Country	The country in which the activity took place.	• Selector • User filter	Optional
Event end	The time or time stamp on which the event ended.	• Process graph • User filter	Mandatory
Supplier	The supplier associated with the case. For example, if a person sends an invoice it could be the associated company which is the employer of the person.	• Selector • User filter	Optional
Supplier Type	An attribute which allows for grouping or categorizing the Supplier attribute. For example, quick supplier, and slow supplier.	• Selector • User filter	Optional
Team	The team or department which is associated with the activity.	• Selector • User filter	Optional
User (input)*	The user which is associated with performing the activity.	• Selector • User filter	Optional
Event ID (input)**	Event ID is a unique identifier per activity. It can be used for other purposes such as due dates.	User filter	Optional

\* User (input): the User expression anonymizes the user names. If you want to show the actual user names, you must configure this in the User expression. \** Event ID (input): if you want to use Due dates in AppOne the Event ID is needed. If your input data does not contain the Event ID (input) attribute, the Event ID (internal) expression creates a unique Event ID.

See illustration below for an example CaseandEvent.csv input file of the BasicConnector-SingleFile.

BasicConnector-TwoFiles

The BasicConnector-TwoFiles expects the data for cases and events from separate input files. The data will be loaded into the Cases_Input and Events_Input tables.

Below is a description of the attributes in the Cases_Input table.

Attribute name	Description	Usage in AppOne	Mandatory/Optional
Supplier type	An attribute which allows for grouping or categorizing the Supplier attribute. For example, quick supplier, and slow supplier.	• Selector • User filter	Optional
Supplier	The supplier associated with the case, for example if a person sends an invoice it could be the associated company which is the employer of the person.	• Selector • User filter	Optional
Case type	An attribute which allows for grouping or categorizing the Case or Case ID attribute. For example, simple cases, and complex cases.	• Selector • User filter	Optional
Case ID	Case ID is a unique identifier per case, it is used to track a case throughout the process.	• Selector • User filter	Mandatory
Case department	The department responsible for the case.	• Selector • User filter	Optional
Case owner	The owner of the case, often the person responsible for the case.	• Selector • User filter	Optional
Case	While Case ID is used to track a case throughout the process it might not be a recognizable number. The Case attribute can be used to give a case a more end-user friendly number or name.	User filter	Optional
Amount	An (often) numerical value associated with one case. For example, this could be the invoice amount in the case of invoices.	User filter	Optional

See illustration below for an example Cases.csv input file of the BasicConnector-TwoFiles.

Below is a description of the attributes in the Events_Input table.

Attribute name	Description	Usage in AppOne	Mandatory/Optional
Activity	Name of the activity which happen in an event. For example, Pay invoice, or Check contract conditions.	• Selector • User filter	Mandatory
Case ID	Reference to the Case ID attribute mentioned in Cases_input.		Mandatory
Country	The country in which the activity took place.	• Selector • User filter	Optional
Event end	The time or time stamp on which the event ended.	• Process graph • User filter	Mandatory
Team	The team or department which is associated with the activity.	• Selector • User filter	Optional
User (input)*	The user which is associated with performing the activity.	• Selector • User filter	Optional
Event ID (input)**	Event ID is a unique identifier per activity. It can be used for other purposes such as due dates.	User filter	Optional

* User (input): the User expression anonymizes the user names. If you want to show the actual user names, you must configure this in the User expression.

** Event ID (input): if you want to use Due dates in AppOne the Event ID is needed. If your input data does not contain the Event ID (input) attribute, the Event ID (internal) expression creates a unique Event ID.

See illustration below for an example Events.csv input file of the BasicConnector-TwoFiles.

Attribute name	Description	Usage in AppOne	Mandatory/Optional
Tag type	An attribute which allows for grouping or categorizing the Tag attribute. For example, rework, or violation.	• Selector • User filter	Optional
Tag	The name of the tag. For example, SLA violation.	• Selector • User filter	Mandatory
Comment	Comment associated with a Tag, that can contain more information about the tag.	Details dashboard	Optional
Tag score	Score associated with a Tag, that can be used to give weights to a tag.	User filter	Optional

Due Dates

Due dates are properties of cases that are important for the process. Due dates are typically defined in the implementation phase by process analysts.

Below is a description of the attributes in the Due_dates_Input table.

Attribute name	Desctiption	Usage in AppOne	Mandatory/Optional
Due date	Name of the due date. For example, Paid on time.	• Selector • User filter	Mandatory

See illustration below for an example Duedates.csv input file of the BasicConnector.

Reference Models

In AppOne functionality to verify existing processes against predefined reference models is available. This enables you to see how many of the cases conform to the ideal processes. Due dates are typically defined in the implementation phase by process analysts.

Below is a description of the attributes in the Reference_models_Input table.

Attribute name	Description	Usage in AppOne	Mandatory/Optional
Reference model	Name of the reference model.	• Selectors • User filter	Mandatory
Trace ID	Unique identifier of different traces which could within one reference model. This can be used when there are multiple paths within one reference model.		Mandatory
Activity	Name of the activity which happen in an event. For example, Pay invoice, or Check contract conditions.		Mandatory