The Import of the Sender-defined Keywords

The Sender-defined Keywords (SDKs) are imported according to specific rules.

The SDKs are defined at the application level and are referenced from the assemblies that belong to that application.

While copying an assembly folder elements that reference the SDK of an application, there is a mechanism responsible for adding the required SDKs to the target application and assigning them to the imported folder instance. Examples of possible scenarios are provided in the table below.

When importing from sequence assembly or submitted view to initial or working assemblies, the SDK is copied to an application and assigned to the imported folders. See the details in the table below.

If the folders are imported to the assembly template, the SDKs are not copied.

The Sender-defined Keywords of the imported folder is not changed after updating the Display Name of the Sender-defined Keywords in a source application.

Note: Changing of CV Profiles in Publishing Settings may lead to unexpected behavior affecting the Context of Use selections, additional and regional attributes.


Action	Result
Importing of folders from the source Assembly1 to the target Assembly2, where the existing SDK has the same Code and Display Name as an SDK referenced in the imported assembly.	After the import, the SDK is not copied from the source Application1 to the target Application2. Additional Information for the imported folder contains the SDK from the Application2.
Importing of folders from the source Assembly1 to the target Assembly2, where the existing SDK has Code and Display Name different from Display Name and Code of an SDK referenced in the imported assembly.	After the import, the SDK is copied from the source Application1 to the target Application2. Additional Information for the imported folder contains the copied SDK.
Importing of folders from the Assembly1 to the target Assembly2, where the existing SDK has the same Display Name as an SDK referenced in the imported assembly, but different Code.	After the import, the SDK is not copied from the source Application1 to the target Application2. Additional Information for the imported folder contains the SDK from the Application2.
Importing of folders from the source Assembly1 to the target Assembly2, where the existing SDK has the same Code as an SDK referenced in the imported assembly, but different Display Name.	After the import, the SDK is copied from the source Application1 to the target Application2. The Code of the copied SDK is generated in the following way: — If the Code value ends with a number, then the number is increased by 1. Example: SDK-001 --> SDK-002. — If the Code value ends with a letter/symbol, then '1' should be added to the end of the value. Example: 001-SDK ---> 001-SDK1. Additional Information for the imported folder contains the copied SDK.