Building Apps that use the Decision Tree Editor
If the app you are building generates or imports FSML decision trees, you can make it possible for your users to be able to edit the trees as attachments.
To integrate this functionality, three attachments are required:
- The FSML decision tree itself, tagged as decision-tree. PMML decision trees are not currently supported by Xpress Insight.
- An input data file in CSV or ZIP format tagged as decision-tree-data. Note that Xpress Insight has an upper size limit of 150MB for all attachments.
- A JSON configuration file that is either tagged as decision-tree-cfg or has the same name as the decision tree itself (preferred).
This file provides important metadata to the decision tree editor. An example:
{ "decisionKeys": [ { "name":"DK1", "displayName":"Decision Key 1", "type": "real" }, { "name":"DK2", "displayName":"Decision Key 2", "type": "string", "constraints": ["category1", "category2"] } ], "treatments": [ { "actionId": "1234", "name":"T1", "displayName":"Treatment 1", "type": "string" } ], "profileVariables": [ { "name":"PV1", "displayName": "Profile Variable 1", "type":"counts" }, { "name":"PV2", "displayName": "Profile Variable 2", "profileType":"categorical", "categories": ["category1", "category2"] } ], "sampleWeight": "mySampleWeightVar" }This file identifies:- Deciision keys
- Treatments
- Profile variables
- Sample weight - the name of a column to be interpreted as a sample weight for each row.
See the Xpress Insight Web Client Users Guide for a detailed overview of the facilities provided for end-user decision tree editing.