search

rbeckman-nextgen / test-mc3

0 stars 0 forks source link

Prompt to remove QUEUED messages too when the user chooses "Remove Messages" #1354

Open rbeckman-nextgen opened 4 years ago

rbeckman-nextgen commented 4 years ago

Now, Mirth removes all messages (including QUEUED ones) when the user selects "Remove All Messages", or "Remove Results"

IMHO, MIrth should ask for confirmation to the user about including QUEUED messages, as it's too easy to remove unsent messages when you're cleaning the dashboard.

Imported Issue. Original Details: Jira Issue Key: MIRTH-1376 Reporter: albertosaez Created: 2010-03-29T06:43:07.000-0700

rbeckman-nextgen commented 4 years ago

Postponed until improvements are made to system wide queuing because at this moment we cannot ensure that more messages will not be queued during this operation.

Imported Comment. Original Details: Author: jacobb Created: 2010-03-29T17:44:30.000-0700

rbeckman-nextgen commented 4 years ago

Please, consider this patch to this issue. The approach is very simple:

1) When the user select "Remove all" or "Remove results", then mirth ask the user if he wants to exclude the queued messages from the removal process.

2) A new parameter is passed to the clearMessages and removeMessages methods to confirm if the queued messages has to be excluded or not.

Imported Comment. Original Details: Author: albertosaez Created: 2010-03-30T12:26:58.000-0700

rbeckman-nextgen commented 4 years ago

To do this properly we should update the message object filter to support accepting multiple statuses. This would allow us to have a filter that includes all messages besides queued messages. A prompt would allow the user to include or exclude queued message.

Imported Comment. Original Details: Author: jacobb Created: 2010-06-28T15:40:23.000-0700

rbeckman-nextgen commented 4 years ago

Updated patch for version 2.1.1

Imported Comment. Original Details: Author: albertosaez Created: 2011-10-09T14:02:54.000-0700

rbeckman-nextgen commented 4 years ago

The advanced message filter now supports multiple statuses, so the user can remove all messages besides queued by doing the appropriate search first. The "Remove All Messages" and "Remove Results" options now also indicate that queued messages will also be removed.

Imported Comment. Original Details: Author: wayneh Created: 2012-12-04T14:56:29.000-0800

rbeckman-nextgen commented 4 years ago

Users aren't fully able to isolate all non-queued messages and delete them. If the user searches for messages with status != QUEUED, it will still return the source transformed message for destination messages that are queued. If those results were deleted, the queued messages would get deleted along with them.

If the user searched for status != QUEUED and status != TRANSFORMED and removed those results, then source transformed messages would not be deleted even if no messages are queued on the destinations.

In order to allow users to optionally include or exclude queued messages when removing, we may need to add additional options to the search criteria.

Imported Comment. Original Details: Author: brentm Created: 2012-12-20T13:28:15.000-0800

rbeckman-nextgen commented 4 years ago

Add a warning to Remove Message and Remove Results, explaining that removing a Source message will remove all of its destinations.

Imported Comment. Original Details: Author: wayneh Created: 2013-03-13T17:12:54.000-0700