With the provided interim fix IF009 everything works fine. Thank you!
Original Message:
Sent: Wed May 08, 2024 09:58 AM
From: Alain Robert
Subject: ODM Rule Designer 8.12.0.1: Handling exceptions in BOM to XOM Mapping
This is indeed a new issue with the product it is registered as DT381870 .
Thanks for your report.
You can use the link above to track when a fix becomes available.
------------------------------
Alain Robert
Original Message:
Sent: Tue May 07, 2024 03:20 AM
From: Stephanie Heßler
Subject: ODM Rule Designer 8.12.0.1: Handling exceptions in BOM to XOM Mapping
Hi Alain,
we have tried to narrow down the problem by creating a mini RuleApp.
The RuleApp deployment fails with the following message:
I've added an excerpt from the eclipse .log file.
The BOM to XOM Mapping is:
try { return 3;} catch (java.lang.NumberFormatException e) { return 4;}
The deployment works fine if the BOM to XOM mapping is simply "return 3;"
------------------------------
Stephanie Heßler
Original Message:
Sent: Fri May 03, 2024 05:42 PM
From: Alain Robert
Subject: ODM Rule Designer 8.12.0.1: Handling exceptions in BOM to XOM Mapping
try/catch blocks in B2X mapping are good practice, it should not be causing issues.
What error message do you receive?
------------------------------
Alain Robert
Original Message:
Sent: Fri May 03, 2024 09:11 AM
From: Stephanie Heßler
Subject: ODM Rule Designer 8.12.0.1: Handling exceptions in BOM to XOM Mapping
Some of our existing BOM to XOM Mappings contain try-catch-statements. That wasn't a problem in the past with Rule Designer 8.10.5 and 8.11.1. When trying to export and deploy the ruleapp with Rule Designer 8.12.0.1 however the export fails.
Did we miss any migration steps?
------------------------------
Stephanie Heßler
------------------------------