Catalog best practices for MSP

[C_Hick]

Looking for any tips/tricks/things to consider for service catalog in an MSP.  

Getting to go live with our first of many catalogs...

Thought setting a condition of Domain = xxx on each workflow would ensure domain separation but it seems to just ensure the workflow fires on every item in that domain.

Looking for any input or advice from all you wonderful MPS gurus.

[Deepak Ingale1]

Hello Kumaran,

Catalogs and workflows are global in nature in MSP environment.

You can hide / visible catalog items with the help of entitlement scripts and entitlement fields present as related list on catalog item.

You can make it hidden / visible to company, group , user , department etc.

[kumaran]

Hi Deepak,

Thanks a lot for your reply. I can understood now . If we make it visible to only a particular company what about the variables used in that item? Is that variable will also be visible only to that company? If not, how to make that variables visible to that company alone.

Also how the workflows and catalog client scripts will be differentiated.

Thanks in Advance.

[C_Hick]

We used domain separation on all of our tables related to Catalog.   All workflows, Catalog items and variables have domain field that lets us keep things separate.   This was not out of the box and the domain field had to be added to all these tables.   It is much easier for reporting and checking when you are trying to see what items are in which domain.

[kumaran]

Hi Cindy,

Thanks for your reply.

We have a requirement that the people belog to finance group can able to see only those items related to finance team within the company.

It seems the "Available for group" is not working.

Please let me know if you have came across this situation in MSP instance and how you have handled this.

Thanks in Advance.

[Deepak Ingale1]

I think you need to make "Available to company" as well as "Available to group"