For the complete documentation index, see llms.txt. This page is also available as Markdown.

Activate Access Card

Use Case Overview

The workflow allows a cardholder to activate an access card.

The template activates just one selected physical credential type.

Creating Active vs. Inactive Credentials

The credential request workflow is designed to create both active and inactive physical credentials, depending on the delivery method selected by the requester. For non-in-person collection methods, the card is generated as inactive in Command Centre. If the card is collected in person, an active credential is created.

Prerequisites Configuration

Before configuring this template, ensure the required system entities, such as lists or approver groups, are already set up. This includes pre-configuring the following elements:

1

Notification Email Templates

The workflow automatically sends notification emails at configured points, such as notifying approvers when an approval task is created or informing a requester when a request needs an update or is completed. Email templates for these notifications should be predefined. Some templates are workflow-specific, while others are reusable. The emails use variables to personalise the content and ensure tailored messages.

2

Command Centre PDF List

Import the Personal Data Fields list from Command Centre. This lets AccessNow use cardholder details in the workflow. For example, it can look up the requester cardholder and display relevant details to the requester or approvers.

You only need to import the Command Centre PDF List once. If you already imported it for another workflow, you can skip this step.

3

Command Centre Card Type List

Import the Card Type list from Command Centre. This list defines the physical and mobile credential types available in the workflow. Examples include staff cards, student cards, and digital credentials. These types determine which credentials the workflow can manage.

You only need to import the Command Centre Card Type List once. If you already imported it for another workflow, you can skip this step.

4

Create a New Workflow

To create a workflow from a template, first manually create an empty workflow.

5

Import a Template

Download the template you want to customize and import it into the empty workflow created earlier. After that, you can start customizing your template.

Once the workflow is imported, steps and fields needing configuration are highlighted in red and are also mentioned in the validation messages. Follow the instructions below to configure these steps.

6

Step configuration: Data Initialisation

Open the workflow in edit mode and find the Data Initialisation step. This step configures all necessary fields and values required for the workflow before the process runs.

The Data Initialisation step is where you link the workflow template to the prerequisite elements you configured in the previous steps. Learn more about Data Initialisation step configuration.

Data Setup tab

Click on the step. It displays the step's configuration in the side panel.

Find the step's Data Setup tab. Steps and fields that need configuration are highlighted in red and are also mentioned in the validation message. Follow the instructions in the table below to configure the required fields.

Field Name
Value type
Value

UniqueUserPdf

Select PDF List

Select the PDF that uniquely identifies the cardholder, such as Email.

FilterCardType

Select Card Type List

Select the credential type this template activates from the Card Type List, for example Employee Desfire.

CardTypeName

String

Enter the same card type name selected in the previous field. Type it exactly as it appears above.

RequestFailedEmail

Email Template

Select the email template sent when the request fails because of a system error.

Remember to Save your changes.

7

Test the Workflow

It is recommended to test the workflow before publishing it for use by the system's end users.

8

Publish the Workflow

After testing and being satisfied with the results, publish the workflow to make it available for system users to make requests.

Last updated

Was this helpful?