Terminology
These terms are useful for understanding the Configuration Management
functionality:
| Term | Description |
|---|---|
| Dependency | Certain resources require other resources to be selected during package creation. These other resources are known as dependencies. |
| Global Package | A global package is comprised of a collection of resources from one or more applications. Global packages are created by Infor or designated Partners. These packages are then entitled to other companies, which can then deploy the global package. |
| Local Package | A local package is comprised of a collection of resources from one or more applications of a tenant. A local package can be created by a company and then deployed to that same company's tenants. |
| Organization | When you create or deploy a package, the top level of data is referred to as an organization. The purpose of an Organization may be different for each application. Refer to each application's Configuration Management Reference Guide for details. |
| Resource | A resource refers to configurations, content, security authorization data and extensions within an application that can be exported via a package. |
| Source tenant | The source tenant is the tenant where the package is created (exported). |
| Target tenant | The target tenant is the tenant into which the package is deployed. |
| Tenant | A tenant is a set of environments of the same type, such as your company's production (PRD) environments. |