VSys Live Application Diagnostics - VOXI Trace Monitor
VSys Live logs a tremendous amount of data with each and every request submitted to it; these can be viewed using the VOXI trace monitor. To understand issues associated with submitting applications online, we're going to use in a specific way:
Enter an appropriate date/time range.
For Command filter, put in "app.postdata" (without the quotation marks).
Under Text search,
If this is an application for a new person, put in the applicant's e-mail address.
If it's for an existing person who's logged into VSys Live, get the person's unique ID code by going into their profile in VSys One, right-clicking on the five digit code in the upper-right corner, and select Copy full ID code to clipboard. Then paste that 16 digit value into Text search. (The reason we have to do this is that a new person's application will always have their e-mail address in it, where an existing person usually will not. That 16 digit code uniquely identifies a person and lets us find their logs quickly and easily.)
Click Get records.
What you'll get on the right is a list of every time this person submitted (or tried to submit) an application during this time period.
This isn't meant to be a user-friendly tool: it goes deep into the heart of how VSys Live processes information. The logs here are primarily intended for our support team.
Click on any event to bring up the detailed request and response.
You should probably select Exclude META tags. <META> tags are basically VSys Live talking while it works: it shows many decisions made and why along with certain timing information. You're not likely to find these useful.
At the top is the submitted data. This is not exactly what was sent by the browser: the browser first sends it to the VSys Live Rails application code, which applies certain diagnostics before then sending it along to VSys Live.
At the bottom is the raw response. In this case near the top we can see errors that were returned to the applicant based on the data submitted. If we scroll down through that we'd see a section called <ERRORFIELDS> which lists every field that had an issue.
From these you can probably deduce what the applicant submitted and what - if anything - was missing or incorrect in their application.
