Hi, We are about to start work on $subject. We have identified 4 locations where we can integrate with workflows. Those are,
1. Self Sign-Up on the API Store. 2. Application Creation 3. Subscribing Applications to APIs 4. Adding Comments. Whenever a user attempts to perform one of the actions above, there will be an extension point from the API Manager which will be invoked. This would be a service endpoint (REST?) where users can have their own implementation. Whenever this service endpoint is invoked, the intended action will not be performed completely. Rather it will end up in an intermediary state. Ex: If a workflow is executed on creating a subscription, the database entry will be created with its state as Inactive. Upon completion of the workflow, there will be an endpoint exposed on the API Manager which clients need to invoke so that the subscription will now move into Active state. The same model described above will be used for all usecases given above. For this to be possible, the following columns need to be added to the relevant tables. i) Status - Active/Inactive ii) Workflow ID - This is for having a reference id between the executed workflow and the relevant database entry. iii) Workflow Status Message - This if for storing a message which can be useful meta information. Ex: If a subscription approval was rejected, why? Appreciate your thoughts and suggestions on this. Thanks, NuwanD. -- Nuwan Dias Senior Software Engineer - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
