Application Details

This is the first page of Application Onboarding Wizard. The images looks like below:

Step 1: Enter the Application Details

Basic Details

1. Upload Application Logo:  Maximum file size is 2MB in PNG or JEPG format
2. Application Name: Enter name of your application here. Currently special characters are not allowed in Application Name
3. Search Keywords: You can enter keywords to tag your application for filters. Multiple values can be entered here
4. Description: Provide a brief description of  the application.
5. Add to Role: Add this Application to a preexisting Role (if any)
6. Add to Collection: Add this Application to a preexisting Collection (if any)

Provide Application Owner details-

1. Business Owner: Enter name of the individual who owns the business associated with this application. This is a required field. Enter your name if not sure.
2. IT Owner: Enter name of the individual who owns technology related decisions associated with this application. This is a required and important field. Enter your name if not sure.
3. Application Details#IDM: Enter Identity Management system and version your Enterprise will use. To use IDHub engine use IDE Shim by default. Other IDM options are only presented if IDHub is integrated with other IDM systems.

Provide details on how this application integrates with IDHub-

1. Integration Level: Is the application connected or disconnected to IDHub. 
   1. For Connected Application you would need to fill the following details:
      1. Authentication type
      2. Connection Credentials (Username and Password)
      3. Scheduler details (Time, date and frequency)
   2. For Disconnected Application, you need not add anything else
2. Trusted Reconciliation: Is this application a trusted source (source of truth) of information for IDHub. If yes, it means the user identity data in the application is the source of user identity information in IDHub

Provide Approval Workflow details-

1. Approval Workflow: Select the approval workflow for the application once requested b the user. Currently, IDHub provides 5 levels of approval workflow namely
   1. Auto approver (Auto approved + Fulfiller group for disconnected applications)
   2. Manager Approver ( Beneficiary Manager Approval + Fulfiller group for disconnected applications)
   3. Level1 Approver ( Beneficiary Manager Approval + 1 additional approver + Fulfiller group for disconnected applications)
   4. Level 2 Approver ( Beneficiary Manager Approval + 2 additional approver + Fulfiller group for disconnected applications)
   5. Level 3 Approver  (Beneficiary Manager Approval + 3 additional approver + Fulfiller group for disconnected applications)
2. Fulfiller: All disconnected applications need a fulfiller group to manually provision and de-provision access to users.
3. Attach a Request Form (New Feature) : This helps in attaching a form what is made in 'Custom Forms' section.
   Select if any preexisting form is there which needs to be used for fetching user information while requesting for the application.
4. Certifiable:  You can enter tags that denote the industry or regulatory standards this application has to show compliance and adhere to.
5. Risk Level: Business owners use an internal enterprise defined criteria to classify the Risk Level of their application.
   Typically in the industry the following are the 3 Risk Level classifications-
   1. Low Risk
      1. Application processes, stores data available for public consumption
      2. Application can be easily restored and data can be easily reproduced
      3. Application  is not-critical enterprise function and is mostly informational.
   2. Moderate Risk
      1. Application processes, stores data not for public consumption and is limited to internal use only
      2. Application is integrated to other systems in the network and is trusted and important for other system function.
      3. Application is important for enterprise function.
   3. High Risk
      1. Application processes, stores data that are highly confidential , restricted and/ or are protected by regulatory standards.
      2. Application is integrated to other systems in the network and is highly trusted and critical for other system function.
      3. Application is critical for enterprise function.
6. Requestable: Switch this toggle button to on for it to be available for request in your end user catalog.

Footer:

1. Next: Navigate to next page in the wizard.