process-mining
2021.10
true
- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Process Mining
Last updated Sep 2, 2024
Tips and tricks
It is possible for multiple records in the input table to be mapped to a single record in the current table. For example, a case has exactly one Case Type, which means that the Case Type value will be the same for every record within a case.
You can use the
any() function to pick one of the records within a case.
This is implemented in the expression
any(records).Casetype.
This can be used in both Lookup expressions and Aggregate expressions.
Note: The record returned from the
any() function is random. Only use this function if you are certain the value of the returned attribute is the same in all records
in the current scope
When developing Aggregate or Lookup expressions you might get an error message stating: “List encountered where a scalar was
expected.” This error means that your expression returned multiple values and you need to select one of them, for example
using the
any() function. However, you should only use this function if it is certain that the value of the returned attribute is the same in all records in
the current scope.
To test whether this is actually the case you can use the
jointext() or listtojson() functions, which will display all the values in the list.
See the illustration below for an example of
listtojson() to inspect the results of a Invoice type lookup.
The Value preview shows that each list consists of one value only. This implies that it is safe to use the
any() function.
