Details
Major
Description
Using the sample case configuration, if I create a case (type = Adult Day Care Referral), I can assign a contact to the 2nd Case Role in the list (Health Svcs Coord). BUT, if I try to assign a contact to the THIRD case role (e.g. Benefits Specialist) - the auto-complete widget doesn't work properly (I get doubled-up listings) and although I can select a contact from the lower listing - I get 'unassigned' afterwards (no relationships is created).
Screen shot attached to clarify.
Attachments
Issue Links
- is supplemented by
-
CRM-6091 Case roles (relationship types) where either or both contact types are a subtype of Individual should be supported
-
- Done/Fixed
-
Activity
If this recreates on 3.1 demo (as indicated by Shawn Duncan), we should fix for 3.1.4 and 3.2.
Just recreated on the civicrm.org drupal demo.
It seems line functionality is working fine for my local install as well as on demo site.
It would be great if you give some more insight/steps to replicate the issue.
thanks.
One suspected issue w/ relationship creation for 'Benefits Specialist' might be :
you are selecting Individual / Household contact to create relationship and this role require contact type should be Organization.
Do check here : http://drupal.demo.civicrm.org/civicrm/admin/reltype?action=view&id=13&reset=1
- Showing meaningful message to user for selecting proper contact.
User guidance text would help alot - thanks. I get a similar behavior, so probably from the same contact type problem, in a custom case. In implementation, if I have a contact subtype of Individual defined: Applicant. I have a relationship defined for use as a case role. If I define the relationship to be between an Individual (contact a) and an Applicant (contact b) and open a case for an contact of subtype Applicant, then attempt to assign an Individual type contact to the role, the result is the same "undefined" text even though the a->b types are correct for the relationship def. If I switch the relationship to be between Individuals (no subtype on contact b) then the "Edit Case Role" button assignment process works properly.
Are we handling sub-types properly in CiviCase?
Main cause of the error I reported was misconfigured relationship types in the sample configuration data (2 of them had 'Organization' as contact_b - which is not supported currently).
I am filing a new issue to deal with support for contact subtypes (of INDIVIDUAL only for now), and to improve the error handling. We'll implement for 3.2 and if relatively simple will also backport to 3.1.
Issue reproduces on my ver. 3.1.3 sandbox with the Adult Day Care sample loaded.