welcome back from the holidays those that went away.
Im still having problems with shared objects whereby ive made my BO shared but the problem comes in when i change data in 1 process... i would like it to change on the other process as well. But it doesnt seem to be changing it. Not sure if thers more coding that i should do?
Oh heres my scenario. Ive got 2 process apps with a process in each app using one shared business object located in the toolkit. Now i want when i change a value in process app 1 and it should reflect in process app 2 as well. It doesnt seem to be doing this.
Re: Shared Object Problem bpm 82013-01-07T16:13:01ZThis is the accepted answer. This is the accepted answer.This behavior doesn't surprise me. I've never tried it, but it would surprise me if you were allowed to "share" data objects between Process Apps. Sure you can have the same data type in both applications by sharing the same toolkit, but sharing actual instance data between Process Applications would violate the premise that Process Applications are isolated from each other. Plus, if they did share data, it would open up all kinds of very difficult versioning problems. (What happens if a new snapshot of Process App A, with a new version of the toolkit with a new incompatible shared business object, gets deployed?)
Bottom line, I think what you are looking to do would require both processes to be in a single process application. Is there any reason that would be a problem?
jmac_EmeriCon 110000S3HB280 Posts
Re: Shared Object Problem bpm 82013-01-07T16:20:37ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
The way I read the doc this is supposed to work. But I have had issues with this too.
The doc is very thin on Shared Objects, and what little there is, indicates it is possible to do what Cebisa is requesting See here at #6
I currently have a PMR open asking for more information, but I am not very hopeful at the moment.
Re: Shared Object Problem bpm 82013-01-07T21:43:27ZThis is the accepted answer. This is the accepted answer.
- jmac_EmeriCon 110000S3HB
Although I have to wonder what the intended behavior is regarding versioning. And whether the community thinks it would be a best practice; it seems too tightly coupled for separate apps, but I could be persuaded.