---
sourceDocument: Yokohama Account Lifecycle Events
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/acct-lifecycle-events

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Account Lifecycle Events

ft:clusterId :

    - actle

bundleId :

    - actle

workflow :

    - Customer and Industry


---

# Set up the context engine mapper

# Set up the context engine mapper {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
After you have defined the data source, the next step is to specify the record in the context table for which it is applicable.  
1. Login as a user with the `sn_acct_lc.ale_success_agent` role.
2. Navigate to AllData Context EngineContext Engine MappersCreate New.
3. Enter the following details:{#account-lifecycle-define-context-engine-mapper__table_oxx_g3l_ydc__entry__2}

   | Field | Description |
   |-|-|
   | Source table | Select the source table to which the data source is to be mapped. This table is related to the attribute selected in the Breakdown field in the Data Source table. For example, if you selected Account in the Breakdown field, select the Customer Account table here. |
   | Source field | The specific field in the source table that contains the data to be mapped. |
   | Supporting related table | The related table that will be used to connect the source and context tables. |
   | Query field | Select the field that is used to query or dot walk the Supporting related table to map data from the Source table to the Context table. |
   | Resolving context table | The target table for mapping the data source. |
   | Resolving context field | The target field where the mapped data will be stored. |
   | Script | If you cannot query the context table through dot walking, you can define a script that uses the Source field and returns an array of possible context fields. |
   [ ]

   {#account-lifecycle-define-context-engine-mapper__table_oxx_g3l_ydc}  
   Note:  
   You can set up the context engine to map the source and target tables using one of the following methods:
   * Related table: Use the mapping rule `related table[query_field] = source table[source_field]`. In every record in the Source table, the Source field value is matched with the Query field in the Related table.
   * Script: The script checks the Source Field and the ID of the record to determine the appropriate context based on the resolving context table.
   {#account-lifecycle-define-context-engine-mapper__ul_fzb_h2b_b2c}

   The following examples show how you can set up the mapping.

   Example with Related table
   :     

   Example with script
   :     

4. Click Submit to save the context mapping.
5. Navigate to AllData Context EngineData Sources.  

   <br />

6. Open the data source you had created earlier and click Publish.

   Data will now be collected as per the defined schedule and the context engine data record is created and stored in the Context Engine Data table.
{#account-lifecycle-define-context-engine-mapper__ol_ehj_3gl_ydc}

*[\>]: and then