Hey all,
We're looking at JSM, and I was wondering what's the best practice when it comes to multiple JSM Object Schemas.
Does it makes sense to build one hug schema with a lot of hierarchy within it? Or, instead, use many different Object Schemas, one for each purpose?
How many object schemas do you use in your organizations?
Thanks!
@liorn -
Are you referring to Assets Object Schema? If so, we have different object schemas to support different business operation units to fulfill their needs.
Ideally, it would be great to have fewer schemas to manage/support the different business units. However in reality, it may also cause limitations/possible collisions when you have too many users with the create/edit rights within the same schema if not properly trained.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
Thanks @Joseph Chung Yin , that's helpful.
I wonder if you can share, eventually, how many schemas do companies you're familiar with end up with. Seems like it shouldn't be more than ~20 or so according to the guidelines you wrote?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.