Creating an extended integration for UKG Pro WFM users

Sync Oomnitza with UKF Pro WFM to gain visibility of user data.

Before you start
Information required for the integration
Credentials
Adding the integration
Mappable fields
Launching the integration

Before you start

To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application.

Creating integration users

Information required for the integration

Integration

Base URL. The format of the base URL is https://<tenant-name>.mykronos.com which vary depending on region, environment, and module. For example: https://myteantname.prd.mykronos.com.

Add the value as a global variable so that when you create workflows that use presets the variable is automatically added. See Adding global settings.

The name of the global variable is UKG.Base URL.

Credentials

See Authentication and security and Quick start.

Base URL
Username and Password
Client ID and secret

Adding credentials

Make life easier and add your credentials to Oomnitza before you create the integration.

In Oomnitza, click Configuration > Security > Credentials.
Click Add new credential (+).
Search for the integration, and then click the forward arrow > to select the integration.
Enter your client credentials and any other additional information.
Click Authenticate. You are prompted to log in to authorize your request.
Click CREATE.

Adding the integration

Creating the integration

In Oomnitza, click Configuration > Integrations > Overview.
Click Block view .
On the Integrations page, scroll down to the Extended section for user integrations.
Click NEW INTEGRATION.
In the sidebar, search for the integration.
Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

User only. Add user records.
User plus SaaS user. User records and SaaS user records are retrieved. User records are displayed on the People page and SaaS user records can be accessed when you open the SaaS application record on the SaaS page and click the Users tab. In addition to retrieving information about the SaaS application such as usernames, you also retrieve key information such as the user's SaaS role and last activity which will enable you to reduce costs by monitoring SaaS usage and removing users who aren't using the SaaS application. To maintain data hygiene, you can enable the deactivate feature.
Software SaaS Selection. Link the vendor application to the Oomnitza Software Catalog which is a repository of supported vendor applications and services. If an entry for the vendor application is not shown in the list, it means that the vendor application has not been added to the SaaS page in Oomnitza and linked to the catalog. See SaaS details overview. You can ignore this field because the vendor application is automatically linked to the catalog when the integration is saved.

Important
Now that user information can be retrieved and users deactivated when the integration is run, you can deactivate or remove the workflows that were added to retrieve SaaS user information and deactivate SaaS users. (The block that is used to complete these actions in workflows is the SaaS User Role Retrieval block.)

When you enable the Deactivate feature, the following actions are completed when the integration runs:

If a user record is missing from the data source - the vendor application - or if the record is marked as inactive in the data source, the user record is deactivated in Oomnitza.
If a user record was deactivated and is now available in the data source, for example, the user logs into the SaaS application, the user record becomes active in Oomnitza.

Installation types

Cloud. Store credentials in the Oomnitza cloud.
Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAuth authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication.

Integration preferences

Create & Update. Add and update records.
Create only. Add records.
Update only. Update records.

Editing the integration details

When you edit the Integration details section, you can select the name or names of integration contacts. Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.

Click Edit .
Make your changes.

Editing the credential details

If you selected Cloud as the installation type, choose one of the following options:

Select the credentials that were created for the integration.
Edit the credentials that were created for the integration.
Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

Click Edit .
Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit .

Select Edit integration to add rules for syncing data. Filtering integration results.

You can add new fields to your integration by selecting Add new field on the mapping page.
Creating custom API fields.

Mappable fields

Account Locked
Connector Sync Time
Email
Employment Status
First Name
Full Name
Id
Last Name
MFA Required
Pay Rule Name
Person Key
Phone Number
SSO Username
Supervisor Name
User Account Status
Username

Drag and drop

You can map additional fields to Oomnitza.

Drag and drop the fields onto the Add new Oomnitza field area in the Oomnitza column.
Rename the field.
Make your changes.
Save your changes.

Selecting sync keys

You must select at least one field as the sync key field. To ensure that the sync runs successfully, the field must contain unique values such as the serial number of an asset record or the email address of a user record. Records that do not contain a value for the sync key are skipped.

See Configuring multiple sync keys.

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration.

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab.

Contents