Fixed
Testing on public sandbox on 28th October generated the following (more testing to be completed on 29th)
- Page for creating/editing a contact which is a subtype extended from the main 3 types has a random 'subtype' label to the right of the name fields at the top of the form - not sure it should be there. [Re: That was frozen subtype. We have updated the page to not show the subtype at all for this particular case.]
- Having created a new custom data group, and used it on a record I then went back to edit which relationships it applied to. Assumed I would click on 'More/settings'. This brought me to the edit page for the group, but the 'Used for' field is hidden and so cannot be edited... [Re: display has been fixed. For adding support to allow adding more subtypes we 'll be filing/updating the issue. ] -> [Re: CRM-5143]
Testing on the public sandbox on 19th October generated the following points. These are not all necessary 'bugs' but observations from the team in using the new functionality.
- Relationship Report does not take account of sub-types. CRM-5259
- The related contact exporting functionality (Jira 5096) does not seem to be working as we would expect (we have tested the standalone functionality from WebAccess successfully). Basically, fields are selected, but fields for related information do not come through in the export. CRM-5256
- Having created a new contact of a particular sub-type, when I press 'Save & New' the 'create new contact' I am offered is the parent type, not the subtype
- When viewing or editing a contact of a particular sub-type how do I know which subtype it is? Should there be some kind of indicator at the top of the page? [Re: Contact view screen shows subtype value if set. Was fixed in r24315]
- The administration of sub-types not currently working
Testing on public sandbox on 28th October generated the following (more testing to be completed on 29th)
- Export templates not saving (Lianne) [re: verified for r24744]
Testing on November 3rd (build 24756 on our own SVN setup) shows a problem with the edit, print, activity, dashboard buttons on the main contact view. See attached. We don't think it is to do with our style sheet, but might be. Can't replicate on the sandbox as this is currently broken for contact view...[Re: sandbox has been updated. Can you 'll have a recheck]
Alpha update 9th November: This problem does not show on the public sandbox, but I am told that it is not something we have done on our style sheet. Help? [Deepak: Update: This is now mostly resolved. It was the setup issue (multiple civicrm codebase inside modules dir) which was causing the problem.Alpha 'll do a test install/upgrade to v3.1.alpha1 and update this page for any issues Alpha International: Issue did not appear on clean install of 3.1Alpha]
Won't Fix
Testing on public sandbox on 28th October generated the following (more testing to be completed on 29th)
- Creating/editing a subtype extended from an organisation or household means the main 'name' field is labelled 'Individual Name' or 'Household name. This would be a little confusing for a 'course' subtype. Could the field label be changed to just 'Name'? [Re: This can be achieved by custom templates OR overriding the template. There was also an issue fixed w.r.t - CRM-5128]
- Not really part of our spec, but... I noticed that even though when I created a new custom data group withoutticking the box 'Collapse on initial display', when I now create a new course, the 'Custom Data' section is collapsed so it is not obvious at all that there is a mandatory field to complete... [Re: Its by design. 'Collapse on initial display' box is meant for fieldset and not panes. Lets discuss if its unclear.]
Do we have to represent subtypes with the indent beneath its parent contact type? We would not want to show them in that hierachical way.

2 Comments
Hide/Show CommentsOct 21, 2009
Lianne Dee
I cannot see these changes in the Sandbox?
Oct 28, 2009
Lianne Dee
We have seen that these changes have been updated in the Sandbox and everything is working as expected.
I've also had a look at the Relationship Export and everything is working as expected, expect that it does not seem to be remembering the "Saved Field Mapping". I cannot access a field mapping that I've previously saved.
Thanks,
Lianne