1. Home
  2. Release Notes – SKYVVA Winter ’20 V 2.44
  3. 9. Patch V2.44.9
  4. 2. Bug Fixed

2. Bug Fixed

[add-search-inside]

Cannot handle long text error message in a message comment

Fixed missing failed message comments for monitoring while it has too long text.

The scheduler does not update status and comment on the screen while the scheduler aborted

There is an error that occurred while the user starts the scheduler in the Salesforce Classic interface, the scheduler has an aborted or unexpected error, and it will not update the status and comment correctly. This issue has been fixed.

The output result returns wrong to ISEMAIL formula function in the mapping tool

The mapping tool is able to use the formula function for adding or editing in mapping records. Fixed issue regarding output result returns wrong in the ISEMAIL formula. For example, the email does not have a domain “xxx.<domain>” like “xxx.skyvva.com”. When we write the mail like xxx@skyvva then it returns true, this is not correct. It should return ‘false’; therefore, the domain extension ‘.com’ is missing.

Cannot reprocess messages manually filtered by the interface name 

There is an error that appears while you want to reprocess the messages manually in the Message Monitoring. If the messages are filtered by an interface name, they are not able to reprocess. This issue has been fixed.

The DoMaintenance scheduler cannot delete the failed, pending, and new messages  

We have fixed the issue which DoMaintenance scheduler cannot delete the old failed, pending, and new messages. This issue occurs while reprocessing the message (MessageReprocessPerxxx), and the DoMaintenance scheduler are working at the same time. For example, the DoMaintenance set a day for the deletion. The scheduler will check the modification date for deletion. However, the message reprocessing (MessageReprocessPerxxx) scheduler tried to reprocess and updated the modification to the current date. Therefore, the deletion message function will be checked by the created date instead.

 

Fandest du diesen Artikel hilfreich? Ja Nein

Wie können wir helfen?