Topbraid EDG update ontology workflow copies

36 views
Skip to first unread message

Stefan Verweij

unread,
Mar 5, 2020, 3:23:33 AM3/5/20
to TopBraid Suite Users
Hi TopBraid crew,

Using Topbraid EDG version 6.2, I am just starting to use workflows to keep track of changes made by me or others. In my ontology every usergroup has his own workflow. Now when one of the workflow copies is merged with the production copy or the production copy is changed in general, the other workflow copies will become outdated. Is there a way to update the remaining workflow copies (similar to how you can merge/rebase branches in git)? Hope you can help me out.

Kind regards,
Stefan

Holger Knublauch

unread,
Mar 5, 2020, 3:47:06 AM3/5/20
to topbrai...@googlegroups.com

Hi Stefan,

workflows are designed so that changes made to master will automatically apply to working copies too. A working copy is simply master plus the delta from the local changes. Do you have changes to master that you cannot see in a workflow?

Holger

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/00e637bd-c486-48a7-b32a-43c8229b88bf%40googlegroups.com.

Stefan Verweij

unread,
Mar 5, 2020, 4:01:50 AM3/5/20
to TopBraid Suite Users
I believe the workflow copies didn't update automatically this morning, but now they seem to do so indeed. Maybe I should have taken my coffee earlier.. :p
Thanks for the fast response and also for this great implementation!

Stefan

Op donderdag 5 maart 2020 09:47:06 UTC+1 schreef Holger Knublauch:

Stefan Verweij

unread,
Mar 25, 2020, 4:21:21 AM3/25/20
to TopBraid Suite Users
Hi Holger,

It's been a while, but I discovered a workflow that does not contain the same properties as the production copy. I checked the differences between the two in the comparison report and checked the change history, but I couldn't find any changes (deletions) made to those properties in the workflow. How can I solve this e.g. can I somehow manually 'pull' the missing properties from the production copy similar to how git works? I'm using TopBraid EDG 6.2.

Stefan

Op donderdag 5 maart 2020 09:47:06 UTC+1 schreef Holger Knublauch:

Hi Stefan,

workflows are designed so that changes made to master will automatically apply to working copies too. A working copy is simply master plus the delta from the local changes. Do you have changes to master that you cannot see in a workflow?

Holger


On 5/03/2020 6:23 pm, Stefan Verweij wrote:
Hi TopBraid crew,

Using Topbraid EDG version 6.2, I am just starting to use workflows to keep track of changes made by me or others. In my ontology every usergroup has his own workflow. Now when one of the workflow copies is merged with the production copy or the production copy is changed in general, the other workflow copies will become outdated. Is there a way to update the remaining workflow copies (similar to how you can merge/rebase branches in git)? Hope you can help me out.

Kind regards,
Stefan

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbrai...@googlegroups.com.

Stefan Verweij

unread,
Mar 25, 2020, 6:26:18 AM3/25/20
to TopBraid Suite Users
Fixed the issue, since it was only one working copy (the others were not affected with this issue), I started looking in the Turtle code. Somehow the NodeShape of the class with the missing properties was missing (probably got deleted by one of the editors in the workflow). Never mind my question, everything works as it should be again.

Stefan

Op woensdag 25 maart 2020 09:21:21 UTC+1 schreef Stefan Verweij:
Reply all
Reply to author
Forward
0 new messages