Security Label Mapping
* 
This tab only appears if you have security labels enabled.
* 
The security label mapping can only be set at the site level. For more information about setting the context level, see Defining Received Delivery Version Mapping.
The Security Labels tab, which is available on the Define Mapping window, allows you to define translations for a set of security labels and values defined on the source system to a set of security labels and values configured on your Windchill system. You can define the security label mapping for each source system with which your Windchill system interacts that also has security labels enabled. For more information, see Best Practices for Using Mapping Definitions.
For mapping the source data to the corresponding target information, follow the procedure mentioned in the Context Mapping topic.
Field
Description
Source Security Labels
Lists the source security label name and value. This name and value pair must match the source system security label exactly and should be listed in the following format: Key=Value separated with a semicolon (;).
* 
You can copy the source security label name and value pair from the Preview Received Delivery Import window.
Mapped Security Labels
Lists the set of security label and security label values that correspond to the set of security label and security label values from the source system.
To set the mapped security label and security label value, click the select security label icon . The Select Security Label window opens, which allows you to select the appropriate security label and value from the Security Labels table. A mapping cannot be established between the source system value and a deleted or disabled value on the current system.
Context
Lists the context in which the values for this row were set.
Locked
Indicates whether the values can be modified in lower contexts. For example, if a row is locked in the site context, it cannot be changed in an organization. The value could be modified at the site context level.
The importing user must also have the appropriate permissions to modify the security label values.
For more information about restricting users who can modify security label values, see Customizing Security Labels.
When security labels are enabled on the source system, but are not enabled on the target system, the import will not apply the security labels and values to the imported objects.
Was this helpful?