AppointmentService caches the wrong clinician for appointments --------------------------------------------------------------

Key: ARCH-43 URL: https://openvpms.atlassian.net/browse/ARCH-43 Project: Archetypes Issue Type: Bug Affects Versions: 1.5-beta-1 Reporter: Tim Anderson Assignee: Tim Anderson Fix For: 1.5

If an appointment has an author participation, this may be cached instead of the clinician associated with the appointment. This is because ScheduleEventQuery pulls in all participations for an appointment but doesn't check the participation archetype. Instead it relies on the participating entity's archetype - in this case it is security.user for both participation.clinician and participation.author.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf