[OpenVPMS Developers] [JIRA] (OVPMS-1120) Messaging enhancements

Message from Tim Anderson (Created) (JIRA) jira@openvpms.org

Messaging enhancements ----------------------

Key: OVPMS-1120 URL: https://openvpms.atlassian.net/browse/OVPMS-1120 Project: VPMS Web Application Issue Type: Improvement Components: Workflow Affects Versions: 1.5.1 Reporter: Tim Anderson Assignee: Tony De Keizer

Extend Messaging to: 1. send a message to one or more users 2. forward a message to one or more users 3. reply to sender with message editing 4. forward a message with message editing 5. increase the Notes field to be more than 255 characters 6. send a message to one or more user groups 7. forward a message to one or more user groups 8. enable message deletion

This requires the following changes: * create new participations participation.toPending, participation.toRead, participation.toCompleted, which links the 'to' users to a message. The Pending, Read and Completed portion of the archetype indicate the status of the message for the user. This is a workaround for the fact that: ** it must be possible to query act.userMessages by user and status ** there is no appropriate indexed field in participation other than the short name to query on * remove the status node from act.userMessage * change the act.userMessage to have multiple participation.to* participations, instead of a single participation.user * rename the act.userMessage notes node to 'subject' * add new act.userMessage notes node, with 5000 character limit * migrate existing act.userMessages * add new archetype entity.userGroup that can be used to group users * add admin UI to create, view, update, delete entity.userGroup * change the act.userMessage editor to enable selection of multiple users or groups. When a message is sent, user groups are expanded to their corresponding users, and participation.toPending are added to the message to link the users. * change Messaging workspace to: ** change message selection to mark the selected act.userMessage read, by removing the existing participation.toPending and replacing it with participation.toRead, for the currrent user ** change Completed button to change the selected act.userMessage's status by removing the existing participation.to* and adding a participation.toCompleted for the current user ** add Delete button. To delete a message for a user, their 'to' participation is removed. When the last 'to' participation is removed, the act.userMessage is removed ** add Reply button. This copies the selected message, sets the 'to' address to the 'from' address (using participation.toPending) and displays it in an editor ** change Forward button to copy message with empty 'to' addresses, and display it in an editor

-- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://openvpms.atlassian.net/secure/ContactAdministrators!default.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

Syndicate content