Programming model
This topic was viewed 5 times since its publication
Sharing of the model was deemed critical for not only ease of future maintenance, but for a consistent programming model for the end user. Sharing this model required compromises between the needs of desktop tools and runtime execution and authoring -- all have clear sets of requirements to meet for their respective environments and these requirements at times conflicted with each other. The artifacts described as part of the overall programming model represent a balance in meeting the requirements of these different environments.
Modification of business rules is limited to only those items that are defined with templates in the rule sets and decision tables as well as the operation selection table (effective dates and targets). Creation of new rule sets and decision tables is only supported through the copy of an existing rule set or decision table. The business rule group component itself is not eligible for dynamic authoring in the runtime with the exception of the user defined properties and description values. Changes that need to be made to the component (for example, adding a new operation) must be done using IBM Integration Designer and then redeployed or reinstalled in the server.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-01-20 10:38