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]

Hi Kumaran,

you are welcome.

Kindly mark this as correct Answer if it has addressed your problem

[kumaran]

Hi Deepak,

I couldnt mark it as Correct as this discussion is posted by Cindy.

Thanks

[Deepak Ingale1]

No worries friend

One more suggestion, do not domain separate the existing or OOB table. Because, if you modify it, you own it.

If you are creating custom table, then you can domain separate it.

[Michael Fry1]

There isn't a way to convert those catalogs/catalog items. You have to build them in the different languages and then use the "Available for company" option so appropriate companies see the language catalogs they need to see. We have just over !,500 catalog items, and we haven't found any other way to do it.

[hblair]

Great discussion all - Deepak and Michael are right on track with this.   Workflows, catalogs, and ACL are not domain seperated and should be built in the global domain.   Then apply conditions like "Available for company" and add the company in question. Cindy, I would recommend that moving forward (especially with Fuji) that you build workflows, catalogs, and acl's in the global domain.   For all the items you have built already then keep them in the domain you built them in, unless they aren't working right.

Hank