User interface for developers
After completing the installation on their workstation, a developer is able to drag the Decision Service Node from the node palette and use it like any of the other nodes.

The Basic section has the following node properties:
- Ruleset Path – Defines the canonical rule path of an rule set application.
- The type is String.
- This property is not required.
- Alternative, the node can use the Local Environment. The Local Environment overwrites the setting of the node.
-
Ruleset parameter – Properties need by the node to fill the ruleset parameter.
- The type is table property with a string as parameter name and data location.
- This property is not required.
- The node uses the getFirstElementByPath() integration bus function to find the input value with the specified data location.
- Alternative, the node uses the local environment. The local environment overwrites the setting of the node.
To overwrite the properties use the following local environment structure:
LocalEnvironment.DecisionServiceParameter.RulesetPath = '/EmployeeApp/EmployeeRules';
LocalEnvironment.DecisionServiceParameter.RulesetParameter.Parameter[1].Name = 'message';
LocalEnvironment.DecisionServiceParameter.RulesetParameter.Parameter[1].DataLocation = '/XMLNSC/Employee_Info';
The section Decision Management System has the following node properties:
- Configurable Service
- The type is string.
- The default is DecisionService.
- This property is required.
- It specifies the user defined configurable service of the Decision Server Management Console.
-
Logging Level - Log Level for the node.
- The type is enum.
- The default is INFO.
- The logs get written in the system out file of the execution group.
- The level INFO provides information for the rule update events and the raised exceptions.
- Use all level below INFO for debugging purposes.