You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When a single open transaction in the TSE should be closed then the "Failed-Transaction-Receipt" can be used. In such cases the cbReceiptReference has to be set or the following exception is thrown: CbReceiptReference must be set for one transaction! If you want to close multiple transactions, pass an array value for 'CurrentStartedTransactionNumbers' via ftReceiptCaseData
Issue:
As this exception is only relevant for the "Fail-transaction-Receipt" it should only be thrown in the described case. But currently the middleware throws this exception even when the "Fail-transaction-receipt" isn't used. Example receipt request:
This is a regular receiptRequest with a "Failed receipt" flag and therefore shouldn't result in this exception. Possible cause: The condition that checks if the receipt is a "Fail-transaction-receipt" is negated and that might result in all receipts being checked except the relevant "Fail-transaction-receipt" if (string.IsNullOrEmpty(request.cbReceiptReference) && !request.IsFailTransactionReceipt() && !string.IsNullOrEmpty(request.ftReceiptCaseData) && !request.ftReceiptCaseData.Contains("CurrentStartedTransactionNumbers"))
saschaknapp
changed the title
DE: cbReceiptReference exception thrown for wrong receipt
DE: cbReceiptReference exception thrown for wrong receiptCase
Jul 24, 2023
Description:
When a single open transaction in the TSE should be closed then the "Failed-Transaction-Receipt" can be used. In such cases the cbReceiptReference has to be set or the following exception is thrown:
CbReceiptReference must be set for one transaction! If you want to close multiple transactions, pass an array value for 'CurrentStartedTransactionNumbers' via ftReceiptCaseData
Issue:
As this exception is only relevant for the "Fail-transaction-Receipt" it should only be thrown in the described case. But currently the middleware throws this exception even when the "Fail-transaction-receipt" isn't used. Example receipt request:
This is a regular receiptRequest with a "Failed receipt" flag and therefore shouldn't result in this exception. Possible cause: The condition that checks if the receipt is a "Fail-transaction-receipt" is negated and that might result in all receipts being checked except the relevant "Fail-transaction-receipt"
if (string.IsNullOrEmpty(request.cbReceiptReference) && !request.IsFailTransactionReceipt() && !string.IsNullOrEmpty(request.ftReceiptCaseData) && !request.ftReceiptCaseData.Contains("CurrentStartedTransactionNumbers"))
middleware/queue/src/fiskaltrust.Middleware.Localization.QueueDE/SignProcessorDE.cs
Line 41 in b3849f7
The text was updated successfully, but these errors were encountered: