The Intelligence System has a point-and-click visual design with an optional
grid display. There is an option to create a flowchart web page that renders perfectly
and can be printed to paper and or an image from a web browser. All buttons are designed
to be pixel-perfect and can be rendered in black, red, green, or blue.
The Intelligence System goes above-and-beyond flowcharts in the creation of
complex systems. Flowcharts in The Intelligence System can optionally have WinForm- and Linq-capable C# or VB.Net scripts
applied to them. Live flowcharting is one of the fastest ways to prototype and create
proof-of-concept applications, and scripted flowcharting makes diagnostic systems (even multi-threaded
diagnostic systems) easy to make.
The scripting engine built into The Intelligence System can interpret C# and VB.Net. Scripts can be
ran in threads or modal form. There are no parameters in Intelligence System scripts; instead, values
(even code) can be injected directly into code at any location.
The Intelligence System comes with a button pad for easy numbered responses (e.g., press 1 for...).
Breadcrumbs provide an action record that can be traced and recalled with the click of a button.
With Voice Recognition, the Intelligence System is capable of interpreting voice communications using the
device microphone. With Voice Synthesis, Agents created with The Intelligence System can speak in Male and Female
voices. When voice recognition and voice synthesis are combined, fully conversive agents can be created.
Note: Voice features in The Intelligence System are based on the Dragon
Assistant (that comes with Windows). Dragon Assistant will have to be trained before
the system will recognize commands with a high level of accuracy.
System keys can house information and be accessed everywhere in the system. File contents, Session
information, Scripting parameters, and more can be maintained from node to node. System keys are what
allow immersive agents to be created.
System commands allow agents to open files (i.e., pictures, videos, or documents related to
the current activity), run programs, open websites, and-or perform file system operations. System commands can include
Intelligence System keys to add dynamic components and make advanced batch components.
An edit mode password that disallows the editting of agents can be added to agents of the Intelligence System.
The edit password makes it possible to securely share agents with knowledge they will retain their original form.
Edit passwords can be easily removed and added.
Agents created with the Intelligence System can run actions on timed intervals. Timer actions activate nodes and
are therefore able to access all abilities within the system. Because the Intelligence System is threaded, Timer
Actions can even spawn sub-systems. In addition to Timer Actions, the Intelligence System has timeout functions
that will activate if-when a response is not entered in a given interval.
Wildcards allow dynamic response recognition. When the user responds to the agent in the Interaction window, the
response can be processed with a wildcard script (written in C# or VB.Net) that then returns a true or false answer
that indicates whether or not to activate a given response action. Wildcard classes can be applied to the entire response
or one word within the response. In addition to wildcard classes, the Intelligence System accepts asteriks as
all-inclusive word wildcards.
Neural Networks can be created and trained in the designer and accessed at agent runtime.
With UDP socket capabilities, the Intelligence System is fully networkable. In the Intelligence System, a listener is
created to listen to a certain location, and messages received are saved to the designated System Key. System Keys can
be accessed anywhere in the system, and it is especially helpful to combine UDP Socket abilities with Event Handlers.
With the UDP Socket engine, machines in other locations can communicate and encourage interoperability.
Event Handlers are akin to 'when' statements (i.e., when 'this' is true, do 'that'). The Intelligence System binds event
handlers to system keys, so activating an action is as easy as adding the event handler and changing the system key to
the value of the event handler. Event handlers are multi-threaded, so the current process flow continues uninterrupted.
Condition casing is a form of positive filtration. An example of positive filtration would be to find all positive prime
numbers less than 50, or find all building elements that are more than $20 and composed of both wood and fiberglass.
Condition cases use a built-in checkbox dialog and save results to system keys for access further in the system.
Threading and concurrency are built into The Intelligence System, and starting a thread is as easy as creating and
activating a node. Threaded operations can be run in tandem, often in the background to the primary thread. Threaded
applications can be developed quickly with the mapping capabilities of the visual Intelligence System design.
An activity log that records every action of an agent is built into The Intelligence System. The activity log will
save actions to a developer-designated text file. Having a trace of activities is useful in debugging and handy for
security purposes. Activity logs can be activated or deactivated at any time during agent processing.
In addition to activity logs, an interaction log that records every interaction of an agent with a user is built into the Intelligence System.
The interaction log will save communications to a developer-designated text file. Have a trace of interactions is
useful in debugging and assists with recordkeeping. Activity logs can be activated or deactivated at any time during
Agents created with the Intelligence System can be bound into a royalty-free redistributable that can be given to friends
or co-workers. Redistributable packages can even be sold at no additional cost. Once bound, an agent cannot be editted in
the designer, so your code remains safe.