Learn about known issues and apply workarounds for Sybase® Money Mobiliser.
| Bugzilla # | Description |
|---|---|
4715 | Issue:
DB2::[Reports]::Error Message is displayed while generating
Transaction detail report. Workaround: None. |
4563 | Issue: Report
displays indicates previous Start Date and End Date after generating
the report.
This issue affects only the display. The data is accurate for the report. You can customize the report template, if desired. Workaround: None. |
4560 | Issue: Ignore these wallet errors when using the plain
vanilla portal. When registering a customer
using the plain vanilla portal, these errors occur when adding
payment
instruments:
2012-09-21 14:51:07,249 [jetty-50] DEBUG com.sybase365.mobiliser.framework.service.response.ResponseCodeAdvice S:() - Endpoint: [WalletEndpoint] threw an exception, attempting to convert to status value for response type [FindPendingWalletEntriesResponse] com.sybase365.mobiliser.money.businesslogic.util.IllegalDataException: No dual approval configuration found for pi type #20 at com.sybase365.mobiliser.money.services.wallet.WalletEndpoint.findPendingWalletEntries (WalletEndpoint.java:798) 2012-09-21 14:51:07,189 [jetty-51] DEBUG com.sybase365.mobiliser.framework.service.response.ResponseCodeAdvice S:() - Endpoint: [WalletEndpoint] threw an exception, attempting to convert to status value for response type [FindPendingWalletEntriesResponse] com.sybase365.mobiliser.money.businesslogic.util.IllegalDataException: No dual approval configuration found for pi type #40 at com.sybase365.mobiliser.money.services.wallet.WalletEndpoint.findPendingWalletEntries (WalletEndpoint.java:798) Workaround: No action required. |
4540 | Issue: The portal does not prevent you from adding the same
day and time in a schedule multiple times for the same alert
blackout. Workaround: None. |