Skip to content

Handle the exceptions and messages for the bulk processes [5] #12257

@carina29

Description

@carina29

Problem Description

In #11597 the bulk progress bar was introduced (for entities < 40 entities) for bulk editing.
For the following operations the happy flow and only some exceptions and error messages were handled:

The following were handled:
For < 40 selected entities:

  • if the user wants to delete an already shared entity (case/event) with Survnet but the call to Survnet fails in case of deleting the entity/entities.
  • an error notification (general exception in UI) will be shown if at least one from the selected entities was sent to Survnet and the Survnet communication is failing=> none of the selected entries will be deleted
  • if in the selected list of External messages there is at least one in "PROCESSED" status:
    the whole deletion will be aborted and a message will be displayed
  • if ineligible events are selected for deletion, a message will appear and those events will be skipped from deletion

For > 40 selected entities:

  • the ineligible entities( example events) will not be processed for delete/restore ( a message will be given if all the selected entities are ineligible or if some of the selected entities are ineligible)

Proposed Change

All the possible exceptions should be handled and proper messages should be displayed in the UI.
The handling should be done generically in BulkOperationHandler, for the missing scenarios.

Added Value/Benefit

  • filtering the not eligible elements before processing them
  • handling all the exceptions and displaying meaningful messages(with the proper reason) for the users
  • preserving all the old functionalities from past ( before the bulk progress bar was introduced)
  • solving the "blocked progress bar problem" which happens when more than 40 entities are selected and not all of the entities can be processed succesfully

Acceptance Criteria

Acceptance criteria:
For < 40 entities:

  • If multiple entries are selected for delete and some of the entries can not be deleted because of the communication with Survnet the following modal window should be displayed adapted to the entity ( case/event) and the eligible entities which do not need Survnet communication, should be deleted:

image

  • the above mentioned modal window should appear also for archive/dearchive/sending to reporting tool if the communication is failing with Survnet

  • if for any other bulk actions (except for delete) can happen that the items are ineligible, should be handled with a similar modal window with a proper message (the messages from DeleteRestoreMessages can be used as reference )

  • if none of the entries are eligible, a message should be displayed ( in case of delete , there is already implemented)

  • If multiple problems can appear during a bulk action ( for example ineligible item and exception from Survnet) in the above given modal window should appear the list of ineligible items , a list of items which could not be sent to survnet, a list of items which had any other general exception which prevented the bulk action.

For > 40 entities:

  • the above mentioned modal window should appear also for archive/dearchive/sending to reporting tool if the communication is failing with Survnet

  • if for any other bulk actions (except for delete) can happen that the items are ineligible, should be handled with a similar modal window with a proper message (the messages from DeleteRestoreMessages can be used as reference )

  • if none of the entries are eligible, a message should be displayed ( in case of delete , there is already implemented)

  • If multiple problems can appear during a bulk action ( for example ineligible item and exception from Survnet) in the above given modal window should appear the list of ineligible items , a list of items which could not be sent to survnet, a list of items which had any other general exception which prevented the bulk action.

  • if the user does not have the proper right for performing an action ( ex: archiving) the warning message will not appear and the progress bar will remain blocked. This problem should also be solved. ( in the future those bulk actions for which the user does not have right, will not appear at all in the dropdown)

Bulk operations which should be covered in this ticket ( only the operations for which the Progress bar was already introduced):

  • Edit ( for all the entities with bulk edit in place)
  • Delete ( for all the entities with bulk delete in place)
  • Restore ( for all the entities with bulk restore in place)
  • Archive ( for all the entities with bulk archive in place)
  • Dearchive ( for all the entities with bulk dearchive in place)
  • Cancel follow-up for Cases
  • Cancel follow-up for Contacts
  • Cases Set to Lost to Follow-up
  • Contacts Set to Lost to Follow-up
  • Link contacts to event
  • Link events to event group
  • Send cases to External Surveillance Tool
  • Send events to External Surveillance Tool
  • Enable users
  • Disable users

Implementation Details

No response

Mockups

No response

Additional Information

Should be implemented after #11931.

Metadata

Metadata

Labels

backendAffects the web backendchangeA change of an existing feature (ticket type)generalNot directly concerned with any particular functional section of the applicationqa-verifiedIssue has been tested and verified by QAvaadin-appAffects the Vaadin application

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions