The Status Mapping section is where parent-level mapping takes place to better associate journey stages and statuses across an account to a normalized value. All existing standard journey statuses (i..e like Scheduling, Offer, etc.) will be mapped to their corresponding Core Stage under the Paradox Default mapping.

Paradox Default System Mapping

The Paradox Default is the default mapping that is the normalized, standardized, and short-list mapping of all journey statuses in an account. This serves as a baseline for scheduling and analytics for the candidate lifecycle within an account for our internal teams.

The Core Stages serve as the basis for system mapping. All standard journey statuses will be mapped for clients by default.

• Note: While some statuses are automatically mapped, we cannot assume every mapping in the CEM, and thus, additional customization must be done at the account level for each client.
  • For Example: One client’s Onboarding Core Stage might be comprised of a combination of Form and custom statuses, whereas another’s might be Forms and Offers statuses. This is the level of additional mapping that would be required account-to-account.

New System Mapping

New System Mapping can be added depending on the use case and which requires a System Journey’s statuses to map a standard mapping status. These should specifically only occur when your client uses multiple sources that utilize status movements.

To add a new system mapping, complete the steps below.

1. Click the Paradox Default System Mapping and then + Add System from the open drop-down menu.
2. A modal will open where you will enter the new system name and then click Create.
   • Note: System names must be unique.
3. A new and blank system mapping will open. Enter the source’s status in the Core Stage field. This status should be the external status that you want to be tied to a Candidate Journey status.
4. If the client has an external ID tied to the journey status, enter that in the External ID field.
5. Select at least one journey status from the Candidate Journey Status Match selector that should be mapped to the Core Stage entered.
6. If more than one external status needs to be mapped, click the + Add New Core Stage button underneath the mapped fields.
7. Repeat steps #3-5.
8. When all Core Stages and their associated statuses are added, click the Save button in the top right corner of the new mapping section.

Calling System Mapping in Integration Center

For configurations where a System Mapping serves as the mapping table for an integration, such as the use case highlighted above in yellow, mapped statuses may need to be called in Integration Center to receive the candidate’s external system mapping.

There are two ways to call the status from the Payload Library:

• Call Paradox Default: {{ __long_id | get_journey_candidate_status_exid}}
• Call Custom System Mapping: {{__long_id | get_journey_candidate_status_exid('system_mapping_name')}}
  • Example: {__long_id | get_journey_candidate_status_exid('SuccessFactors')}}

Reorder standard statuses in a custom mapping

If you want to rearrange the order of standard statuses, follow the steps below.

1. Click the settings icon next to the Save button.
2. Select Reorder Mapping from its drop-down menu.
3. From the modal that opens, click the preferred stage’s rearrange icon (multi-dot icon), and then drag and drop the stage in the preferred order.
4. Click Apply.

Delete statuses in Custom stages

You can delete any added statuses by selecting them in the list and then clicking the Delete button that appears in the top right corner of the custom mapping section. A modal will then open, which, when confirmed, will remove the selected statuses from the mapping.

Rename, duplicate, or delete custom mapping

If you want to rename, duplicate, or delete custom mapping, simply click the settings icon in the top right corner of the selected custom mapping section and select the desired action from its drop-down menu. From here, complete the necessary actions.