Custom Software Asset Workspace - Create a New Experience or Variant?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2023 05:09 PM
We have one instance serving two organizations for software asset management. Our requirement is to be able to have a separate Software Asset Workspace for each organization since their data is different. Currently, we are using the Department field to make this differentiation where it applies.
I've started looking into the components of the Software Asset Workspace and, while the UI Builder makes it easy to set up workspaces, it looks quite extensive and complex OOB. The current options I see so far are:
Option 1: Create a variant for each page of the workspace.
- I'd need to create new roles for each organization
- BUT can I customize the data source for each component in the variant (org requirement)?
Option 2: Create a new experience
- I'd need to recreate each component on the workspace
- Is it possible to move a variant from one experience to another?
Option 3: Create a script to copy all components of the OOB Software Asset Workspace (doable according to a separate post)
- Seems like a lot of work up front assuming it works without any issues.
Which of these 3 options would you recommend and why? Any references would be helpful and appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2023 08:52 PM - edited 04-10-2023 08:53 PM
Have you looked at Domain Separation? If you have one instance, but support more than 1 organization, that is exactly what Domain separation accomplishes. This will be the case for all Modules, not just SAM.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2023 03:08 PM
We have had a similar requirement in the Incident space. I have found it to be pretty easy to use the same workspace for both. The workspace itself is just a shell. Then, create differing variants for anything that needs to be different between the groups. You can set the view rules for each varient so that the different teams, using the same workspace, just wee their own variants.
I tried going down the road of creating the custom workspace, but it was way more pain than it was worth. I would stick to 1 workspace with multiple variants.
https://youtube.com/watch?v=zYi8KhP9SUk