> 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/competency-transformation.md).

# Adding a Competency transformation

### Introduction

When a source value is transformed, it can be used to add, update or remove a competency from a cardholder.

### Procedure

1. Create a transformation mapping to the Gallagher Command Centre Competencies 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-91c93c768d5ae6e77acce66b55c7c78feed31fe6%2Ftransformationcompetencies.png?alt=media)
3. In the upper field, enter the source value you wish to transform.

   **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. Select the competency you want to assign to cardholders, from the drop down list.
5. To enable or disable the competency, select either:
   * **Not mapped**. When added, the competency will be enabled. When updated, this value will remain unchanged.
   * **Fixed value**. Select either Disabled or Enabled. Disabled will disable the competency until the specified Re-enablement Date. Enabled will activate the competency until the specified Expiry Date.
   * **Source data field**. Select a source field to retrieve the enabled or disabled value from. Boolean characters will be used to determine if the competency is enabled or disabled. A positive value will disable the competency. 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).
6. To set an expiry date and time for the competency, select either:
   * **Not mapped**. When added, the competency default expiry date and time will be used. When updated, this value will remain unchanged.
   * **Fixed value**. Enter a date and time.
   * **Source data field**. Select a source field to retrieve the date and time from.

     If you wish to specify a fixed expiry 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 competency will expire at a time of 0:00 hours on the defined 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 source field contains a blank value, a transformation mapping will clear the competency's expiry date and time. Note that this is the opposite behaviour from a direct mapping.
7. To re-enable the competency at a specified date and time, select either:
   * **Not mapped**. When added, the competency will remain disabled. When updated, this value will remain unchanged.
   * **Fixed value**. Enter a date and time.
   * **Source data field**. Select a source field to retrieve the date and time from.

     If you wish to specify a fixed re-enablement 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 competency will re-enable at a time of 0:00 hours on the defined 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 source field contains a blank value, the re-enablement date and time will not be set.
8. To add a comment to the competency, select either:
   * **Not mapped**. When added, a comment will not be added. When updated, the comment will remain unchanged.
   * **Fixed value**. Enter your free-form text comment (limited to 1500 characters).
   * **Source data field**. Select a source field to retrieve the comment from.
   * If the source field contains a blank value, the comment field will be set to blank.
9. To replace the existing comment, select **Replace** from the drop down list.
10. To append the comment, select **Append** from the drop down list.

    If the new text when added, exceeds the maximum size for the comment field, text will be removed from the beginning.
11. Click the **OK** button. Your transformation is added to the Transformations grid.
12. 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-361224c28b56f3c8117494c2f70ae87174f75e55%2Ftransformationcompetencyexamples.png?alt=media)

    **Notes:**

    * 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).
    * If you have mapped more than one source field to a competency (not recommended), then the last mapping listed in the Edit Mappings window will be used to add/update the competency for the cardholder.
    * 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/competency-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.
