Currently the API manager supports business process work flow execution only for below operations.
1. User creation process. 2. Application creation process. 3. Subscription process. With this new improvements the focus is to introduce business process work flows for API life cycle stages transitions related operations. In APIs there are five main stages in the life cycle. 1. Created 2. Published 3. Deprecated 4. Retired 5. Blocked. Work flows can be introduced to any transition between two life cycle stages. For example we can introduce a BP work flow for the transition from Stage Created to Published. Currently when we update the API life cycle state to the published via the API manager publisher it will automatically get published to the API gateway allowing the API to be exposed to the consumers. With this approach it will introduce intermediate state ( in review ) between the Created and Published states. When API created and in order to get API published in the gateway( updating the life cycle state of API to published from the API manager publisher ) it will change API state from created to in review state, from there, human task related to approve the work flow changes API state change from in review to published( in gateway). Workflow-admin will provide the necessary interface controls for the approval/reject for API to be published in the gateway. >From implementation point of view it is necessary to add a new column to AM_API_LC_EVENT table ( store the events related to state changes in API life cycle ) indicate whether state transition has completed or not. ( whether it is in the in review state between the previous state and next state in the transition event ) That way It will support many business process work flows for API life cycle stages transitions related operations, not only just support for the current requirement of single BP work flow related to API publishing. Thanks Kevin
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
