Release 9.5

Release 9.0

Release 9.4

The following is a summary of the main changes in release 9.4 of Knowledge Builder:

Major New Features

1. Dialog object design-time inheritance
   • One-level parent/child inheritance for Dialog properties & controls
   • Option to setup a Master Dialog Template

2. New Text object type
3. New Form Rules for validating user input in Dialog objects
4. Validation Script for validating user input on Dialog input controls
5. Text objects inputMask (Web Deployments only)
6. Multi-instance Dialogs (JavaScript Web Deployment only)

Main Enhancements

1. Multi-select List objects now support allowBlank and isEmpty properties in the same way as single select List objects. Prior to this release, an "empty" Multi-select Listbox would allow the runtime user to leave the Dialog regardless of the allowBlank value. The isEmpty property would also be set to False after the object's capture even if it was "empty".
2. The new FinalURL property in the "Deploy Settings" for the whole Project overrides any FinalURL values set in individual Knowledge Modules.
3. New helpText object control property, for Web deployment, displays a question mark icon next to the input control which when clicked will display the text contained in the helpText property.
4. New default Knowledge Module Template
   • Uses a Startup Tab instead of the Main Agenda
   • Start object set to a default object Main_Flow
   • Using a Master Dialog and a Child dialog for each object type (List, Boolean, Numeric, Date and Text)

5. New option to set the width of columns in Grid controls as displayed at runtime (defaults to 80 pixels). This option can be set in the "Runtime Display" tab of each instance property.
6. Listbox and Grid controls options
   • For an object with multiSelect=False
     • ControlType=Standard, Hyperlink, Radio buttons and Checkboxes

• For an object with multiSelect=True
• ControlType=Standard and Checkboxes

7. Using a common Dialog object to capture different objects (one at a time as they are invoked by object inference)
   • Set the TiedDialog property for the different objects to the same Dialog object
   • Add a single input control (Listbox or Grid) to the Dialog object
     • Select the required ControlType value
     • Leave the TiedItem set to (none) to allow the input control to be dynamically tied to different objects at runtime.

• You can also embed an object control property in the caption of a Label control. This will be resolved to the property of the object being invoked.
• Using two underscore characters followed by the property name to signify this e.g. {__description} to display the "description" property