Hi,
+1 for develop as separate app and more clean and logical way . But I think
user point of view, its more applicable to view and function with in
publisher. Cant we implement as separate Jaggery app and included to
publisher as a carbon feature. Then this workflow support app is available
as
Hi,
*Overview*
We are currently working on initial design to support workflow extensions
in Enterprise Store as in APIM. Both global workflow extensions (Ex : Self
signup ) and asset level extensions (Ex : Application creation for an API
store ) will be supported.
*Concern*
Once the workflow
There can be workflows for both the Publisher and the Store. Therefore
having a single place to administer both sounds appropriate and easy to
manage.
At least in the context of API Manager, having a page on the Publisher to
administer operations occurring on the Store doesn't seem right.
IMO