> Correct Usage of Secure Data ID's

  Websites which contain URL "modifiers" that preserve and enable
  the browser to maintain its current state is being used more and
  more in the creation of new websites for enhanced security
  purposes.

  Because each session modifier changes dynamically, a script
  recorded with an intital value would generate a different set of
  values on playback which would cause invalid sessions.

  By default, eValid automatically adapts to each session by
  replacing the first occurance of the Data IDs on the right-hand
  side of the URL in the script with the currently used and valid
  session ID.

  For servers that manage sessions that use two or more different
  sets of session IDs, or that use one session ID but place it
  somewhere other than in the first position, eValid needs to be
  told the names that need to be replaced.

  This is done through use of the SecureDataID command, which
  identifies and registers each unique DataID to allow eValid to
  track and make the appropriate modifications.  eValid only makes
  the modifications when it detect a change in the registered
  Data/Session ID's.

  A typical eValid sequence to accomplish this would be:

     ...
     EnterSecureZone
     SecureDataID $FIRST-NAME
     SecureDataID $SECOND-NAME
     SecureDataID $THIRD-NAME
     ...(eValid commands)...
     ExitSecureZone
     ...