Tenanted knowledge documents under tenanted knowledge categories are exported, but when the package is imported, the documents appear under the public knowledge categories. How do I get them imported under the tenanted knowledge categories?

book

Article ID: 50441

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Description:

This article explains why tenanted knowledge categories might get imported as tenanted knowledge articles but under public/un-tenanted knowledge categories, and how to ensure that the knowledge categories maintain their original tenancy when imported.

Solution:

When you create an Export/Import Template for the purpose of exporting a set of knowledge documents in a multi-tenanted Service Desk Manager environment, the Tenant field should be set to the tenant of the documents that are to be exported. You can then select from the categories that exist for that tenant.

When subsequently importing the export package to another system, the tenant needs to be pre-defined to that system.

As well, in order to maintain the tenancy of the knowledge categories, run the import of the export package under a logged-in Administrator contact with a matching tenant.

If you run the import when logged-in as a contact that is un-tenanted (i.e. public), the knowledge categories that are imported will be un-tenanted.

The following screenshots are taken from a r12.5 CA SDM system with multi-tenancy set to ON. In this system, 3 tenants have been created: tenantSP is the service provider, and tenant1 and tenant2 are two non-service-provider tenants.

Figure 1. Export/Import Templates under the Administration tab.

<Please see attached file for image>

Figure 1

Figure 2. A sample Export/Import template for tenant1. Note that the Tenant field specifies tenant1.

<Please see attached file for image>

Figure 2

Figure 3. Editing the template (to add Categories ... click on Category).

<Please see attached file for image>

Figure 3

Figure 4. Only the public categories and the categories for tenant1 can be selected.

<Please see attached file for image>

Figure 4

Figure 5. Here are all of the Knowledge Categories that are defined in the sample system (These are listed under the Knowledge Categories subfolder of the Knowledge folder under the Administration tab.)

<Please see attached file for image>

Figure 5

Figure 6. Click Export in the Export/Import Template Detail form.

<Please see attached file for image>

Figure 6

Figure 7. The Knowledge Export Transactions List contains a new entry for the completion of the export. The file for the package exists in the $NXROOT\site\keit\export directory.

<Please see attached file for image>

Figure 7

Environment

Release:
Component: ARGIS

Attachments

1558698593685000050441_sktwi1f5rjvs16ocl.gif get_app
1558698591681000050441_sktwi1f5rjvs16ock.gif get_app
1558698589850000050441_sktwi1f5rjvs16ocj.gif get_app
1558698588215000050441_sktwi1f5rjvs16oci.gif get_app
1558698586228000050441_sktwi1f5rjvs16och.gif get_app
1558698584368000050441_sktwi1f5rjvs16ocg.gif get_app
1558698582374000050441_sktwi1f5rjvs16ocf.gif get_app