On Wed, Oct 15, 2014 at 1:19 PM, Manoj Gunawardena <[email protected]> wrote:
> 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 a feature to distribute with any other app. > > > Thanks > > On Wed, Oct 15, 2014 at 9:47 AM, Nuwan Dias <[email protected]> wrote: > >> 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 having an app for administrative purposes seems logical/clean and >> more secure (you can take it off completely from public facing interfaces >> and deploy internally if required). Even in the case of ES, you can use it >> for workflow administration, theming, doing import/export asset kind of >> stuff, etc. >> >> Thanks, >> NuwanD. >> >> On Wed, Oct 15, 2014 at 9:28 AM, Tanya Madurapperuma <[email protected]> >> wrote: >> >>> 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 support is enabled, there should be a place where >>> different types of tasks will be listed for an admin user approval. In >>> APIM, a seperate admin-dashboard app is used for this >>> purpose.(admin-dashboard app in APIM serves some other tasks such as theme >>> uploading etc as well. ) >>> >>> Does it require to use a seperate app for this in ES as well? Isn't it >>> relevant to add these as pages in ES Publisher with appropriate >>> permissions.Because basically publisher app acts as a store-admin which is >>> used to perform store releated admin tasks such as publishing assets to >>> store, viewing statistics etc. >>> >> Not in all cases can we say the publisher app is admin related. There can be external facing publisher deployments where users will come and publish their artifacts (e.g. external users with publisher role come and publish APIs in API publisher). In that case having workflow integration in publisher app doesn't seem correct. +1 for separate app if you don't have an existing admin related app. > >>> WDYT? >>> >>> Thanks, >>> Tanya >>> -- >>> Tanya Madurapperuma >>> >>> Software Engineer, >>> WSO2 Inc. : wso2.com >>> Mobile : +94718184439 >>> Blog : http://tanyamadurapperuma.blogspot.com >>> >> >> >> >> -- >> Nuwan Dias >> >> Associate Tech Lead - WSO2, Inc. http://wso2.com >> email : [email protected] >> Phone : +94 777 775 729 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Manoj Gunawardena > Tech Lead > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > Mobile : +94 77 2291643 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks & Regards, *Johann Dilantha Nallathamby* Associate Technical Lead & Product Lead of WSO2 Identity Server Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
