Working With Custom Queries

Virtual Ticket provides users with possibility to create extensive search routines called "Finds" to find and retrieve virtually any information stored in the database. However, the working scope of each Find is limited by the set of fields defined for the folder/document type on which the Find is based. Moreover, the form that the Find utilizes when retrieving information from the database might narrow this scope even further.

Consider the following example. One of the employees from the production department of your company might be responsible for ordering ink supplies needed for all open jobs. The information on ordered ink for a job is stored in the Preflight Analysis document attached to the job. Using Finds, the user can get a list of all open jobs and a list of all Preflight Analysis documents where the Ink Ordered status is not specified.

Virtual Ticket provides the ability to use Custom Queries to extend the standard searching and reporting capabilities of the system. Using a Custom Query in the above example, it is possible to create a search for all open jobs (instances of the Jobs folder type) whose attached Preflight Analysis documents (instances of the Preflight Analysis document type) have empty Ink Ordered fields.

Generally speaking, creating a Custom Query is a matter of defining the underlying SQL query on the administrative level and making the query available to the end users of Virtual Ticket.

::Related Topics
:: Virtual Ticket Administrator User Guide