> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-transformation-mapping/card-transformation.md).

# Adding a Card transformation

### Introduction

When a source value is transformed, it can be used to assign a card and define the card's properties.

A Card transformation can be used to modify the properties of a particular card type or the properties of all card types assigned to a cardholder.

Alternatively, a Card transformation can be used to change a cardholder’s card type. When the cardholder is imported, the cardholder’s card type will be changed to that of the card type specified.

### Procedure

1. Create a transformation mapping to the Gallagher Command Centre Cards field.
2. Click the **Add** button to add a transformation. The Add Transformation window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-06ce4221fee0a989f10d8aedd5634e6e94c24d2e%2Fcardtransformation.png?alt=media)
3. In the upper field, enter the source value that identifies the card type you wish to add or update.

   **Note:** This field accepts wildcard characters. Refer to [Wildcard characters](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.md).
4. To assign or modify a single card of this type, ensure the **Add or modify a card of type** radio button is selected.
5. Select the card type you want to assign or modify from the drop down list. The properties of this card will be modified as per the properties below.

   This card type will be assigned to, or modified for, all values that match the transformation in the source data.

   If a card of this type has already been assigned, its properties will be updated.

   **Note:** If you select a GovPass card type additional **Visitor Contractor** fields appear in the Card Properties section (under the **Card enabled** fields). To set the Visitor Contractor, select either:

   * **Not mapped.** When added, the Visitor Contractor will be set to the default, (i.e. Visitor / Contractor = No, Owned by Site = Yes). When updating the card, this value will remain unchanged.
   * **Fixed value.** Select either "Visitor / Contractor" or "Full Rights".

     <table><thead><tr><th width="193">If set to...</th><th>the settings on the Cardholder Cards tile in Command Centre Client will be...</th></tr></thead><tbody><tr><td>Visitor / Contractor</td><td>Visitor / Contractor = Yes, Owned by Site = Yes</td></tr><tr><td>Full Rights</td><td>Visitor / Contractor = No, Owned by Site = Yes</td></tr></tbody></table>
   * **Source data field.** Select the appropriate source data field value.

     <table><thead><tr><th width="193">If value is...</th><th>the settings on the Cardholder Cards tile in Command Centre Client will be...</th></tr></thead><tbody><tr><td>Either 1 or True</td><td>Visitor / Contractor = Yes, Owned by Site = Yes</td></tr><tr><td>Either 0 or False</td><td>Visitor / Contractor = No, Owned by Site = Yes</td></tr></tbody></table>
6. To modify all cards of any type assigned to cardholders, select the **Modify all cards** radio button. The properties of all existing cards on the cardholder will be modified as per the properties below.
7. To modify a card type (excluding specific card types), select the **Modify a card that is not of type** radio button, then select the card types that will not be modified.
8. To set the card number, select either:
   * **Auto**. When added, a card number will be automatically generated. When updating the card, the card number will remain unchanged. Only one card of this type should exist on the cardholder, when specifying "Auto". Otherwise the card number must be supplied in the source file.
   * **Source data field**. Select the source field to retrieve the card numbers from.
   * If the source field contains a blank value, the cardholder record will fail to import.
   * If the source field contains a non card number value, (text, negative number or out of range) the cardholder record will fail to import.
9. To set the card enabled From date and card enabled Until date, click the From or Until date drop down arrow and select either:
   * **Not mapped**. When added, the date and time will be set to the default card type date and time. If a date and time has already been set, this value will remain unchanged.
   * **Fixed date**. Enter a date and time. The Until date and time must be greater than or equal to the From date and time.
   * **Source data field**. Select a source field to retrieve the date and time from.

     If you wish to specify a fixed From time or fixed Until time, check the "Use a fixed time of" check-box and enter a time. This time will override the time specified by the source field.
   * If the source field contains a date but not a time and the "Use a fixed time of" check box is unchecked, the time will be set at 0:00 hours on the From date and 0:00 hours on the Until date.
   * If the source field contains a time but not a date, then today's date will be used.
   * If the source field contains a non date value, the cardholder record will fail to import.
   * If the Until date and time is less than the From date and time, the cardholder record will fail to import.
   * If the source field contains a blank value, the From or Until date and time will not be set.
10. To enable or disable the card, select either:
    * **Not mapped**. When added, the card will be enabled. When updating the card, this value will remain unchanged.
    * **Fixed value**. Select either "Card Enabled" or "Card Disabled".
    * **Source data field**. Select a source field to retrieve the enabled or disabled value from. Boolean characters will be used to determine if the card is enabled or disabled.

      Refer to [Mapping Boolean values](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/mapping-boolean-values.md).
11. To set the card issue level, select either:
    * **Not mapped**. When added, the issue level will be set to the card type default. When updating the card, this value will remain unchanged.
    * **Fixed value**. Enter an issue level for the card (0-15).
    * **Source data field**. Select the source field to retrieve the issue level value from.
    * If the source field contains a non issue level value, the cardholder record will fail to import.
12. To set the card type, select a card type from the drop-down list.

    **Notes:**

    * The "Edit Enterprise Data Interfaces" operator privilege enables an operator to view all card types in the drop-down list.
    * Only card types with the same Region Code and Facility Code can be changed.
    * The card transformation has to match one card on the cardholder. If a cardholder has multiple cards of one type, then the record will fail.
    * A card type cannot be added and changed using a single transformation.
13. Click the **OK** button. Your transformation is added to the Transformations grid.
14. Repeat as necessary, to add additional transformations.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-073aa022ea02eb3512c282f24625f1db0ffd41bc%2Ftransformationcardexamples.png?alt=media)

    **Note:**

    * If the source value doesn't match a transformation, refer to [Mapping a value that doesn't match a transformation](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/mapping-a-value-that-doesnt-match-a-transformation.md).
    * When mapping from a database, if the source field is a related data field containing multiple values, then each value will be processed in turn.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-transformation-mapping/card-transformation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
