Application State Transitions in API Developer Portal 5.3.2
Article ID: 433589
Updated On:
Products
Issue/Introduction
We are currently working with API Developer Portal version 5.3.2 and trying to manage application states via the Portal API (PAPI).
Specifically, we have been testing the different possible application states:
ENABLED
DISABLED
APPLICATION_PENDING_APPROVAL
INCOMPLETE
EDIT_APPLICATION_PENDING_APPROVAL
Our findings are the following:
If we create an application with status ENABLED or DISABLED, we are not able to transition it to any other state afterwards.
If we create the application with APPLICATION_PENDING_APPROVAL, the application is actually created in INCOMPLETE status.
Once the application is in INCOMPLETE state, we are unable to transition it to any other state. The only available action seems to be deleting the application.
Resolution
It is not possible to set a application randomly to these states there are rules which define the possible state transitions .
The main states for a application are ENABLED or DISABLED, you can switch the applications between these states .
INCOMPLETE means there is something missing in the application definition like api keys . this state is set by portal when the application is incomplete and can not be changed unless it is resolved .
APPLICATION_PENDING_APPROVAL, means the application creation needs to be approved by a portal admin before it can be set to enabled .
This state can not be changed until approved or denied by a administrator.
Feedback
