We can think of JavaScript running within a clients browser as a robotic agent. It has an environment in which it can sense things. The ability to look at the environment and make decisions based on plans.

So whys that useful, well why is a robot useful? You can produce many different complex plans and give them to the robot and forget about it while it does the work potentially over and over again. If we are really lucky the robot can demonstrate some intelligence and deal with uncertainty.

Well I tried out a small part of this idea to build a server side service which delivered plans in JavaScript to the client. The JavaScript planning agent followed the plans. Its not a intelligent robot but this is just a prototype. The plans where focused on validation conditions that a user needed to get through to post a form.

Example:

1
2
3
4

planCollection = Array();
planCollection[0][0]= Array();
planCollection[0][0]= document.forms['iwfmsForm'].elements['age'].value>18;
planCollection[0][1]= document.forms['iwfmsForm'].elements['ward'].value=='adult’;

Timings where implied by ordering of plans in an array. i.e. for plan 0 – value > 18 must happen before ward == adult.

Array dimensions imply different plans or forks in the plan.

Its a rather crude plan referencing form names and lots of low level javascript but it helps simplify the boring bits!

The Environment

The environment represents the different states the form elements and the user can be in.

The See process

This function maps the form elements to their associated values.

The Message Store

The message store is used to represent events generated by the user. Events could be the result of clicking on a form element or clicking away from a form element. Such events generate messages which the plan executor responds to. These events are the points where the planner is activated.

The Plans

The plans represent a sequence of constraints within the JavaScript syntax on form elements. This type of action is not executed but used to help decided upon which plan path to follow.

The Action process

This process deals with selecting actions based on the see process which provides information about the form element’s values. There may only be a single plan and thus no decision to make. If there are multiple plans the decision to follow an action is only made for the first action of a plan. Which initial action to decide upon is decided by testing each of the first actions of the plans until one holds from the information provided by the see process. This plan is then used to further test the next constraint of the plan and so on. If multiple first actions hold each of the plans is tested to see if any of them reach the goal.

The Goals

The goals of the plans can be regarded as ensuring that all the conditions in the plan hold based on the data in the HTML form.

The Execution of Actions

Within the planner the actions are not executed. Since we are constraining the user all we need to do is find a valid plan path. The planner affects the environment by alerting the user if it cannot find any valid plan path.

The plan executor needs to be able to handle two different situations:

• Form submission When the user inputs information into a form and then submits the form the planner will have to ensure that a valid plan path is reflected by the values that are held in the form. The form submission should be prevented if such a plan cannot be found.

• Real time user input

  • 1. Guidance through a plan As the user inputs information the planner needs to be aware of the current position in multiple plans and what effect this has on the current form element being filled in. Alerting the user if they have failed to achieve any plan as a result of the data they entered into the form.

    2. 1. Temporal ordering restrictions The planner needs to be able to handle temporal restrictions on the form elements. Indicating in which order form elements have to be completed. Therefore we have to look at the impact that a real time input action will have on the rest of the form. For example one form element being completed may have the effect that another disabled form element can be activated for input.

JavaScript Planning agent Code

https://github.com/josephwilk/iwfms/blob/master/javaScript/javaScriptPlanner.js