Skip to main content
Version: On prem: 14.0.16

Application onboarding

The Application onboarding process entails a collaboration between the Business and IT. Not all resources will require applications, and the scope of application onboarding can vary from business to business. However, there are some general guidelines on how to approach this process.

A good starting point is to create a breakdown of applications to be onboarded that includes information on which applications are AD-controlled, need system integration, or need an API, for example:

Application NameAD-Controlled?Comments
Report on Financial PostingsYes
OmicronNoNeeds API / integration path
ZetaNoOracle-based – System Onboarding for Oracle Needed
tip

Active Directory is usually one of the first systems to be onboarded. It provides a good starting point for evaluating the amount of collaborative effort that will be needed during the application onboarding process.

Follow these steps to prepare for onboarding:

  • Prioritize resources according to business criticality, try to answer the following questions:

    • Which resources contain business-critical access rights?
    • Which resources contain highly sensitive information?
    • Which resources does the business need to control for auditing and compliance purposes?

  • Select applications to run test onboarding

    • Choose a few business-critical applications and follow the instructions available in the [] section.

The onboarding of Application roles comprise different elements, some which you only need to create once initially, some that you need to create once for each application, and others that you need to create multiple times.

Below you will find a detailed overview of these elements, how they are created and used.

Initial elements created once for the whole solution:

  • Resource folders are created once based on the desired levels of approval, for example:

    • Manager and owner approval
    • No approval
    info

    To create new Resource folders, go to Setup > Master data > Resources > Resource folders and create one folder per approval level.

  • Resource types are created once for use for application accounts and roles.

    • Application account
    • Application role (available in product)
    note

    You also need a resource type for Application Role which is available as part of the standard application. You can also choose to create your own the Resource type(s).

    In most cases, you only need to create one Resource type. Reasons to create multiple types include Post-validity, Attributes for example for data separation, Exclusively managed resources.

Elements created once for each application:

  • Application

    • Application (system object marked as "Logical system")

  • Application resources

    • Application account resource (one per relevant account type)

Elements created multiple times:

  • Application resources
    • Application roles (multiple per application)
info

Next, follow the steps described in the following sections to successfully onboard an application: