CiviCRM Community Forums (archive)

I do know that originally orgs couldn't be assigned as clients, so whenever that addition was made probably the corresponding role code was never updated. Ideally it would limit roles to the A-to-B (B-to-A?) types that correspond to the client type.

I don't remember the original reason for it, although looking at old wiki spec documents it suggests the original intention may have been partly for access control which I could see being a little more complex with relationships to orgs, but it may also have just been a decision of the form "we don't need it now and there's more important things to fit into the budget".

As a workaround, depending on the situation, an org that has a role in a case is likely to be involved with several cases, e.g. your law firm, so you can add the org to the global case contacts group (as defined in settings.xml) and it will appear on every case.

I am not sure we are all talking about the same thing.

I don't want to now how to get around  the issue as I don't use CiviCase on a production site.

I have been testing the new 4.5 case configuration UI to write the documentation and I am just stating the situation and asking if that will be problem for people that do use CiviCase. 

The situation is:
In 4.5 you can only use case roles that are individual to individual.  You can add a case roles that is individual to organisation in the case type (eg Sponsoring Company), but when you want to fill that role you can only select from individuals and, of course, this gives an error and can't be saved. 

This fixes it along with a couple other misc improvements to that screen:
https://github.com/civicrm/civicrm-core/pull/4060

I just tried it in 4.5 as well as 4.6 and it is working as I would expect. As a test I added the "employer of" role to a case type, and then it prompted me to add an organization to that role (individual and household were not allowed, as I expected).