Naming convention
During the configuration step in application onboarding, you will have to create several objects. It is best to agree on a stringent naming standard from the beginning, so that it can be used on all the applications consistently.
Here is an example using an AD-based application called Financial Postings:
| Object | Omada Identity ID | Omada Identity Name |
|---|---|---|
| Application | PREFIX_APPNAME LOGICAL_FINANCIALPOSTINGS | App Name Financial Postings The naming convention for the Application should use a prefix as the SYSTEMID must be unique. For example, you can use: LA_APPNAME for “Logical Applications” and PA_APPNAME for “Physical Applications”. |
| Application Account (Admin) | APPNAME.ACCOUNTTYPE FINANCIALPOSTINGS.ADMIN | App Name Account type Account Financial Postings Admin Account |
| Application Account (Personal) | APPNAME.ACCOUNTTYPE FINANCIALPOSTINGS.PERSONAL | App Name Account type Account Financial Postings Personal Account |
| Application Resource ID Prefix | APP_APPNAME_ APP_FINANCIALPOSTINGS_ | N.A. |
| Resource Folder | APPNAME FINANCIALPOSTINGS | App Name Financial Postings |
| Resource Type (Applications) | This does not have an ID, just a name. | Application Resource |
| Resource Type (Account Resources) | This does not have an ID, just a name. | Application Account |
| Resource Category | For the purposes of application onboarding this field will always be filled in as “Role”. | Role |