Ident_Salesforce_SLSFContacts_Realtime

Sample workflow to provision a Salesforce Contact from a Identity user (representing the SLSFContact); triggered by an EBR event

A provisioning workflow transfers the account, group and membership changes that DirX Identity has calculated for a target system into the connected system, and acknowledges the result back into the Identity Store. It is the workflow that executes what privilege resolution has decided: when a user gains or loses a privilege, the resolution writes the resulting account or membership change into the target system subtree of the Identity Store, and this workflow applies that change to the connected system.

The workflow processes single requests as they arrive, so it reflects changes with little delay. Use the corresponding validation workflow to detect changes that were made in the connected system outside of DirX Identity.

Ident_Salesforce_SLSFContacts_Realtime is the provisioning workflow for objects of type aSFContact that represent Salesforce Contacts. It is typically triggered by an EBR event and keeps those objects synchronized with the corresponding contact records in Salesforce. The sample parameters identify the target system as sample-ts in cluster <server-address>.

The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.

At a Glance

Name

Ident_Salesforce_SLSFContacts_Realtime

Category

Target Realtime / Salesforce

Technology

Java-based real-time workflow

LDAP object class

dxmIDMWorkflowDefinition

Workflow type

ProvisionTS

Connected system / controller type

aSFContact

Configuration wizard

wf-Provisioning-Synchronize.xml

Active in the factory data

FALSE

Factory data version

8.4

Factory data path

Workflows/Default/Target Realtime/Salesforce/Ident_Salesforce_SLSFContacts_Realtime

Prerequisites

  • A connected directory of type Salesforce, with the bind profile Admin set to a Salesforce account that may create and update contact records and their related assignments.

  • SSL is switched on for the TS port, so the Java-based Server must trust the certificate that is presented by the Salesforce endpoint.

  • A target system of type aSFContact in the Identity Store whose objects represent the Salesforce Contacts that this workflow provisions.

  • The Java-based Server that runs the workflow must be able to reach both Salesforce and the Identity Store.

Workflow and Activities

Activity Type Component description Description Ports

error

error

provisioningActivity

Error Activity

Message

join

ProvisionTS

provisioningActivity

Join activity for the provision-to-TS workflow

event, IdentityDomain, notify, ts

Ports

Activity Port Component description Connector Connected directory Bind profile SSL

error

Message

errorPort

ErrorNotifyMailConnector

-

-

not set

join

event

notificationPort

JmsConnector

-

-

not set

join

IdentityDomain

provisioningPort

LdapConnector

Identity Store

Domain_Admin

not set

join

notify

notificationPort

NotifyMailConnector

-

-

not set

join

TS

provisioningPort

SalesforceConnector

Salesforce

Admin

TRUE

Channels

Table 1. Channels of port IdentityDomain (activity join)
Channel Description Reference type Delta type

members

Channel for members

OneToOne

SearchAttributes

SLSFaccounts

Channel for Salesforce Accounts

OneToOne

SearchAttributes

SLSFcontacts

Channel for Salesforce Contacts

OneToOne

SearchAttributes

SLSFpermissionSets(groups)

Channel for groups (Salesforce PermissionSets)

OneToOne

SearchAttributes

SLSFprofiles(groups)

Channel for groups (Salesforce Profiles)

OneToOne

SearchAttributes

SLSFusers(accounts)

Channel for accounts (Salesforce Users)

OneToOne

SearchAttributes
Table 2. Channels of port TS (activity join)
Channel Description Reference type Delta type

members

Channel for members

OneToOne

SearchAttributes

setPassword

Channel for setting a password

OneToOne

SearchAttributes

SLSFaccounts

Channel for Salesforce Accounts

OneToOne

SearchAttributes

SLSFcontacts

Channel for Salesforce Contacts

OneToOne

SearchAttributes

SLSFpermissionSets(groups)

Channel for groups (Salesforce PermissionSets)

OneToOne

SearchAttributes

SLSFprofiles(groups)

Channel for groups (Salesforce Profiles)

OneToOne

SearchAttributes

SLSFuser(accounts)

Channel for accounts (Salesforce Users)

OneToOne

SearchAttributes

Filters

Port Filter Description Sequence

TS

CryptFilter

decryption

1

Configuration Parameters

Table 3. Workflow parameters of Ident_Salesforce_SLSFContacts_Realtime
Parameter Default value

timeout

P0Y0M4DT0H0M0S

tscluster

<server-address>

tsresource

sample-ts
Table 4. Parameters of activity error
Parameter Default value

resourcefamily

Mail

retrylimit

3

timeout

P0Y0M1DT0H0M0S

waitbeforeretry

P0Y0M0DT2H0M0S
Table 5. Parameters of port Message (activity error)
Parameter Default value

decrypt.attribute

dxmPassword
Table 6. Parameters of activity join
Parameter Default value

resourcefamily

Salesforce

retrylimit

3

timeout

P0Y0M1DT0H0M0S

waitbeforeretry

P0Y0M0DT0H30M0S
Table 7. Parameters of port event (activity join)
Parameter Default value

appid

event

decrypt.attribute

userPassword

jmsprovidertype

MQSERIES

tgtisjmsclient

false
Table 8. Parameters of port IdentityDomain (activity join)
Parameter Default value

decrypt.attribute

userPassword
Table 9. Parameters of port notify (activity join)
Parameter Default value

decrypt.attribute

userPassword
Table 10. Parameters of port TS (activity join)
Parameter Default value

decrypt.attribute

Password

A Java-based real-time workflow runs as a permanently loaded configuration in the Java-based Server (IdS-J). It is triggered by a request or an event rather than by a schedule. Each workflow consists of activities; an activity opens one port per system it talks to, and each port uses a connector to reach that system.

Most provisioning workflows contain a join activity that performs the actual work and an error activity that receives requests which still fail after all retries and sends a notification about them. The retrylimit, waitbeforeretry and timeout parameters of an activity control how often and how long a failed request is retried before it is handed to the error activity.

The event port publishes change events over JMS, and the notify port sends e-mail notifications. Neither port is bound to a connected directory.

The join activity does the provisioning work. Its IdentityDomain port reads the affected aSFContact object and its related Salesforce assignments from the Identity Store, and its TS port writes the corresponding contact state into Salesforce on the matching channels. CryptFilter decrypts protected values before the request is sent to Salesforce.

A request that fails is retried up to 3 times (retrylimit) with 30 minutes between the attempts (waitbeforeretry). If it still fails, the error activity takes it over and sends a notification through the Message port; the workflow parameter timeout gives a request 4 days before it is discarded.

Operation

  1. An EBR event marks the affected aSFContact object in the target system subtree of the Identity Store for provisioning.

  2. The Java-based Server passes the resulting request to the join activity of this workflow.

  3. The IdentityDomain port reads the affected object from the Identity Store over the matching channel.

  4. The TS port creates or updates the corresponding Salesforce Contact and its related assignments.

  5. The result is written back into the Identity Store so that the state of the target system entry reflects what happened in Salesforce.

  6. The event port publishes the change as a JMS event for applications that listen to provisioning events; the notify port sends the configured e-mail notifications.

  7. Requests that fail permanently are handed to the error activity, which reports them by e-mail.

The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario, connect the copy to your connected directory and activate the copy.