# 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.

{% hint style="info" %}
**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 at the Command Center. If the card is collected in person, an active credential is created.
{% endhint %}

## Prerequisites configuration&#x20;

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:

{% stepper %}
{% step %}

### [Notification Email Templates](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/email-templates.md)

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 specific to a workflow, while others are versatile. The emails utilize variables to personalize the content, ensuring tailored messages. &#x20;
{% endstep %}

{% step %}

### [Create new workflow ](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/creating-a-new-workflow.md)&#x20;

To create a workflow from a template, first manually create an empty workflow.
{% endstep %}

{% step %}

### [Import a template ](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/working-with-workflow-templates/importing-workflows.md)

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.&#x20;

<figure><img src="/files/U9wbzKVPA1bvHHCyrs7j" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Step configuration: *Data Initialisation* &#x20;

Open the workflow in the [edit mode](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/editing-a-workflow-version.md) and find the [Data Initialisation step](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/data-initialisation-step.md). This step, aims to configure all necessary fields and values required for the workflow before executing the process.&#x20;

{% hint style="info" %}
Data Initialisation step is where you link the workflow template to the prerequisite elements you configured in the previous steps. Learn more about the [Data Initialisation step configuration](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/data-initialisation-step.md).&#x20;
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/yXkJziGyE6Td8uHoYlFq" alt="" width="266"><figcaption></figcaption></figure></div>

#### Data Setup tab&#x20;

**Click** on the step. It displays the step's configuration in the side panel.&#x20;

Find the step's **Data Setup** **tab**. Steps and fields needing 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. Remember to always **Save** your changes.&#x20;

{% hint style="warning" %}
To learn how to reference the **Command Centre PDF IDs and Card IDs** in AccessNow, follow these instructions: [Command Centre PDF & Card Type IDs](/command-centre/accessnow-user-guide/help-resources/command-centre-pdf-and-card-type-ids.md)
{% endhint %}

<table><thead><tr><th>Field Name</th><th width="131.748779296875">Value type</th><th>Value</th></tr></thead><tbody><tr><td>UniqueUserPdf</td><td>String</td><td>Please provide the <a href="/pages/Q8ZBe78gUpYN1tmHXtbV">Command Centre PDF ID</a> that uniquely identifies the cardholder.</td></tr><tr><td>RequestFailedEmail</td><td>Email Template</td><td>Select the email template for notifying users when a request fails due to a system error.</td></tr><tr><td>FilterCardType</td><td>String </td><td>The template activates just the selected credential type. You choose the type using this field. Replace "xxx" at the end of the reference link with the <a href="/pages/Q8ZBe78gUpYN1tmHXtbV#card-type-id-values">Card ID</a> from the Command Centre. The template activates just the selected credential type. </td></tr><tr><td>CardTypeName</td><td>String</td><td>Enter the label used for the Cart Type in the Command Centre. For example: Desfire</td></tr></tbody></table>

Remember to **Save** your changes.&#x20;
{% endstep %}

{% step %}

### [Test the workflow ](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/testing-a-workflow-version.md)

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

{% step %}

### [Publish the workflow](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/publishing-a-workflow-version.md)

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/working-with-workflow-templates/activate-access-card.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
