Deployment

You must prepare the application before deploying the local package.

Prepare the target tenant before you deploy a Infor GenAI local package. Use Infor CloudSuite Self-Service Portal to complete the export, import, and validation steps. The export, import, and validation procedures apply to all products. For those procedures, see the Infor CloudSuite Self-Service Portal Configuration Management Administration Guide.

What do I need before deploying?

  • Enable the Infor GenAI application on the target tenant.
  • Enable the required Infor GenAI feature flags on the target tenant. Required feature flags include the feature and resource-specific features, such as conversation starter editing.
Note: If the target tenant does not have the GenAI application enabled, or does not have the required GenAI feature flags,a warning message is displayed. You can then continue the deployment.

How are dependencies handled?

When you add an agent to a package, it does not automatically add its tools and skills. You must include them manually. Otherwise, the agent will not work in the target tenant because its required dependencies are missing.

  1. You select an agent and add it to a package.
  2. The agent may show that it uses certain tools and skills.
  3. You must manually add those tools and skills to the package as well.
  4. If you do not include them, they will not exist in the target tenant after deployment.
  5. As a result, the agent may fail or not work correctly because the required tools and skills are missing.
Component Dependency
Agent
  • Assigned tools
  • Skills
  • Custom security roles
  • MCP tool references
Skill
  • Assigned tools
  • Custom security roles
Focus mode
  • Referenced agents
  • Tools
Extension
  • Targeted agents
  • Skills
Guardrail
  • Assigned custom security roles
Note: Conversation starters and prompts do not include dependencies.

Custom API suites, with or without MCP Server enablement, that tools invoke are included in the package under the IONAPI product scope.

How does the compare report work?

Before deployment, the compare report validates the package content against the target tenant data. The compare report identifies:

  • Name conflicts: Resources with the same name already exist in the target tenant.
  • Dependency issues: Required API suites or MCP servers are not available in the target tenant.

Review the compare report before deployment. Resolve all reported errors before you deploy the package.