| Type | Score | Description | |
|---|---|---|---|
| Knowledge characteristics | User set or System set | User set | Any value set in code becomes user set, and is not overwritten by the rule engine. |
| Parameters or complex model | Complex model | The custom service has the complete profile available as input. There can be well defined output variables as service parameters. | |
| Enhanced by Blueriq Functionality |  | There is a dependency to the custom service call and model validations on its parameters. There is no support on any business knowledge that is hard coded in the service. | |
Maintainability characteristics It should be possible to quickly make changes to business rules independent of other functionality. | Focus on Internal or External Use | Internal | The custom code is only called by Blueriq |
| Low Implementation complexity |  | You get a new service call which you can simply place in your flow. | |
| Internals invisible (encapsulation) | | Internals are not visible and/or accessible of a web service. | |
| Autonomous | | The business rules are executed in a separately, and no side-effects are possible. In code you could theoretically change all profile values, but we assume that only well defined output parameters are changed. | |
| Highly Testable | | Unit tests can be written in code. | |
| Highly Reusable | | As long as the custom code is available, using it is easy. | |
| Out of the Box | | No custom code required. | |
Deployment characteristics | Part of Application or Separate Deployment (=deployment) | Separate Deployment | The code has its own life-cycle and is deployed separately. |
Overview
Content Tools