Overview

This guide describes how Infor GenAI content moves between tenants through local packages and describes the tasks on the target tenant after package deployment.

Use this guide with the Local packages section of the Infor CloudSuite Self-Service Portal Configuration Management Administration Guide. The Local packages section describes the export, import, and validation procedures that apply to all products.

A local package transfers GenAI content from a source tenant to a target tenant through the Configuration Management component in the Infor CloudSuite Self-Service Portal (CSSP).

On the source tenant, an administrator selects GenAI content by using the Manual Selection export option. The package is then deployed to the target tenant.

What is a local package?

A local package is a tenant-level export that contains GenAI content. An administrator can import a local package into another tenant that the same company owns.

After package deployment, administrators can edit all imported content on the target tenant.

Local packages differ from global packages. Global packages deploy Infor-curated content. Global packages can enforce content immutability or require a namespace association.

Key characteristics of local packages

  • All imported content is fully editable after deployment.
  • No namespace association is required.
  • Content that is part of MCC-delivered global packages is excluded from local package creation.
  • Resources retain their enabled or disabled status from the source tenant.
  • The Created By field for all imported resources is set to System on the target tenant.
  • Custom security roles (SRs) and functional security roles (FSRs) referenced by resources are not included in the package. You must manually add the Custom SRs and FSRs to work on the target tenant.
  • MCP Tools referenced by agents or skills are included in the package.
  • Custom API suites referenced by tools are not included in the package. You must manually add custom API suits from IONAPI.

Which GenAI resources can be included in local packages?

A local package can include these GenAI resource types:

Resource type Included in local package
Tools Yes
Agents Yes
Skills Yes
Extensions Yes
Focus Modes Yes
Guardrails Yes
Conversation Starters Yes
Prompts (Prompt Catalog) Yes: includes settings, but not attachments or variables
Note: Prompt Catalog entries are included with their settings, such as the model, temperature, and system prompt. Local packages do not transfer attachments or variables that are configured on prompts. After package deployment, re-create prompt attachments and variables on the target tenant.

What is excluded from local packages?

  • Content delivered through MCC global packages is not available for selection during local package creation.
  • Prompt Catalog attachments and variables.