Hi Vinod, Thanks for the comment, No it's not IS scenario is not suitable rather I looked into current implementations of workflow integration on user signups available in our products and try to get the best out of them.And yes IS do have UI component for Workflow Engagements and Workflow definitions which abstract the underline BPEL definitions from the user.IMO for the ES workflow integration scenario, we can also use those existing UI components rather than reimplementing the logic.
Regards, ~KasunTe On Tue, Jan 26, 2016 at 3:16 PM, Vinod Kavinda <[email protected]> wrote: > Hi Kasun, > AFAIR, in IS they have a generic workflow template (bpel) and they allows > users to modify this via a UI component. With this behavior users don't > have to learn bpel and we have more control over the workflow. > I don't see any point in allowing users to upload workflows. (We can > always use BPS UI if a very rare use case occurred) > Why do you think the IS scenario is not suitable for yours? > > In another note, you can use BPMN also for this. We now prefer using BPMN > over BPEL. > > Regards, > Vinod > > > On Tue, Jan 26, 2016 at 2:50 PM, Kasun Thennakoon <[email protected]> > wrote: > >> I'm currently working on implementing workflow integration with >> Enterprise Store.Problem scenario is when a user signup with the user store >> their registration should be approved by an authorized user in the user >> store before accessing the store.As I did a background study on the problem >> I found that currently similar feature is available with API manager store >> and IS dashboard with different architectures. >> In IS implementation, it provides UI features for adding workflow >> definitions and Workflow Engagements. where a user doesn't need to >> upload human tasks (archived file) and business process (archived files) >> to BPS separately, where those configurations are created in BPS via >> service calls to BPS.And if the workflows are added to trigger on Add user >> operation, when a user create an account in IS dashboard and if there is a >> workflow engagement associate for Add user operation, then the newly >> created user will be queued for approval by an authorized user. >> In API manager user case[2], we have to upload human tasks and business >> process files to BPS and disable the Simple Workflow Executor and enable WS >> Workflow Executor in workflow-extensions.xml.Other than those manual >> configurations it is similar to IS user signup workflow. >> >> IMHO, It would be easy for the user if we provide a UI for deploying >> human task and BPELs by getting required inputs from the user.So we can use >> already existing workflow Integration components from IS for user signup >> approval processes. >> >> any suggestions and recommendations on implementing workflow integration >> would be helpful. >> >> [1]: >> http://wso2.com/library/articles/2015/09/article-wso2-identity-server-5.1.0-workflow-feature-and-use-cases/ >> [2]: https://docs.wso2.com/display/AM1100/Adding+a+User+Signup+Workflow >> >> Thanks >> -- >> *Kasun Thennakoon* >> Software Engineer >> WSO2, Inc. >> Mobile:+94 711661919 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Vinod Kavinda > Software Engineer > *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.* > Mobile : +94 (0) 712 415544 > Blog : http://soatechflicks.blogspot.com/ > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Kasun Thennakoon* Software Engineer WSO2, Inc. Mobile:+94 711661919
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
