Jobs
Jobs are specific tasks that are executed according to a scheduled time. Raptor has several types of jobs:
Job configuration
Jobs can be found in the Raptor configuration panel in the tab 'Jobs'.
Every job has a status indicated by a color. The colors can be:
Gray: job has not run yet
Purple: a job execution is running
Green: last job execution was finished successfully
Orange: last job execution ran into an error and will retry later
Red: last job execution failed after multiple retries
A job also has a type. Available job types in Raptor are:
D365FO Taxonomy
Retrieves an export from Dynamics 365 F&O and generates tags based on it's contents.
D365FO Users
Retrieves an export from Dynamics 365 F&O and creates Raptor users based on it's contents.
D365FO Kofax Masterdata
Retrieves an export from Dynamics 365 F&O and pushes it as masterdata to Tungsten AP Essentials (formerly Kofax).
D365CE Taxonomy
Retrieves an export from Dynamics 365 CE and generates tags based on it's contents.
D365BC Taxonomy
Retrieves an export from Dynamics 365 BC and generates tags based on it's contents.
Kofax Document Export
Retrieves processed invoices from Tungsten AP Essentials (formerly Kofax) and forwards them to the E-Platform.
Azure AD - Users
Retrieves users from Azure Entra ID (formerly Active Directory) and creates them as Raptor user.
SQL Taxonomy
Retrieves an export from a SQL database and generated tags based on it's contents.
Dataverse Taxonomy
Retrieves an export from Dataverse and generated tags based on it's contents.
Dataverse Kofax Masterdata
Retrieves an export from Dataverse and pushes it as masterdata to Tungsten AP Essentials (formerly Kofax).
SQL Kofax Masterdata
Retrieves an export from a SQL database and pushes it as masterdata to Tungsten AP Essentials (formerly Kofax).
Next to a type and status, every job has:
A unique ID
A cron schedule: this is the schedule for the job execution in the cron-format. Cron schedules can be easily created using the website crontab: https://crontab.guru/
Cron schedules should be set up in a reasonable format. Scheduling jobs in a hyper frequent manner (e.g. every minute 24/7) will result in the job being deactivated. Jobs that proactively generate tags are usually not critical for the working of a production environment, as tags can always created ad-hoc. For these type of jobs we advise a schedule limited of max. 3 times a day, preferably outside business hours or in the weekend.
A service connection (Source): the connection used to retrieve data. See Service connections
A service connection (Destination): the connection used to push data. See Service connections
A service account (On behalf of): this is the Raptor user that will be used to make any API calls to Raptor during the job, if applicable.
Delta packager: the packager service that will be used to retrieve data for the job.
Service connections
Service connections are used by jobs to connect to external services, such as Dynamics 365, Tungsten AP Essentials or a SQL database. Service connections allow you to store credentials in a safe, central place. Updating a service connection will have an effect on all jobs making use of that connection.
Service connections can be found in the 'Jobs' configuration, tab 'Service Connections'.
Creating a service connection
To create a service connection, click the '+' icon. Provide a meaningful name for your connection and select the service type that you will be connecting to. Based on the selected service type, you can choose the purpose of this connection under 'Data'.
Click 'Save' to create the service connection and fill in the required fields.
Dynamics 365 service connections
Connections to Dynamics 365 are made with the OAuth2.0 protocol using an App Registration in Azure. Raptor uses the ID of the client application as well as the secret value and Directory ID. Depending on which Dynamics environment you are connecting to, the app registration may need different API permissions.
Dynamics 365 F&O
For F&O, the app registration needs following API permissions:
Dynamics ERP
AX.FullAccess (Delegated)
CustomService.FullAccess (Delegated)
Odata.FullAccess (Delegated)
Microsoft Graph
User.Read (Delegated)
Dynamics 365 CE
For CE, the app registration needs following API permissions:
Dynamics CRM
user_impersonation (Delegated)
Microsoft Graph
User.Read (Delegated)
Dyanmics 365 BC
For BC, the app registration needs following API permissions:
Dynamics 365 Business Central
API.ReadWrite.All (Application)
Microsoft Graph
User.Read (Delegated)
Last updated