Code list extensions

For a code list, extensions are used to add name-value pairs.

Users can create and store code list in PEM Partner Repository and provision them to any external system such as Sterling File Gateway.

For more information about adding extensions to a code list, see Creating a code list.

Extensions are used to map the Sterling File Gateway Code List version number with PEM Partner Repository Code List version. Therefore, when a Code List is provisioned, PEM Partner Provisioner creates an extension with the extension name VersionInSFG and value SFG.

CAUTION:

Do not to delete or modify the VersionInSFG extension. Also, use this extension only if you have implemented Code List integration with Sterling File Gateway.

When provisioning code lists, users can modify the details of code lists that are in In-Progress status by adding extensions in the following format:
VersionIn<ApplicationName>

Example: If Sterling File Gateway wants to store a version of the code list in PEM Partner Repository that is in In-Progress status, the code list extension name must be VersionInSFG with the respective extension value, which is version number of the code list in Sterling File Gateway.

Note: When extensions with VersionIn<ApplicationName> format are added to code lists, on creating a new version of such code lists, the extension details are not copied to the new code list version.