Skip to main content
Share / Export

Configuring WF Notifier Queries

WF Notifier Queries creates and maintains SQL queries used by Notifier jobs in WF Notifier Job Manager. Queries run against the Vista SQL Server. Form help sits under About Automated Notifications → WF Notifier Queries. Procedure: Creating Notifier Queries. There is no help slug configuring-wf-notifier-queries. Help is a basic overview, not SQL training. If you cannot write SQL, use a standard query (Viewpoint Standard checked).

Before you start​

  • SQL skill, or a shipped standard query / copy / VA Inquiry.
  • Jobs are configured later in WF Notifier Job Manager.
  • Event-driven queries need key fields (below).
  • Datatype security changes what you may query (tables only when security is on).

Steps​

  1. Open WF Notifier Queries.
  2. Create from scratch, or use/copy a standard Notifier query, or use/copy/create a VA Inquiry.
  3. Query Name (unique; selected on Job Manager Info tab Query; F4 lists existing).
  4. Title (up to 255).
  5. Check Event Query if event-driven.
  6. Description (up to 255): what the query returns.
  7. Select Clause (up to 8,000): SELECT list. Format Query adds brackets for email fields. Aliases in brackets become email fields (example Select Name as [Name], Address as [Address], Zip as [Zip]).
  8. From Where Clause (up to 8,000): FROM and WHERE. Options → Viewpoint Views opens WF Notifier Viewpoint Tables. Example in field defs: FROM HQCO WHERE HQCo > @company.
  9. Test Query (error check).
  10. Add local variables (@company, etc.) on Query Parameters (Parameter + Description up to 255). Values are set later on the Job Manager Parameters tab. Procedure adds parameters before save; field defs say create the Query Parameters entry after save — do both: save, then confirm parameters exist in SQL and on the tab.
  11. Save. Email Fields then lists bracketed Select aliases. Edit only the bracketed text in Select Clause, then save to refresh.
  12. If event-driven, check Is Key Field on Email Fields for each key field.
  13. Associate the query with a job in WF Notifier Job Manager.

Hard rules​

  • Queries run as an admin account with access to all Viewpoint data, so they can return data the recipient cannot see under datatype security. Limit To/CC/BCC to people allowed to see that data (Restricting Notifier Queries).
  • If datatype security is on, views are not allowed; tables only.
  • A parameter must exist both in SQL and on Query Parameters or Job Manager will not recognize it.
  • Event-driven: first run records every match and does not mean “new event.” Later runs notify only when key fields change or a new key combination meets the rule. Same keys still meeting criteria = no repeat email.
  • VA Inquiries has no Event Query box. Key fields on its Notifier Email Fields tab mean the system treats it as event-driven. To event-drive a standard query: VA Inquiries → File → Copy Query, point the job at the copy, then edit the copy.
  • Before a real event-driven job, test-run to one account as a consolidated notification, or the first compare sends many emails.
  • Several jobs can share one query if restrictions differ; parameters are placeholders filled per job.

Notes​

  • Related: Creating Notifier Queries; About Event-Driven Queries; Restricting Notifier Queries; WF Notifier Job Manager; WF Notifier Viewpoint Tables; VA Inquiries; WF Notifier Options; Table Layout; Email Parameters.
  • Field-def typos include “even-driven” and “FROMWHERE Clause.” Restricting may say “Param field” for Parameter.