Query Output Options

In a query, after you select Run Query, you’ll find an Output setting that provides options in two categories:

• Export destinations: The various places in Slate to which you can send your query results and the formats in which you can export them.

• Batch management: These options let you use the query results to perform bulk operations on Slate data.

The options available under these categories depend on the base on which the query was built.

Export destinations

These output options allow you to format the data in different ways. Not all options are available to all query bases.

Excel spreadsheet

Download the results as an Excel XLSX file.

Deliver mailing

Copy the entire query into a mailing (for use as a live query) or copy the results into a mailing as a static recipient list. Only non-system mailings with a status of In Progress or Completed that are assigned to the user running the query are available as an export destination. Users can only add queries as recipient lists to new mailings or to mailings for which they are also the assigned user.

Portal

Add the query to an existing portal.

Report

Use the query as the basis for a Data/Charts part in a new report.

Concierge

Display the query results in a Concierge dashboard.

Comma-delimited CSV file

Download the results as a CSV (comma-separated values) file.

Tab-delimited file

Download query results as a tab-delimited .txt file.

PDF document export

Export PDF documents as a single file or within a ZIP archive. Only available to queries on the Application base.

Decision letter export to Word

Download a Word document containing all of the decision letters on all of the applications in the query results. Only available to queries on the Application base.

PDF report

Download a PDF file with the query results in a table layout.

HTML report

Display query results in an HTML table.

Mail merge Word document

Export the results to an uploaded Word document and either merge the data or set up the merge fields. Requires Windows.

Batch management

These output options let you use the query results to make updates to data in Slate. Only some query bases support batch management, and the options that appear depend on the query base:

Most batch management options update all records in the saved query run. Bin and Decision also provide Update Selected. Run the query again before you use batch management when you must update the current result set.

Activity

Select Activity to add an activity to all applications in the query results. This option requires the Application Update permission.

Configure the following settings:

• User: Select the user associated with the activity.

• Code and Subcode: Select the activity type.

• Date/Time and Subject: Enter the activity date, time, and subject.

• Private Comments and Public Comments: Enter comments and select whether to post the public comments to the online status page.

• Additional settings: Form and event registration codes provide instance and status settings. Payment codes provide payment type, amount, currency, and account settings.

📝 Note

If you submit this output again, Slate can add another activity to the same applications. Confirm that the activity does not already exist before you submit the update.

Assign

Select Assign to change the role or user assignment for all messages in an Inbox query. This option requires the Inbox permission.

• Role: Keep the current role or select an Inbox role.

• User: Keep the current user, clear the user, or select an eligible user. The selected role controls which users are available.

📝 Note

A role change can change which users can view and respond to the messages. Confirm the role membership before you submit the update.

Bin

Select Bin to perform bulk operations on the workflow bins associated with the records returned by the query.

Available controls:

• Workflow, when more than one workflow is applicable

• Leave Current, Set Bin, Clear Bin, Set Pending Bin, or Clear Pending Bin

• Add Readers, Clear Readers, or Clear Specific Readers

• Add Reader and Remove Reader

• Update Selected or Update All

Requirements:

• Read access to the query

• Bin Management

• The applicable workflow permission and realm access for workflow-specific queries

🔔 Important!

Clearing a bin or its readers can remove records from an active review queue. Export the existing bin and reader assignments before you make a large update.

Checklist

Select Checklist to update checklist items for all applications in the saved query run. This option requires the Application Update permission.

Select a checklist item or select Form and then select a form. Select one of the following actions:

• Add New

• Add New + Mark as Received

• Add New + Mark as Waived

• Mark Existing as Received

• Mark Existing as Waived

• Remove Existing

Checklist does not provide Update Selected. It updates all applications in the saved query run.

Decision

Select Decision to add, clear, or confirm decisions for selected applications or all applications in the query results. This option requires the Application Decide permission.

Configure the following settings:

• Code: Select a decision code or select Clear Decision.

• Reason: Select a reason when the decision code uses decision reasons.

• Letter: Use the default letter for the decision or select another available letter.

• Status: Select Confirm decisions immediately upon updating to confirm the decisions.

Select Update Selected or Update All.

For a workflow-bin query, Slate updates the application associated with each workflow record. The user must also have the applicable workflow permission and realm access.

📝 Note

Clear Confirm decisions immediately upon updating when you add provisional decisions. Confirming a decision does not release the decision.

Field

Select Field to add, replace, or delete a field value for all records in query results.

1. Select a custom field to update.

2. Select an Action:

   • Add to Values: Available only for fields configured to store multiple values. Append the selected value to the existing field values. If a record does not yet have a value for the selected field, one will be added.

   • Replace Values: Replace existing field values with the new value selected. If a record does not yet have a value for the selected field, one will be added.

   • Delete Values: Remove values for the selected field for all records in the query results.

3. Select or enter the new field value.

4. Select Submit.

The available fields depend on the query. Application queries can include application-scoped and person-scoped fields. Dataset queries include fields for the selected dataset. Inbox queries include Inbox Message-scoped fields. This option requires the Person Update permission.

🔔 Important!

Replace Values and Delete Values remove existing data. Delete Values removes all values for the selected field. Export the current values before you submit the update.

Form/Event

Select Form/Event to update one property for all forms and events in the query results. This option requires the Events (edit all users) permission.

The available properties include:

• Folder, Description, Status, Title, Privacy, Archive, User, User 2, and Realm

• Deadline, Activation Date, and Duration

• Location name, street, city, region or state, and postal code

• Registrant Limit and Waitlist Limit

• Trip and Related Registration Check-In

Some properties apply only to specific resource types. A blank value clears the selected property when that property supports a blank value.

Select Submit, confirm the affected count, and type UPDATE [count].

Form/Event - Delete

Select Form/Event - Delete to delete all forms and events in the query results. This option requires the Events (edit all users) permission.

Select Delete Records, confirm the affected count, and type DELETE FORM.

🔔 Important!

This action deletes the forms and events. It does not archive them. Export the resource IDs and confirm the query results before you continue.

Generate PIN

Select Generate PIN to set a PIN for records that do not have a password or PIN. This option requires the Person Update permission.

• Slate does not replace an existing password or PIN.

• An Application query updates the associated person records.

• A Dataset query updates the dataset records.

• Slate does not send an automatic communication with the new PIN.

Select Submit to update all records in the saved query run.

Interaction

Select the Interaction destination to add an interaction code for all records in query results. Records Affected displays the number of records that will receive this new interaction code.

Person and Application queries require the Person Update permission. Dataset queries require the Dataset Update permission.

The query base affects how interactions can be configured and how they are applied:

• For an Application query, Slate adds the interaction to the person record associated with each application.

• Form and event registration codes provide instance and status settings.

• Payment codes provide payment settings.

📝 Note

If you submit this output again, Slate can add another interaction to the same records. Confirm that the interaction does not already exist before you submit the update.

Priority

Select Priority to replace the priority value for all applications in the saved query run. This option requires the Application Update permission.

Select a value from the Priority list and select Submit. Priority does not provide Update Selected.

📝 Note

This action replaces the existing priority on all affected applications. Export the current priority and use filters to limit the query results.

Retroactive Refresh

Select the Retroactive Refresh destination to simulate a record update. This is a helpful way to trigger rules or origin source calculations for records that have not been updated recently.

Records Affected displays the number of records that will be refreshed. For queries with an Application base, the associated Person record will also be updated:

Retroactive Refresh adds records to the deferred rule-processing queue. It does not run rules immediately. Form-submission rules and application-submission rules do not run from Retroactive Refresh. Application queries require the Application Update permission. Other queries require the Person Update permission.

📖 Retroactive Refresh

Round

Select Round to move all applications in the saved query run to another application round. This option requires the Application Update permission.

Select a value from the Round list and select Submit. Round does not provide Update Selected.

🔔 Important!

A round change can affect requirements, deadlines, rules, communications, and Reader configuration. Test the update and use filters to limit the query results.

Security

Select Security to update all users in a User query. This option requires the Security Administrator permission.

Select one of the following update types:

• Assign Role or Remove Role

• Add Explicit Permission or Remove Explicit Permission

• Update User Status

• Set User Expiration Date

• Set User Multi-Factor Authentication

Population-aware roles and permissions provide settings for one population or all populations. A blank expiration date clears the current expiration date. Slate enables MFA only for users who have a mobile phone number.

📝 Note

Removing an explicit permission does not remove the same permission when a user inherits it from a role.

Status

Select Status to update all messages in an Inbox query. This option requires the Inbox permission.

Select one of the following actions:

• Open or Resolve

• Delete Messages, which removes the messages from the active Inbox

• Restore Messages, which returns them to the Inbox

• Flag Messages as Junk or Unflag Messages as Junk

• Star Messages or Unstar Messages

Tag

Select the Tag destination to set or unset a tag for all records in query results.

1. Select a Tag.

2. Set or Unset the tag.

For an Application query, Tag updates the person records associated with the applications. It does not update application-scoped tags. For a Dataset query, it updates the dataset records. This option requires the Person Update permission.