Background Queries

You can execute complex queries in the background and continue working on Aurea CRM.

By clicking users can execute queries asynchronously in the background in addition to executing queries immediately via . When running a query in the background, the user can continue to work in Aurea CRM.Web. The query is executed on the server. When finished the user gets a notification that he can now access the query snapshot.

Note: Executing queries in the background is recommended for long-running complex queries.

To enable the processing of background queries, CRM.server must be up and running on the server. For further details, see CRM.Server.

The rep ID of the CRM.server user must be specified in the UpdateServer.RepID Web Configuration parameter because the to-dos for background processing are created for that rep. For further details, see UpdateServer.RepID.

The Web Configuration parameter Jobs.PollingInterval defines the time interval in which the existence of new query snapshots is periodically checked. For further details, see Jobs.PollingInterval.

The Web Configuration parameter Query.BackgroundExecutionStart allows you to specify a time in the format hh:mm for asynchronous queries to be processed on the server. For further details, see Query.BackgroundExecutionStart. That way the processing of background queries can be scheduled for off-peak hours in case performance issues arise.

CRM.server is notified about new background queries via To-Do records that are automatically created by Aurea CRM.Web. The query is saved as a D1 document (*.xml) linked to the to-do record. CRM.server processes the query with the rights of the rep that has sent the query and then saves the result in a query snapshot, and finally creates a Message record for the user. The message contains a link to the To-Do which now has the status "completed". The to-do contains a link to the query snapshot. The XML document is automatically deleted after completion.

Users can access the to-dos created for background queries via Queries & Analyses > Background Queries. For further details, see ID_NET_TD_BACKGROUND_QUERIES.

In UPDATE_DEFAULT the special headers Query and QueryFooter contain the button.

If you add the button to those headers, users can create a CSV file containing the query results. The file is stored in the Document info area (D1) and linked to the Message via a D3-link.

Note: With Create CSV File in Background the resulting records are not stored as a query snapshot but in the CSV file only.

Note: If the created CSV file exceeds a certain size, the decompression of the file (when transferring it from the database to the client) is not performed in memory but via the file system.

For information on the background query buttons and their configuration. For further details, seeQuery Background Processing Buttons.