Hi all,
Matrix in [1] shows how userStore operation we are currently considering
with workflows affects to each other and how we are planning to handle them.
Please add you suggestions on if there is anything to be changed or added.
Thanks.
1.
Thanks, Chamila :-)
And you get the list of people easily from the database table...
Best regards,
Frank
2015-07-22 14:31 GMT+02:00 Chamila Wijayarathna cham...@wso2.com:
Hi Frank,
yes, one of the main requirements I am trying to address is handling
adding duplicate users. Also as I
Yes, the list of people who are not in the userstore since they are in a
workflow.
On Thu, Jul 23, 2015 at 4:12 PM, Frank Leymann fr...@wso2.com wrote:
Thanks, Chamila :-)
And you get the list of people easily from the database table...
Best regards,
Frank
2015-07-22 14:31 GMT+02:00
Dear Chamila,
in summary, you are implementing a pessimistic offline lock, right?
http://martinfowler.com/eaaCatalog/pessimisticOfflineLock.html
Best regards,
Frank
2015-07-22 7:23 GMT+02:00 Chamila Wijayarathna cham...@wso2.com:
Hi all,
Currently we are in the process of implementing
Hi Frank,
yes, one of the main requirements I am trying to address is handling adding
duplicate users. Also as I mentioned in my previous mail, we need a way so
that an admin user can see list of people with those who are still in
workflows and not accepted.
Thanks
On Wed, Jul 22, 2015 at 5:37
Hi all,
Currently we are in the process of implementing Workflow support for user
operations in IS 5.1.0. Recently we have identified following issue in the
implementation. For the sake of the conversation let’s focus only on
workflow support for 'addUser' operation.
Usually when a user is added