Activate Application
- You will need elevated permissions to perform most of these actions.
- Check out Authorization & roles for more info.
Application activation is necessary because we provide additional metadata, like context type support, to distinguish whether the application is supported by the selected context type or universally across all context types.
- Have the application key ready
appKey
. This can be found in Fusion when navigation to an application. path will the be:
fusion.equinor.com/apps/{appKey}
or Find the app-key for the app you want to onboard in the Portal API URL
GET: /api/portal/fusion/apps
- If not already there Go to the
Portal API URL
swagger page og the environment you want, se env table below. - **Find the app-group ID you want to onboard the app to (eg CC's ID).
GET: /api/app-groups
Starting from v3.0.0 the appCategory / appGroup is part of the application manifest. This means that the appCategory defined in the application manifest is the one used in the portal. This reduces manual work since the category only needs to be defined once, but is sadly required to onboard a application.
- Find out what contextsTypes teh application is supporting?
If no context type is specified during the application onboarding process, the app will be accessible for any selected context. In this scenario, the application is regarded as global. Conversely, when context types are provided, the application becomes available only when a context of the corresponding type is selected.
{
"appKey": "some-application-key",
"isLegacy": false, // is needed but does not have any effect.
"appGroupId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"contextTypes": [
"ProjectMaster", "Facility"
]
}
- Fill in all fields in
POST: /api/onboarded-apps
- Your app is now onboarded, but will not be available yet in any portal.
- Proceed with onboarding the application to the portal: Onboarding Global Application or Onboarding Context Application