Assigning resources to namespaces

Users assigned to the RPA Administrator, IONAPI Administrator, or Infor System Administrator role can use the Configuration Management functionality.

Application-specific configuration, content, extension, and security must be assigned to a namespace. Global package version can then be created from the namespace.

In RPA, a process version is considered as the content or resource. The resources are associated to namespaces in the RPA Studio. RPA Studio is a desktop component of the RPA application.

  1. Log on to the RPA Studio application using your tenant login profile. The tenant must be an editor tenant.
  2. Click New Project. The New Project window is displayed.
  3. Specify the details of the new project that you want to create. RPA flows are created within a project.
  4. Select the global package namespace to which you want to assign the process. The association completes when the process is published.

    Once an RPA process is published with a namespace association:

    • The namespace cannot be changed, and all process versions must belong to the same namespace.
    • Process versions cannot be overwritten.
  5. Review the versioning behavior for subsequent versions published from the editor tenant.

    The major and minor version upgrades are permitted when publishing subsequent versions from the editor tenant, after a process is associated with a namespace. This restriction ensures that the Major.Minor version of the process remains unchanged on the target tenant, regardless of the number of modifications made on the target tenant.

    Note: An RPA Flow is called a Process when published in the RPA Management application. You can also assign namespaces when publishing a process.

    Some RPA flows depend on an Intelligent Document Processing (IDP) Document Processor flow, which is a Configuration Management resource. To establish this dependency, both the RPA process and the IDP Document Processor flow must be registered in Infor Package Repository (IPR).