That sounds great. I will be waiting to hear from him, I'm at gtalk, the jbpm and the
drools IRC channel if he wants to chase me there. Just for you to know there are two
separate concepts, one is the flow chart / business process and the other is each human
interaction. Right now inside jbpm5 the process engine is in charge of executing the flow
charts, which can contain human interactions and the human task component is in charge of
keeping the lifecycle of each one of these interactions, I'm sharing with you these
two concepts because it might be helpful for design decisions :)
Cheers
--
Salaboy@Redhat
Sent with Sparrow (
http://www.sparrowmailapp.com/?sig)
On Tuesday, May 1, 2012 at 2:18 PM, Anil Saldhana wrote:
We are just exploring ways in which a idm usecase is represented as a
collection of BPM tasks. You assemble tasks based on a flow chart. Some of the tasks may
be "login", "get attribute from ldap", "logout",
"process saml" etc.
Still early discussions. Pedro Silva will interface with you soon.
On 05/01/2012 02:55 AM, salaboy wrote:
> Hi, my name is Mauricio Salatino, and I'm working in the jBPM5 Team with the
Human Task module. I saw a post related to Human Tasks and IDM and I want to offer my help
on the BPM side to do a bidirectional integration of both projects. Do you have a place to
describe what are you trying to achieve? I'm not so familiar with IDM but I was
contributing long time ago with jboss-sso so I think that I can catch up quickly.
> Cheers
>
> --
> Salaboy@Redhat
> Sent with Sparrow (
http://www.sparrowmailapp.com/?sig)
>
_______________________________________________
picketlink mailing list
picketlink(a)lists.jboss.org (mailto:picketlink@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/picketlink