[OpenVPMS Developers] [JIRA] Issue Comment Edited: (OVPMS-891) Deleting a lookup should prompt for replacement lookup
Tim Anderson edited comment on OVPMS-891 at 11/18/09 12:24 AM: ---------------------------------------------------------------
This change has the following limitations: * batch updates are used which do not update persistent version numbers. This could lead to data inconsistency if an in-memory object is subsequently saved. * affected objects are cleared from the second level cache in order to minimise the above. There will a performance impact while caches are re-established * object validation is not performed on affected objects. * the UI checks version no.s to determine if an object needs to be refreshed. As the version no.s aren't incremented the changes will only be reflected in the UI when an affected object is subsequently edited.
Changes applied to: * framework, revisions 3469-3471,3480 * archetypes, revision 3474 * archetype-maven-plugin, revision 3473 * reports, revision 3475 * etl, revision 3476 * vpms, revision 3472 * release, revision 3477
was (Author: tanderson): This change has the following limitations: * batch updates are used which do not update persistent version numbers. This could lead to data inconsistency if an in-memory object is subsequently saved. * affected objects are cleared from the second level cache in order to minimise the above. There will a performance impact while caches are re-established * object validation is not performed on affected objects.
Changes applied to: * framework, revisions 3469-3471,3480 * archetypes, revision 3474 * archetype-maven-plugin, revision 3473 * reports, revision 3475 * etl, revision 3476 * vpms, revision 3472 * release, revision 3477
> Deleting a lookup should prompt for replacement lookup > ------------------------------------------------------ > > Key: OVPMS-891 > URL: https://openvpms.atlassian.net/browse/OVPMS-891 > Project: VPMS Web Application > Issue Type: Improvement > Components: Administration > Affects Versions: 1.3 > Reporter: Tony De Keizer > Assignee: Tony De Keizer > Fix For: 1.4 > > Original Estimate: 1 day, 4 hours > Time Spent: 1 day, 4 hours > Remaining Estimate: 0 minutes > > When a user tries to delete a lookup in the lookup workspace they should be first prompted for the lookup instance of the same type to replace all existing instances of the lookup being deleted. > This will require the application to find all archetype nodes that utilise this lookup and any instance of the old lookup code and replace with the new lookup code. > This is an important function in regards data integrity and should be implemented as a business framework method.-- 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
