Hi Shiva, As discussed, let's move all Process Store functions to the publisher. Then we can keep the store side as it is for now.
Regards, Chathura On Thu, Sep 4, 2014 at 2:03 PM, Shiva Balachandran <[email protected]> wrote: > +1. Moving the publisher functionality to the store will increase the > usability of the product. The no. of steps to perform the functionality > will be minimum, especially now the user has to log in twice, once in the > store and secondly in the publisher, when swapping between the UI. > > > On Thu, Sep 4, 2014 at 12:52 PM, Chathura Ekanayake <[email protected]> > wrote: > >> Hi Ruchira/all, >> >> If we separate the publishing and store parts that way, a user (e.g. >> business analyst) who is viewing a model has to switch to a separate UI to >> edit it. If you recommend to use the publisher to add/edit models, I think >> more appropriate method would be to implement most of the Process Store >> functionality in by extending the publisher (e.g. add, edit, browse, >> visualize associations, static/runtime analysis). Then the store, which >> will be used only by process clients and participants, has minimum >> functionality to browse/search/view models. In this way, we can do only >> minor (or zero) modifications to the store part and implement all other >> Process Store features in the publisher. >> >> So the implementation will look like: >> >> Publisher (heavily extended by implementing almost all Process Store >> features): >> - Users: process designers, management staff, business analysts >> - Features: >> - Add, edit, delete, browse, search, navigate and view process >> models and related artifacts >> - Design-time analysis of process models >> - Runtime analysis based on execution data >> - Lifecycle management >> - Policy definition and enforcement >> >> Store (minor/zero extensions): >> - Users: >> - process clients (e.g. an employee who wants to purchase a >> computer can find a suitable procurement process and initiate it) >> - process participants (e.g. employees of the loan handling unit >> refer to the loans approval process to determine next steps to be followed) >> - Features: Browse, search, navigate and view process models >> >> WDYT? >> >> Regards, >> Chathura >> >> >> >> >> >> On Thu, Sep 4, 2014 at 12:01 PM, Ruchira Wageesha <[email protected]> >> wrote: >> >>> HI Shiva/Chathura, >>> >>> I would recommend you to keep the adding/editing functionality in the >>> publisher side. Otherwise, you will have to re-implement most of the stuff >>> that we have done in the publisher. >>> >>> You can do SSO between store and publisher. Hence, what you need to do >>> is, just display an edit link in the store. When that edit link is clicked, >>> the user will be redirected to the publisher's edit page of that specific >>> process. Since SSO is enabled, the user will not see much difference. i.e. >>> he will feel that the edit page was there in the store app itself, only >>> difference is, you see a page refresh. >>> >>> Further, if you go with publisher, you have more freedom in the future >>> to improve your add/edit views as publisher UI has designed for that kind >>> of requirements. Otherwise, you will have to introduce your own left menu, >>> search, LC UIs etc. in the store side. >>> >>> /Ruchira >>> >>> >>> On Wed, Sep 3, 2014 at 1:46 PM, Chathura Ekanayake <[email protected]> >>> wrote: >>> >>>> As Shiva has mentioned, we want to do both adding and displaying >>>> process models in the same UI, diverting from the current model of ES to >>>> have a separate publisher and a store. An example requirement would be: a >>>> user browsing a process model may want to add some details to certain >>>> sections of the model, so that he should be able to do it from the same UI. >>>> Similarly, a user may want to add a specialized version of a currently >>>> displaying model. Therefore, I think the adding/editing functionality has >>>> to be provided in the same UI, controlled by user's authorizations. >>>> >>>> Regards, >>>> Chathura >>>> >>>> >>>> On Wed, Sep 3, 2014 at 12:08 PM, Shiva Balachandran <[email protected]> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> The Enterprise Store currently satisfies necessity to host >>>>> applications, gadgets and eBooks. Users are able to add new assets of the >>>>> given type or create their own asset type and work with the store. A >>>>> requirement has arose to develop a Process Store to host processes of all >>>>> types and visualize associations with processes whilst providing other >>>>> utility functions. I am currently working on building a Process Store to >>>>> address the requirement. >>>>> >>>>> After discussion with the stakeholder we have agreed to initially >>>>> build the store as an extension of the enterprise store and move the >>>>> process store out as an product in the future. The extension to be built >>>>> will be for textual based processes and in future will be able to support >>>>> other type of processes too. >>>>> >>>>> The extension to be built will have the following functionality:- >>>>> >>>>> >>>>> - Adding a text based process >>>>> - Editing a text based process >>>>> - View a text based process >>>>> - Search for a text based process >>>>> >>>>> >>>>> - Associate existing text based process to a new variant - The >>>>> user when adding a new process can associate the new process to a >>>>> existing >>>>> one if the new process is a variant or similar to the existing process >>>>> but >>>>> a variant. >>>>> >>>>> >>>>> - Navigating processes through associations - The user can >>>>> navigate through the associations to find similar processes or their >>>>> variants. >>>>> >>>>> >>>>> - Visualizing associations in graph views - The associations >>>>> between the processes will be sketched or depicted. This will be >>>>> developed >>>>> using JSPlumb. >>>>> >>>>> The processes will be built as an asset type of the Enterprise Store >>>>> as discussed and the utility functions of the store such as adding, >>>>> editing, viewing, searching and visualizing will be done in the store >>>>> front >>>>> rather than navigating to the publisher. >>>>> >>>>> Thank you >>>>> >>>>> -- >>>>> Shiva Balachandran >>>>> Software Engineer >>>>> WSO2 Inc. >>>>> >>>>> Mobile - +94 774445788 >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Ruchira Wageesha**Associate Technical Lead* >>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> <http://wso2.com>* >>> >>> *email: [email protected] <[email protected]>, blog: >>> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >>> mobile: +94 77 5493444 <%2B94%2077%205493444>* >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Shiva Balachandran > Software Engineer > WSO2 Inc. > > Mobile - +94 774445788 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
