Hi community,
I'm currently evaluating Oracle version management (OWM) using Bentley Map. Creating, switching and merging workspaces (or versions) work fairly good from Bentley Map, I can't manage to do a "DBMS_WM.RefreshWorkspace". Allthough there is a "Resfresh" and "Resfesh all" menu item, it doesn't seem to provide the functionaliyty I'm looking for.
Anyone having experience with this ?
TIA
Holger
So I take it you have someone who has created a child version, and made some edits to it, and someone else has made changes to the parent version, in the mean time, and you want to 'update' the child with the changes from the parent ?
Holger,
At this time the ability to perform a DBMS_WM.RefreshWorkspace call from the Bentley Map Interoperability user interface is not supported, but is being considered for inclusion in a future release based upon overall customer demand. Could you please describe your organizational workflows that require this capability? Would you expect the refresh operation to support a similar conflict resolution user interface and process similar to the existing "Merge to Parent" capabilities?
Regards,
Jeff Bielefeld [Bentley]
Jerry, Jeff,
I was out of office the last two weeks, so I'm try to describe the situation now.
User A creates Version A of LIVE workspace with pessimistic locking and start to create new features and change existing ones.
User B create Version B of LIVE workspace with pessimistic locking and start to create new features and change existing ones.
When User B tries to change a feature User A has already modified, his lock attempt fails due to pessimistic locking mode.
Ok, this is the expected behaviour.
User A merges his changes to parent (LIVE) workspace and User B would like to update his workspace with the changes User A did. This is the moment when DBMS_WM.RefreshWorkspace enters the game. User B can't refresh his workspace through the dialog, only by applying DBMS_WM.xxx in a database session.
Our current workflow wouldn't expect conflict management in this case since we're using pessimistic locking.
Best regards,
First of all thank you for your valuable feedback, much appreciated. Next, as previously mentioned, at this time unfortunately the ability to perform a DBMS_WM.RefreshWorkspace call from the Bentley Map Interoperability user interface is not supported, but is being considered for inclusion in a future release.
Please feel free to contact me directly to discuss potential solutions for your current workflow needs.