Thank you very much for your prompt response.
The message is directly related to the attribute, I can't see any error in the BOM to XOM code, in fact, I reduced the code just to return a simple string, and the problem persisted.
This is the reduced version of the BOM to XOM code:
<b2x:translation xmlns:b2x="http://schemas.ilog.com/JRules/1.3/Translation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.ilog.com/JRules/1.3/Translation ilog/rules/schemas/1_3/b2x.xsd">
<id>51d581b5-c40b-4b3c-a49f-5b254402623c</id>
<lang>ARL</lang>
<class>
<businessName>com.consupago.brms.originacion.xom.common.ReciboNomina</businessName>
<import>java.util.Iterator</import>
<import>com.consupago.brms.originacion.xom.common.CampoAdicional</import>
<attribute>
<name>clabe</name>
<getter language="arl"><![CDATA[
return "-";
]]></getter>
</attribute>
<attribute>
<name>tipoRegimen</name>
<getter language="arl"><![CDATA[
return "-";
]]></getter>
</attribute>
</class>
</b2x:translation>
In fact, both attributes "clabe" and "tipoRegimen" show the same problem.
This is the message (sorry for being in Spanish)
[B2X] GBREX0021E: No se puede encontrar el atributo 'tipoRegimen' en la clase de ejecución '........TheClaasss' modelo.....Problema de BOM a XOM de Rule Designer
[B2X] GBREX0021E: Unable to fnd the attribute 'tipoRegimen' in the execution class '........TheClaasss' model.....Problema de BOM a XOM de Rule Designer
All documentation talks about using the BOM to XOM box and no additional configuration, as you also said, but not working.
This project was migrated from iLog 7.1.1, and we are working on ODM v8.10.5.
I'll keep trying.
Best regards!
#OperationalDecisionManager(ODM)#Support#SupportMigration