What issues we foresee with Multiple Org implementation?

[sathalye]

With Multi Org we can achieve separate Business processes, ACLs, Objects etc. What issues we might face in future?

I know its more inclined towards Business Need but what design consideration should be taken care before making a decision.

Few points

-- Any data sharing issues?

-- how to handle configuration , change of common parts?

Regards

Sameer

[BineshKumar1]

As you rightly said it is more of a business call. If you have different departments working on same category of product line, then probably group based ACL would be good enough, if your enterprise has divisions working on different product lines then Org containers make sense. So do with the workflows and LCs

Data sharing works great in 10.2  with multiple organization. In fact a lot of limitations with Multi Org  in 8,9 version has been fixed in 9.1 and 10.x release. You can view,share and move data between multiple organizations.(You can't move products/libraries though) . System supports principals from multiple organizations to be part of workflow/team and can be used for change.

One another thing you should be aware of is - Organization level uniqueness on business objects not available from 10.x onwards.

Thanks

Binesh Kumar

Barry Wehmiller