Mastering Change Management with Workspaces

Summary

Orbus Software's recent webinar on "Mastering Change Management with Workspaces" provided an in-depth guide on utilizing workspaces to manage organizational changes efficiently. Hosted by Kelly, a senior customer success manager, and Jonathan, a product manager, the session covered tips, best practices, and live demonstrations for navigating change management using the Orbus Infinity platform. Highlights included utilizing workspaces for solution architecture and experimentation without affecting baseline models, an overview of model merge functionalities, and the importance of strategic alignment and stakeholder engagement in successful change management. Attendees also had the opportunity to engage in a Q&A for clarifications and further insights.

Highlights

• Introduction to change management essentials and Orbus's unique approach. 🚀
• Understanding the role of models and workspaces in Orbus Infinity. 📊
• Detailed walkthrough of the workspaces functionality and its applications. 🛠️
• Live demo showcasing workspace creation and how to manage data life cycle. 📽️
• Discussion on permissions and governance within workspaces for data security. 🔐
• Insightful Q&A session addressing user concerns and advanced capabilities. 🤝

Key Takeaways

• Master change management with Orbus Infinity's workspaces for smooth transitions. 🧩
• Strategic alignment and stakeholder engagement are key for successful change. 💡
• Model merge functionalities add flexibility and security in change management. 🔄
• Workspaces offer a safe zone to test changes before applying them. 🛡️
• Upcoming functionalities promise improved audit trails and user experience. 🔜

Overview

The webinar started with Kelly and Jonathan introducing the concept of change management and its critical importance in organizational success. They emphasized the role of leaders as guides in implementing change and ensuring seamless transformation through strategic alignment, risk management, stakeholder engagement, and efficiency improvements.

As the session progressed, Jonathan took attendees through a live demonstration of Orbus Infinity's workspaces. This included creating a workspace, reusing and updating models, and managing data without impacting parent models until changes are approved. This feature is presented as instrumental in facilitating solution architecture and experimentation in a controlled environment.

The interactive segment of the webinar saw an engaging Q&A session where attendees asked about licensing, permissions, and the application of workspaces in real-world scenarios. The hosts teased upcoming features that will further enhance the platform's capabilities, hinting at a bright future for users eager to navigate change efficiently.

Chapters

• 00:30 - 01:30: Introduction and Overview In this introductory chapter, the hosts, Kelly and Jonathan, are introduced. Kelly is a senior customer success manager in North America, while Jonathan is a product manager who has been with the company for nearly two years. Jonathan's work focuses on the repository stream, involving aspects like change management and meta modeling. The session is a webinar on 'Change Management with Workspaces'. This chapter sets the stage for discussions on change management in subsequent chapters.
• 01:30 - 02:30: Importance of Change Management The chapter titled 'Importance of Change Management' starts with a discussion about the agenda, which includes a brief introduction and overview of why change management is essential. It also introduces Oris's approach to change management, specifically focusing on model merge and workspaces. The chapter seems to transition into a demonstration led by a speaker named John.
• 02:30 - 03:30: Orbus Infinity and Change Management The chapter titled 'Orbus Infinity and Change Management' discusses the functionalities of workspaces and provides tips, tricks, and best practices. It emphasizes the importance of change management and highlights the roles architects, VPs, and CIOs play as guides in the transformational process at the enterprise level. The chapter concludes with a Q&A session.
• 03:30 - 04:30: Model Merge Functionality The chapter focuses on Model Merge Functionality and emphasizes navigating through organizational change to ensure success. It highlights strategic alignment as crucial, ensuring planned changes support organizational goals and strategies. The chapter discusses the importance of mapping changes properly and providing adequate support. Additionally, it addresses minimizing risk by identifying potential issues and mitigating them effectively.
• 04:30 - 06:00: Workspaces Approach The chapter 'Workspaces Approach' emphasizes the significance of mapping out change in order to identify potential risks early on. A key point is the importance of stakeholder engagement and the connection between business and IT, which is deemed critical for success. Utilizing models, visualizations, and reports helps ensure that all parties are aligned and working towards the same goals. Additionally, the chapter highlights improving efficiency by effectively using budgets, personnel, and resources.
• 06:00 - 15:00: Demo by Jonathan: Creating a Workspace The chapter titled 'Demo by Jonathan: Creating a Workspace' discusses the challenges of change management, metaphorically comparing it to 'herding cats'. It emphasizes the importance of a deliberate and managed approach to change. The chapter highlights 'Orbus Infinity' as a tool for supporting change management. Orbus Infinity provides 'models', which are discrete spaces within a repository, allowing users to work independently from other models, thus facilitating efficient change management.
• 15:00 - 21:00: Demo: Updating, Adding, and Deleting Data The chapter discusses the varying approaches organizations take in setting up data models based on their specific needs.
• 21:00 - 30:00: Merging Workspaces Back to Baseline The chapter discusses the importance of keeping the 'Baseline' updated in an enterprise environment. It highlights how quickly a current state can become outdated after changes are implemented. Orbus aims to simplify the process of updating the Baseline while ensuring flexibility and maintaining control over the models through review and approval processes.
• 30:00 - 39:00: Further Demonstrations and Q&A The chapter titled 'Further Demonstrations and Q&A' discusses improvements made to Orbit Infinity, focusing on enhancing change management through a new feature called model merge. This feature allows users to compare data between two models, select specific changes, and execute them as needed. The chapter includes a demonstration of this functionality.
• 39:00 - 45:00: Tips and Tricks for Using Workspaces Chapter Title: Tips and Tricks for Using Workspaces The chapter discusses the feature of model merge and the protective measures that can be implemented by limiting merge permissions to specific users or roles. There's positive feedback on the model merge feature, and the team encourages users to share their experiences and thoughts on it. The discussion then transitions into the introduction of the workspaces feature, which is part of phase two of the change management robot initiative.
• 45:00 - 50:00: Closing Remarks and Upcoming Webinars The chapter provides an understanding of how workspaces function as separate and independent entities from the main models in data architectures. Workspaces are described as submodels that allow users to make adjustments and implementations without impacting the main or parent model. They serve multiple purposes, with one of the highlighted uses being solution architecture, particularly useful for proposing changes or target states within a given data structure.

Mastering Change Management with Workspaces Transcription

• 00:00 - 00:30 so hello everybody and welcome to today's webinar change management with workspaces I am Kelly nman I'm a senior customer success manager here in North America and with me today is Jonathan Everet Jonathan Quick intro hi yeah I'm John and I am a product manager and have been with orus for almost two years just shade under two years um and I currently work with a repository stream so that's that's dealing with meta model um things like change management um that views and
• 00:30 - 01:00 visualizations as well so that's my remit great okay thank you Jonathan or John whichever you prefer usually I end up switching back and forth for some reason that's fine that's fine that works all right so today's agenda is pretty straightforward we're going to provide you a quick introduction and overview on why we do change management and oris's approach to it with model merge and workspaces uh then I'll turn it over to John for a short demonstration of the
• 01:00 - 01:30 workspaces functionality and we'll give you a few tips and tricks best practices on that and lastly we will have some time at the end for Q&A all right that being said let's go intro to change management so a little change management 101 why is change management important as an architect as a VP as a CIO um all of you play critical roles when it comes to transformation across your Enterprise but you are the guides you're lighting
• 01:30 - 02:00 the way to navigate your organizations through change and ensure that change is successful so how does the work you do support that there are a few ways that I've got right here for you strategic alignment is a big one making sure that the changes that are being planned support the goals and strategies of the organization do they line up do they map properly are they being adequately supported minimizing risk what potential issues will we see how can we mitigate those risks
• 02:00 - 02:30 mapping out change helps bring those risks to the Forefront arguably the most important one I would say stakeholder engagement uh painting the picture for the business and making sure business and it are connected is critical to success so if you can do that with models visualizations reports you can make sure everybody's on the same page pulling in the same direction and lastly improving efficiency making sure your budget your people all of your resources are being used in the right way so sometimes it
• 02:30 - 03:00 can feel like hurting cats that's why I've got a little picture of cats down here but when you do it right and you're planning and executing your change in a deliberate managed way everybody benefits so that being said how does orbis infinity support your change management efforts most of you should already be familiar with the concept of models in orbus Infinity models are discrete spaces within your repository where you can work independently of whatever's contained in your other mod models so when it comes to how folks use
• 03:00 - 03:30 models it definitely varies based on the organization uh some of our customers go pretty simple one current state one target State one sandbox boom that's all we need some split out into different domains or different lines of business uh they have a model for each one of those some even go a bit more granular than that and set up models for each project they build or each architect they have may have their own model to work in uh just all depends on how you want to use and segregate your data and
• 03:30 - 04:00 what works best for your Enterprise and your team uh and of course as we all know as time passes and changes are made your current state or your Baseline needs to be updated frequently uh it almost gets out of date as soon as you put the changes in so we here at orbus wanted to make this as easy as possible to do while giving users the flexibility they require and at the same time making sure that your models weren't being changed without review and approval so we worked
• 04:00 - 04:30 on bringing some improvements to orbit Infinity across two main phases phase one of improving change management in orbit Infinity model merge was recently rolled out as you may have seen this is a big step forward in how you can manage your data in the repository with the model merge functionality as you'll see in the demo here in a bit you can very easily compare data between two models you can select which changes to apply and then execute those changes when you're ready
• 04:30 - 05:00 you also have a layer of protection here by limiting model merge permissions to only those certain users en roles who need to be able to do that um we've gotten a lot of positive feedback on model merge already which we love to hear so if you've had a chance to play around with it um definitely feel free to share your thoughts we love we love that feedback keep it coming so that's phase one phase two of our change management robot and what we're actually here to show you today is workspaces so as I me mentioned earlier
• 05:00 - 05:30 your models are separate spaces where your data can live independent of all the other models so think of workspaces like little submodels they're containers that Branch off of your parent model where you can do work and make changes without affecting that parent model so there are lots of ways that you can leverage workspaces lots of things you can use them for um first one top of mind would be solution architecture uh if you've got a proposed change a Target state um those are things that you can
• 05:30 - 06:00 pull into a workspace model out and then as the project goes forward you can merge those back into your Baseline when you're ready um also um very easy to use workspaces to create a little scratch Pad so you can experiment and test play around things like that um whatever whatever floats your boat whatever works for you guys uh when you create a workspace you can actually choose which objects and relationships to pull in so you're not having to pull in the entire uh data set from the parent model you can be more
• 06:00 - 06:30 selective so you don't get overwhelmed um and then whatever work you do within that workspace will not impact your parent model at all or other workspaces that you may have branched off from that until you're decide until you're ready to merge that workspace back into your parent model so this functionality is coming very soon and as I said earlier we're really excited to see what our customers can do with it uh but I think that's probably enough from my end uh Jonathan if you're good hand it over to
• 06:30 - 07:00 you so you can take us through how it works yeah of course thank you Kelly I just just see there's a question in the chat asking if this session is being recorded obviously the answer is yes so sh afterwards so yes thank you all right thank you okay uh first thing I do is share my screen and if I've got the right one I a new one screen hang on a second okay okay can everybody see my screen yep I can see it okay super that's
• 07:00 - 07:30 that's a good start okay and again apologies if I talk too quickly um it's it's been known so please feel free to stick a question and saying John please slow down okay so what what I plan to show you today is a very quick demo of going going end to endend of creating a workspace populating some data um updating some some data that's come from that populated data adding some new data and deleting some data so it's kind of that full idea of of managing the life cycle of data
• 07:30 - 08:00 so it's quite a trivial example so it's not it's not a huge model but effectively it's one that just allows me to kind of demo all the key parts of of a workspace without kind of being being making it too big and too complicated so what I'll first of all show you is the my my Baseline okay so so I've created a baseline architecture it's called Baseline architecture 2024 and it's got hardly anything in it so it's got a few processes and a few capabilities and I'll just show that as a visual ation so you can see there's a
• 08:00 - 08:30 hierarchy and what you've got here is an imaginary human Capital Management platform and I've i' broken it into two sections so there's there's an absence management part and a recruitment part and so this goes down here and then we've got the recruitment going down here what what I plan to do is create a workspace that goes down this right hand leg so so the recruitment side make some changes and then applies them back so that that's that's what it looks like right now uh so the first thing I'll do now is going create my
• 08:30 - 09:00 workspace so I go to the three dots menu under models and I choose add workspace and I'll call it what I always call it which is uh DBS project and then I'll link it to the appropriate parent which is based on architecture 2024 and I create my model my my workspace a biggy pardon there we go so the workspace is created and the first thing it does is prompt you that if you want to populate your workspace then
• 09:00 - 09:30 um the the kind of recommended way is to use reuse so again you don't have to populate stuff in from from a parent model you could just import new data so so this is me taking existing data because because I want to make a change so I'll go back to my view now and I will highlight the items I want to sorry highlight the items I want want to move and I want that one that one that one that one and that one so so I'll select these these objects
• 09:30 - 10:00 and by default it will copy the relationships as well so I'll do reuse reuse selected and then I'll choose again because um workspace and models are so similar they appear in the same list so there's there's my workspace I choose reuse and then I will do a little bit of fiddling around a second with a view to make it all work so I'll hop back to public views I will fire this one I'll just add the
• 10:00 - 10:30 workspace to the filters so again this works exactly like models it's it's it's very very familiar and I'll just pick the workspace again same thing again there we go run the filters quickly save it and now what what you can see is
• 10:30 - 11:00 exactly as I described earlier is you now have the the right hand leg of that original um model so I only want to do a part and and it's this particular part I don't I don't want to confuse myself although again the original model is quite small I don't want to confuse myself I'm just getting the bit I need okay so so there we go it's in there so that's the visualization and the first thing I'm going to do is change some of the content we've got in this reused um model in this reused objects so I choose human Capital Management that's
• 11:00 - 11:30 the first one and when I click edit here this is this is one of the key changes or differences between work spaces and models so if you had reused content in a model then you would have to effectively decide whether you wanted to link or unlink the data okay so so if you if you left it linked that it would update the um original model the original content as well if you UNL it then you'd break that link and you'd manage a variant with with workspace is that sets all
• 11:30 - 12:00 gone um and it's all managed through the the workspace itself because we know you're in a workspace then the changes get merged back as part of the merge process so in actual fact you could just make changes so just go yeah adding oops can't type adding description okay so I add that I'll put uh T some of the categories just to make it look better when you do the merge and then well pop my name is the owner here we go and you get let's give it not that
• 12:00 - 12:30 let's give it a criticality number in there as well so made some changes so first thing I will just pop back to the content view just to illustrate something here so if I go back there and I now switch on both the workspace and the model and what you can see already there you go there's there's the use and that added description has come
• 12:30 - 13:00 through but it hasn't been reflected back to the Baseline even though you know there's no linking or unlinking it just happens because that's how the process works now okay so that that's that's updating data okay so next bit I will do sorry just I'll go back to my public View and I just quickly Show fact don't that the next thing I plan to do is add some data okay so I'm going I'm going to add an application and an application serch so I'm going to have an
• 13:00 - 13:30 application and that's the first bit is I need to do a quick tweak here because there's in my environment there's a change that hasn't come through yet which is coming through tomorrow so in here I just need to update the permissions and do this right and if all goes well and I hope it does then what should happen now is I can now create
• 13:30 - 14:00 yes there we go so I'm going to add something called DBS manager or DBS check manager beg you pardon so that that's an application as get another description leave type it I do description because description is easy to um spot when when you're doing the the merges so it's not the only thing that can change I promise you there you go I'll pick some other numbers in here just just as as a random um proof that that's there so I'll save
• 14:00 - 14:30 that change I'm now going to um link that to some of the other content so I'm not going to link it back to candidate screening so there's a process called candidate screening sorry I just got my model that links up to candidate screening I'm going to do another one so
• 14:30 - 15:00 I'm going to do um create a new object a new application service and it's called DBS service okay now if I go back to my public view you can see the effect of this so
• 15:00 - 15:30 again I'll pop into a visualization and sorry I've chosen the wrong one beg you pardon there we go that's better so um so now you can see that in in the workspace um I've added these two items so I've reused I've updated and I've added and now I want to delete so um delete Works in in two subtly different
• 15:30 - 16:00 ways which is why why I've kind of highlighted these things so I plan to um in my in my wisdom I've decided that I no longer want DBS Services I put it in the in the in the workspace but I decided I don't need it um but I also want to remove manage offer which was something that I reused from the Baseline okay so so that's that's a reuse and that's an existing one but they're both going to be deleted so I'll switch back to list View and then I will highlight the deletion so we're going to get remove DPS service and we're going to remove move manage
• 16:00 - 16:30 offer and then delete selected content okay so so with that I I think um my my design is now done i' I've as I said I've I've reused some data updated it added some data and deleted some data so we kind of gone through that that whole qu life cycle um the same thing applies to relationship so if I were to go back and and um change a relationship ship then again I could put something in
• 16:30 - 17:00 I I won't choose that one because I've just that's the same one that's linked to the um human Capital Management let's do this one okay there we go just to prove it's live okay so there we go just just to prove relationships work as well so that that's it as far as far as the workspace changes are concerned now the next bit
• 17:00 - 17:30 is is to merge it all back so this is where we're now in the same kind of process as we have for um model merge so this this is by and large the same process I'm going to um choose a merge request and if I do new merge request there's a subtle difference that if I pick um you'll see now that I've got workspace and and and models separated so that these are grouped together to make nice and easy to find if I choose the one there we go choose um choose project it tells you it's a child
• 17:30 - 18:00 workspace there you go so you know even even here that it's a workspace and by default it picks the parent model as the target you can change that if you want to but by default um it will pick that as as the as the target so next step is to do review merge so I guess some of you may have seen this when you when you've done merges um with model merge but again it's it's it's the same process and and hopefully I might actually be able to show you the next steps if it works but so fingers cross that works won't be in this one it'll be in another environment but I'll show you something else
• 18:00 - 18:30 so as you can see these are the changed objects so I added DBS check manager I deleted manage offer and I updated human Capital Management so again the delete there's there's nothing you can do there there's no link it's gone it's being marked as a delete um if I hover over DBS check manager um you can see the link and if I click on the link it'll open up object details okay so there you go you can see the content if you want to go in and and see the exact cont content that's in that object you can do um similarly for
• 18:30 - 19:00 human Capital Management you can do the same thing but for updates um you can also do this so you can actually see the difference you can actually see what changed between the um your chosen Target model which in this case is the parent model and the workspace so you can see that there's the two um model and and workspace I've added owner I've changed CR criticality current added a description then and added categories as well and obviously if the if these had values in the you see the differences between the two as well so that
• 19:00 - 19:30 highlights the differences so that's a nice quick way of of showing the differences there's also a relationships Tab and in here you can see the relationships that are impacted so this relationship was effecting kind of implicitly deleted so because I deleted manage offer the relationship that was between employee on boarding and manage offer is also marked as delete it's not a mandatory delete yet because I haven't actually selected manage offer to be deleted so these these the effects of
• 19:30 - 20:00 the change we have on the Baseline okay so um but again I will go through I'll start and changing stuff and on this one this this one tells you that you can't merge the relationship unless you mark the source and Target objects as included so in this example because DBS check manager only lives in the workspace you can't actually merge this relationship back until both elements are either would be in the merge or in or in the parent model so there's there's some kind of validations there to make sure you can't kind of you know
• 20:00 - 20:30 um merge things incorrectly so first thing I do is I'll tick some of these now so I take them for merge and as as soon as I tick it you see the merge button becomes enabled um I'll just kind of highlight um again I'll do all these three actually so you you'll see the effect then on the relationships so I'll do that um I'll do something else I'll save and leave as well so if you've got lots to do you can Mark stuff as being uh ready for merge and come back later so if I save and leave
• 20:30 - 21:00 I need to go and find my thing again so I it is the this one here so DBS project into Baseline architecture and you can see these are these are marked as merge and then with the relationships you can see that now this one has become ticked so it has to be deleted because I'm I'm deleting the parent and that's what that message says as well and then I can then choose to uh pick the other relationships to be
• 21:00 - 21:30 emerge back as well if I didn't pick um a relationship to emerge back so if I didn't pick this relationship then DBS check manager would get merged but the relationship wouldn't so the relationship would remain in the workspace and I could merge it back at the later date so kind of this this is the idea this this incremental approach to merging where you can kind of choose what you want and so you can almost do it if if you run in Sprints you could do on a Sprint by Sprint basis you could just just say that's what's changed in this Sprint I can now merge that back and have have my Baseline reflect almost
• 21:30 - 22:00 on on a kind of Sprint by Sprint basis the the you know level of accuracy okay so that's it I'm just going to clear out my my notifications just clear all um when I when I when I push the button um if it all works properly and it should do then um the merge will run and what you will see or won't see is um the manage offer has been removed from the parent model and DBS check manager has been added plus
• 22:00 - 22:30 all the changes that have been made to um uh human Capital Management and the relationship that I changed as well so um hopefully I'll be able to show you all those so I'm press the butt Jonathan yeah oh sorry sorry we' we've got a bunch of questions coming in um a lot of them I think we can tackle at the end but since you've got the environment up can you just talk quickly about there's uh what's the difference between the square merge check box and the round check box on the left of the s okay yeah this this is one that makes
• 22:30 - 23:00 me sad so so the the the round one I'm not sure sorry I put the wrong one that's one I just done um sorry the round one is oh I've got n got anything in them let me just find one that's got some stuff in it have I got any active ones no I haven't they're all closed um that's that's for future state so so we're one one of the things we're looking at is improving selection so so like bulk select to kind of you know merge things you got or drag and and we had that there as something we were
• 23:00 - 23:30 going to do we didn't implement it so that so that one is is kind of future State we probably should remove it I'll be honest with you because it's kind of there on the left hand side the one that actually does the merge is is that column marked merge so that's the one you need to tick too and enable it to be merged back in okay thanks for clarifying okay any any other questions want there or should shall I um hop back uh we've got we've got quite a a few um there's a
• 23:30 - 24:00 couple questions about what kind of licenses you need to um create workspaces in to do the merge um do you want to just check about chat about that quickly yeah so that's that's a good question so um we it is a good question actually so well I I was going to say we were G to lock it down to Authur but the reality is that we don't really need to because it's all about the data you've got access to really so we're at the moment we're not going to we're not going to lock it down to any any
• 24:00 - 24:30 particular role um but we we reserve the right we may do that so at the moment I think anybody could get there the reality is that if you didn't have access to very much data you can't you wouldn't see it all here okay so one of the things that sorry one of the things that we will do I think is is um it will be authors and contributors that will have access to the data and I think viewers will probably be limited to view okay thanks I think I think that that was exactly what I was about to ask
• 24:30 - 25:00 so yeah yeah yeah you beat me to it okay um let's see there are there's quite a few so yeah let's let's go ahead and round this off yeah so just just to show you what what I was talking about there we go so um we've added DBS check manager um as you can see there's no longer manage offer there we've got all the silly descriptions I added in here uh again um to also to the relationship as well so that's kind of the round trip the whole bunch of changes got made ads updates deletes and as part of that
• 25:00 - 25:30 merge process then they were all applied back to the parent model and that's that's kind of the roundt trip sorry Kelly you g to say oh no go ahead I was just goingon to say we we'll catch the rest of the questions at the Q&A section okay I'm I'm going to try and go slightly off and show you something else as well so this this this is our development environment I can't guarantee it will work because it's it's used for development so sometimes it's it's being used for deployments and if we get lucky looks like we might I'll show you
• 25:30 - 26:00 the next bit of the merge request so what we're working on right now is in the merge request I hope this has got some stuff in it this one this one's been completed okay so the one you saw when it completes it just tells you it's completed what we're building right now is when it completes it tells you what was in the merge so you can go back so for each merge that you do you can go back you can look at when it was
• 26:00 - 26:30 completed what was in it um did it did it pass did it fails you know so because case there'll be failures I think you know there reasons why locked objects for example may cause problem so uh um these are kind of things there go item wasn't merged so these are examples where we've deliberately try to show you the the the edge cases here so so that's what we're working on for the future as well so not only have you got the merge you've also got this kind of audit and governance piece that sits on the other side so we we're building this right now that that's coming coming soon and we'll be added to uh what you've just
• 26:30 - 27:00 seen yeah so that's that's that's kind of it for the moment so thank you great should I stop sharing um I'll I'll take the screen back give me just a second here no appreciate it um but yeah keep the environment up in case we need to dig into anything q& a awesome okay share okay cool all right yeah thanks for taking us through everything Jonathan um again really excited to see see how people take advantage of the the workspaces functionality
• 27:00 - 27:30 um uh just a couple of T tips and tricks that we put together um you know as you're thinking about how to use workspaces in in in your environment um of course you know think about first of all how you want to use these workspaces and make sure that everybody's got the sort of same base level of understanding and um you know what kind of naming conventions do you want to set up do you want to set up a workspace for every architect do you want one for every project do you want to be able to have
• 27:30 - 28:00 folks just spin one up as they need um entirely up to the you guys individually uh but definitely wor some thought up front um so just to keep things from from going crazy so so that that's a good point actually so at the moment we we've gone with a fairly I kind want to say permissive approach that the idea is that it's it's there for people to kind of use and explore so it's not really locked down um because obviously there's no kind of Licensing stuff so kind of go yes it's there as as an expiration tool um so that does mean that people can go go and create stuff uh the where
• 28:00 - 28:30 where we've put governance in is you need permissions to the Baseline to merge things back so so if if you you need like kind of read update or delete permissions to the Baseline in order to merge things back so the the idea being what you can do um as a as a somebody who's who's kind of looking after the main repository is you can reduce permissions for people uh on the base repository to read and reuse which means that I can then create a create a workspace I can then um reuse content into my into my workspace but I can't
• 28:30 - 29:00 actually merge back because I don't have permissions to merge back so rather kind of go with a really complicated um permissions model out the gate we've gone with something quite simple but there are kind of few rules to it to to make it kind of work okay thank thank you for clarifying yeah so if we if we don't want people to make those changes just give them read and reuse only yeah is that right yeah I mean because the idea is if there's not some kind of level of governance there's you almost don't need work spaces because if if you're everyone to update the Baseline then you kind of like you're fine you're
• 29:00 - 29:30 just you know you're happy it's if you want more control and more governance so yeah perfect okay thank you cool um yep just a couple more tips um if you want to bring data into your workspace quickly um versus having to go through your Baseline and pick things out one by one uh you can create a list view pretty easily apply the the filters and constraints that you want and then reuse the entire view into the workspace boom everything's there um pretty pretty simple and I think the last one Jonathan
• 29:30 - 30:00 you and I talked about yesterday um if you extra extra cautious and you want to make changes in experiment but you don't want to mess with your baseline or your workspace um it's pretty easy just to copy them over into like copy your model and your workspace over um test what you want to test experiment and then when you're done you can just delete those out so you can do kind of a kind of a dry run just by copying things over really quick yeah cool yeah Abol um I think that about covers what we had
• 30:00 - 30:30 for today uh we do have a ton of questions so I'm going to try to get through as many as we can okay so I'm going to start from the bottom okay yes um we talked about permissions Jonathan do related documents or counterparts move with the objects when reuse I think uh no counterparts don't no there's there's um there's more work to be done on counterparts I think is fair to say uh let me think about documents good question I don't think they
• 30:30 - 31:00 do okay do we want to just double check double Che I'll go back that one yeah yeah yeah that's an open question I'll go back on that one great um cool do so talked about permissions can we use Vio to create objects in a workspace you can so so I I said that you you absolutely 100% Can what you need to do to make it work best for you is to do that first step so if you're reusing content from your parent model for example it's best to do that and then
• 31:00 - 31:30 and then use your workspace to design your your Vis diagrams what we haven't got yet because you know um we were kind of um working along along in Tander with the guys who who are doing draw is we don't have a deep integration into Vis it it fundamentally works because they're basically models but yeah you want to kind of create that content have that reuse there in the first place you can't kind of reuse you can't reuse into a um workspace from Phio if if that
• 31:30 - 32:00 makes sense got it okay thank you okay so we talked about permissions uh we talked about this one um ah so in terms of performance um or I guess limits in the number of workspaces do we have a hard limit set or is it right now it counts towards your your model total so they are um yeah they do count towards your model total so they would be of the that limit got it okay so and I believe that's 100
• 32:00 - 32:30 yes normally yes okay very good but again part part of the idea of this and this this is why I I showed the the merge request as well part of the idea of this is that we provide enough information and governance and audit that you don't need to keep your project workspace for example or your um or your project model because there's enough governance in in the merge to tell you what's been merged back and there's no reason to kind of keep the other one just in case that that's kind of the idea and maybe there's more work to do
• 32:30 - 33:00 questions around documents and stuff is interesting but that's that's kind of where we where we're TR you know tracking towards cool thank you um okay um can we undo a not in what no I mean happy manual so so you know if if it was problematic then you can use and it'd be horrible to do it if it's out of any any any size um you have the ability to revert in the
• 33:00 - 33:30 history of an object you'd have to do at the object level there's there's no blanket reverse the the um reverse the the merge process because the fact you know there a whole bunch of stuff where it you know changes objects and looks for reuses and matches all back so it's so it's not an easy process to undo now but that's also to your point Kelly why it's worth doing the experimentation with you know if you want to copy it and try it before you merge it back then that there's opportunities to do that to make sure it's right before you merge it into your your Baseline thank you all right good point um what
• 33:30 - 34:00 happens when somebody changes a baseline object after I've reused it into a workspace Baseline object after you re it into workspace um and the answer is it depends okay so if you've if it's an attribute that you haven't changed that will come through so it works exactly like I don't if you're familiar with with um in the same way as reuses inv variance right now but but what it is is they're kind of taking care of on your behalf so so if you make a change to um
• 34:00 - 34:30 an attribute in in a reused object sorry in an original of a reused object in a in a parent model um and you haven't changed it in the workspace that change will just apply so it will go one way so it'll go from original to workspace and it will just go yes I've now updated this is the new the new state of my object in my workspace if you've changed that attribute so in that example where I Chang description I could I could change it also in the parent model and and that wouldn't then apply to the parent mod to the to the workspace
• 34:30 - 35:00 because it knows there a difference so so this kind of idea of of um this safe space is it means that you can what it means is that you can you can update your Baseline with other workspaces so if if you're if you're kind of running running transformation at scale and you're merging multiple Works spaces back into your Baseline you kind of want those changes to to impact a workpace that you might merge back so any change you you made that kind of safe changes will be applied anyone where you've got a difference you'll see
• 35:00 - 35:30 there a difference in the merge if that makes sense great yeah so changes flow down unless you've made a change in the workspace and then you'll see it exactly before yeah okay very good um so do you want to maybe talk a little bit about when you would want to use a workspace versus just have a separate model I think we'll end on that yeah yeah I mean it's when when would you do it I I guess if you want so I I think the key place I
• 35:30 - 36:00 mean if you look at use cases I think there are many use cases you could use it for so many the kind of the what we considered to be um all this Infinity um use cases would would work but eff anywhere where you want to explore where you want to play where you want to try things out so it's great as you said solution architecture it's a great one for that because you can you can do it you can you can you know you can um well one thing you can do is you can also copy workspaces so if if you get it to a certain point and and you um you've created a workspace and you want you you
• 36:00 - 36:30 want three options you could you could have three options that different in in different workspaces for example that's one way of doing it so very much around that experimentation piece I've not tried this but I think you could also do APM in it so if you have your changes in your workspace you can kind of capture those changes before you apply them back to um the Baseline so I think that's another one what we could do I think there's plenty of of of areas where having a having a safe space to apply change before you merg it back kind of like sense got it okay yeah kind of like
• 36:30 - 37:00 a little little scratch Pad kind of just yeah yeah also without having all of the data contained in the model to sort of confuse you can just pull in what you need absolutely yeah and again you know if you want to start from scratch again you don't have to reuse you could use again this is the other advantage of of the some of the kind of design choices we made is is all the other functionality work so if you want to use um Excel input you can Exel input directly into your workspace for example
• 37:00 - 37:30 and then you could then apply that as as a merge back to your parent model yeah they all work in slightly different ways they they do match by um the merge process um for reuse kind of matches by ID or or identif identifying attribute but it also matches by name as well so if you've got things that that are the same object type and the same name it treats that as a match and goes well actually I think this this is these changes should be applied to this object so it kind of works that way as well great okay yeah apologies I know we've
• 37:30 - 38:00 got at least a dozen other questions maybe that that we're not going to have time to to dig into today um but uh we do have them captured here and we'll we'll definitely follow up with those that we didn't get to address after anything that we've got I I will make sure it get answered yeah yeah thank you yeah also feel free to uh we have a h in the community a workspaces uh thread or sub Forum um feel free to post those questions there um that's that's monitored pretty pretty
• 38:00 - 38:30 closely so we tend to get back get back to people as soon as we can so right cool all right and so I think that about covers it for today um but before we wrap I just want to give you guys um just a little heads up about our our next couple of webinars um next week on the 20th we have Conquering the silent killer overcoming technical debt and Enterprise modernization um that's next week Wednesday at 10:00 a.m. eastern time 3 p p.m. BST and then on Thursday
• 38:30 - 39:00 December 5th we will have to draw or not to draw where diagramming drives transformation so that that'll be a good one as well um Thursday December 5th 10: am. Eastern 3 pm BD right cool and uh that's it for today's session Jonathan thank you so much for sharing this with us uh for taking us through I'm really excited yes do um do we have an this this functionality should be coming within the next few weeks I believe yes y yeah
• 39:00 - 39:30 so we're we're finishing it off so so we as you saw that that that um that merge process there's still more to do there so we kind of haven't quite anchor on on on a date yet because there's still a little bit more to do but yeah in next few weeks they'll be there yeah next few weeks yeah just in time for Christmas we hope yeah absolutely yeah again thank you so much Jonathan thank you to everybody who attended I hope you found it valuable um if you've got any additional questions uh feel free again to post them in the community and um if we've got them here we'll we'll follow up with you guys directly all right
• 39:30 - 40:00 appreciate everybody's time take care have a good one yeah thank you thanks so byebye