process-mining
latest
false
- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- Publishing process apps
- App templates
- Additional resources
Process Mining
Data transformations
With the introduction of unit tests in dbt version 1.8, the
tests: key was renamed to data_tests:. For existing process apps, this results in a deprecation warning that is displayed when running an ingestion or opening
Data transformations.[WARNING]: Deprecated functionality The `tests` config has been renamed to `data_tests`. Please see https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax
for more information.For default process apps, you can rename the occurrences of the
tests: config to data_tests: in the dbt_project.yml and the sources.yml files to fix this. For customized process apps, this can be present in other .yml files as well.
Check out the official dbt documentation on the New data_tests: syntax for more information.
It can occur that the Preview does not change after you changed the query and run the file.
The
sql file is identical to the one in dbt, as it has not been updated since the last run. If you run the file again, no changes will be detected and therefore the
Preview table won't be updated. For example, if you add a WHERE condition and run the file, the Preview will only show the filtered records. However, if you remove this WHERE condition and run the file again, the Preview will still only display the previously filtered records, when it should actually
show all records.
The following warning messages are displayed in the ingestion log.
When you get the two warning messages
The selection criterion "+<file>.state:modified+" does not match any nodes and Nothing to do. Try checking your model configs and model specifications args, it means that no changes were detected compared to the last time the queries were run. The Preview panels are showing the most up-to-date version of the data.
To force a complete re-run of your queries, select Apply to dashboards.
