Conflict Handling - Example

In the following example, creating a record results in a conflict and the error messages are displayed in CRM.pad:

  1. A new order for a company is added containing two delivery dates on the same day.



  2. If a server connection exists, an error occurs:



    The application's server log file shows a Duplicate-Key-Error thrown by Aurea CRM's business logic.

  3. If no server connection exists, this error message is not displayed as CRM.pad does not check this occurrence. CRM.pad accepts this record in offline mode and the user can even add further order items. After entering the data, the record is probably displayed.



  4. When CRM.pad is online again, the Sync conflict(s) are shown in the application menu.



    The record created previously is not included in the order list anymore.

  5. If the user taps on the Sync conflict(s), the conflict's error message is displayed:



    In addition to the error message, also the info area, the action (e. g. new) and whether a dependent process (e. g. quick add for offer items) exists are displayed.

  6. The user can either click on Discard changes (the data will be removed) or click on the conflict to fix it (in the example by changing the second date and saving the record again). Child processes are also automatically executed (and hopefully do not return another conflict).