03-10-2013 04:57 AM
03-11-2013 06:50 AM
03-11-2013 11:16 AM
Of course 3 would be the 'cleanest' solution, but also the most complex one. Also technical, as you'd need two-phase transactions and all that if you want to do it cleanly…Hi,
But I'm wondering, what exactly is being stored in the other processes? Why can't you just store the userId in Activiti, and store the other details somewhere else. Whenever you need them, just do a call to that external system for the details?
03-12-2013 04:30 AM
03-16-2013 05:18 AM
I guess all those requirements (when you choose sync) can be fixed if your user-management allows plugging in code when these events occur, so you can call the Activiti API to perform the required actions.Thanks for this idea, but we have a old legacy application, that API not allows plugging in code ops:
03-18-2013 11:50 AM
03-20-2013 08:49 AM
Damn those legacy systems! 😉we have anlegacy application, but not a legacy dbms;-)
Is it a regular old db? Shouldn't be an issue then?
03-21-2013 07:18 AM
03-22-2013 09:31 AM
Poor you .. but still, Access has a jdbc driver (or is it OCDB?) right?
Dang, when I was a student I had to fetch stuff from access using jdbc…. brings back memories.
03-25-2013 08:43 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.