- 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 dashboards
- 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
Cause
This usually happens when the developer did not create a workspace on a newly created branch. It is also possible that the branch was created in a different repository.
Solution
Create a workspace on the newly created branch. If the branch is not visible in the repository, check the other repositories.
Cause
The Superadmin settings have changed.
Solution
When changing the Superadmin settings a refresh of the page is needed to see the results of the changes. Press F5 to refresh the Superadmin page.
Cause
Most likely the URL that is used to access the Superadmin page is incorrect.
Solution
/?page=superadmin
is in the URL. You can also verify the title of the login box. This must be </> Superadmin login. See illustration below.
superadmin
in the URL must be all lowercase!
Cause
Most likely the folder is accidentally created within a different folder. It can be difficult to create folders in the root especially in some of the Superadmin tabs.
Solution
When creating a folder, make sure that you have selected the root. You can also check which folder is selected after the new folder is created. You can drag and drop folders to the correct location after creation.
See The Superadmin Page.