This table lists other entities (besides business logic modules, contracts, reports, resources, resource groups) that are supported by the Content Transfer feature. The table also lists what is not transferred with the entity and any related entities.
|
Entity |
What does not Transfer |
Related Entities |
|
|---|---|---|---|
|
Adapter |
|
|
|
|
Alert Devices |
|
|
|
|
Alert Profiles |
|
Event types Resources Alert Recipients |
|
|
Alert Recipients Note: The user is not transferred. The default user name <sadmin> is used. |
Users |
Alert devices |
|
|
Change Set |
|
|
|
|
Contract Non-Versioned Attachments |
|
|
|
|
Contract Non-Versioned Parameters |
|
Document repository |
|
|
Contract Non-Versioned Thresholds |
|
|
|
|
Contract Party |
The contract party is transferred without the relations to user and user groups. However, it does not override existing relations. The association of the contract party with an ACE instance is not transferred. In the local environment, the contract party is associated with the default ACE instance. |
Contract Party Group |
|
|
Contract Party Group |
The contract party group is transferred without the relations to contract parties. User and user groups, however, do not override existing relations. |
|
|
|
Contract Template |
Note a: Site Settings, Advanced, Content Transfer, “Transfer security with Template Library Note b: Site settings, Template Library, Security Mode. |
Non-version entities (non-version parameters, attachments, thresholds, current status, and metric relations) of a template also transfer during a template transfer. If you update a non-version template entity, the template metadata also updates. Transferring a Contract Template also transfers Contract Template Security as a related entity when the "Site Settings" parameter (Note a) is set to “Y” (Default is “N”) and the source and target both use restricted mode (Note b). Current Status transfers together with Contract Template and Service Level Template. |
|
|
Contract Template Security |
|
Contract Template Security comprises several security settings of the Template. (A template can link to many parents; each link can set security.) Contract Template Security brings its root’s Template Library Security, Contract Template, Contract Template’s parents (Template Library or Template Folder) as related entities. Note: There is a limitation in the transfer of Contract Template Security. First, transfer the template folder. Then, in a second transfer operation, transfer the Contract Template Security. |
|
|
Contract Thresholds |
|
|
|
|
Current Status |
|
Current status transfers as a non-version entity. Current status transfers only when contract is committed. |
|
|
Custom Attribute |
The custom attribute order is not transferred. |
Resource type |
|
|
Data Loading Forms |
Do not transfer the User or User Group transfer as a related entity. Handle as for Reports or Alerts. |
|
|
|
Document Repository |
|
|
|
|
Domain Category |
|
Service Domain, Unit |
|
|
Event Type |
The association of the event type with resource types is not transferred. |
|
|
|
Image |
|
|
|
|
Reports |
|
Booklet template transfers with booklet report. |
|
|
Report Folder |
|
Booklet template transfers with booklet report. |
|
|
Resource |
|
|
|
|
Resource Group |
|
|
|
|
Resource Type |
The association of the resource type with event types is not transferred. |
|
|
|
Role Note: When the permissions are not identical the roles are not transferred. Verify that the list of permissions is identical. |
|
|
|
|
Service |
|
|
|
|
Service Domain |
|
|
|
|
Service Group |
The service group is transferred without the relations to services. |
|
|
|
Service Level Template |
Note a: The path is: Site Settings, Advanced, Content Transfer, “Transfer security with Template Library Note b: The path is: Site settings, Template Library, Security Mode. |
Non-version entities (non-version parameters, attachments, thresholds, current status, and metric relations) of a template also transfer during a template transfer. If you update a non-version template entity the template metadata is also updated. Transfer of Service Level Template also transfers Service Level Template Security as a related entity when the "Site Settings" parameter (Note a) is set to “Y” (Default is “N”) and the source and target both use restricted mode (Note b). Current Status transfers together with Contract Template and Service Level Template. |
|
|
Service Level Template Security |
|
Service Level Template Security comprises several security settings of the Template. (Note that a template can link to many parents; each link can set security.) Service Level Template Security brings its root’s Template Library Security, Contract Template, Contract Template’s parents (Template Library or Template Folder) as related entities. Note: There is a limitation in the transfer of Service Level Template Security. First, transfer the template folder. Then, in a second transfer operation, transfer the Service Level Template Security. |
|
|
Template Library |
Note a: Site Settings, Advanced, Content Transfer, “Transfer security with Template Library Note b: Site settings, Template Library, Security Mode. |
Transferring a Template Library also transfers Contract Template Security as a related entity when the "Site Settings" parameter (Note a) is set to “Y” (Default is “N”) and the source and target both use restricted mode (Note b). |
|
|
Template Library Security |
|
Template Library Security is saved using the option “Apply security to included items upon save.” in Content Transfer. So all children’s security will be reset after Template Library Security transfer |
|
|
Time Slot Template |
|
|
|
|
Time Zone |
|
|
|
|
Translation Entries Note: When transferring the translation entries, the entire table is transferred, with the exception of the pending entries. |
|
Translation Table Resource Event Type Service Contract Party Time zone |
|
|
Translation Scripts |
|
Translation Table Time zone |
|
|
Translation Tables |
|
|
|
|
Unit |
|
|
|
|
User Note: Passwords are not transferred from the source to the target. Change the status to active. A prompt then asks for a new password. The default password is “ oblisync”. The organization field must be added to the target manually. Otherwise, the user transfer fails. |
|
User Group Role Time zone Contract Party Contract Party Group |
|
|
User Group
|
|
Role Contract Party Contract Party Group |
|
|
Copyright © 2013 CA.
All rights reserved.
|
|