SK SKYVVA Documentation

License Key for the Automated Process User

Overview

Salesforce uses a special system user called Automated Process to execute background operations such as Platform Events, Scheduled Jobs, Flows, and asynchronous Apex processes.

Unlike standard Salesforce users, the Automated Process user is managed by Salesforce and cannot be modified. Therefore, the license key cannot be stored in the User.CIM_LICENCE_KEY__c field.

To support integrations running under the Automated Process user, SKYVVA allows the license key to be configured in the SkyvvaSetting Custom Setting.


When to Use This Configuration

Configure the license key in SkyvvaSetting if your integration is executed by the Automated Process user.

Examples include:


Prerequisites


Configuration Steps (Salesforce Lightning)

  1. Log in to Salesforce as a System Administrator.
  2. Click the Setup (⚙️) icon and select Setup.
  3. In the Quick Find box, search for Custom Settings.
  4. Open Custom Settings.
image
  1. Locate SkyvvaSetting and click Manage.
image
  1. Click New.
image
  1. Enter the following information:
FieldValue
ValueEnter your valid SKYVVA License Key
image
  1. Click Save.

How It Works

When an integration is executed by a standard Salesforce user, SKYVVA reads the license key from the user's CIM_LICENCE_KEY__c field.

When the integration is executed by the Automated Process user, SKYVVA cannot access a license key from the user record because the user is managed by Salesforce. In this case, SKYVVA automatically reads the license key from the SkyvvaSetting Custom Setting.


image

Notes


Example Scenario

A Platform Event triggers a SKYVVA interface.

  1. Salesforce executes the Platform Event as the Automated Process user.
  2. SKYVVA attempts to validate the license.
  3. Since the Automated Process user cannot store a license key, SKYVVA retrieves the license key from SkyvvaSetting.
  4. The interface continues processing successfully.
Note: This configuration serves as a fallback mechanism for Salesforce system users whose user records cannot be modified. It ensures that integrations executed by the Automated Process user can be licensed and processed successfully.
Open this article in the interactive viewer →