AD Connector

Step-by-step guide

This guide will show you how to manually kick off an AD Connector workflow in case you need to trigger it before its next scheduled run.

Contents

• Introduction

• Trigger the workflow

• Wait for service to run

• Schedule workflow

Introduction

The Ciphr AD Connector workflows are scheduled to run overnight so it can process the previous days amendments to Ciphr. However, there may be times where you need to manually kick off the process.  

Delayed starter entry: HR adding new starters to the system on the same day they start

Data Sync: It may be that an internal change is made to Ciphr and you need to push out the changes from Ciphr to AD to reflect this as soon as possible.

Trigger the workflow

Go to the following area:

• Login to your AD Connector portal (IT Access only)
• Workflow Configuration > [Workflow you wish to trigger]  > Edit Record

Set the Schedule Type to "Run Once" and click "Save"

Wait for service to run

The local service on your environment will need to ping the newly enabled trigger state, which should happen within ten minutes.

You can see if it has run by checking the Workflow Configuration area. The service will mark the workflow as "disabled" once it has picked up the workflow to be processed.

• Login to your AD Connector portal (IT Access only)
• Workflow Configuration > [Workflow you wish to trigger]  > Edit Record

Schedule workflow

Once you can see the service has kicked off the process and it is processing records you are able to reschedule the workflow back to its original configuration so it runs that night. 

Go to the following area:

• Login to your AD Connector portal (IT Access only)
• Workflow Configuration > [Workflow you wish to trigger]  > Edit Record

Set the Schedule Type to "Advanced" and click "Save"