Triggers to Be Migrated

If you see the checklist item "Migrate triggers to rules" on your Cycle Prep status page, this article is for you! The information in this article will help you migrate any remaining custom SQL triggers to newer Slate functionality. Refer to the documentation linked below for descriptions of these triggers and instructions on how to migrate them.

Applications

Group / Page Keys

Create Group/Page keys in Application Logic to replace application.QueryConfig

  • The application.QueryConfig trigger runs when an applicant views application pages or the status page.
  • It allows additional data to be included on a page for use in conditional logic or to display.

Submission Requirements (Hard & Soft Fails)

Create hard and/or soft fails in Application Logic to replace application.QueryIncomplete

  • The application.QueryIncomplete trigger runs when an applicant navigates to the Review page within a Slate-hosted application.
  • It alerts the applicant to data points that are required for application submission that were omitted (hard fails).
  • It also alerts the applicant to recommended data points that were omitted (soft fails).

If any of the above apply to your Slate database, it has custom SQL triggers that can be replaced with Application Logic.

Refer to the Slate Knowledge Base for detailed instructions on creating: hard and soft fails and group and page keys.

Custom School-Scoped Materials and Checklist Items

Create custom school-scoped checklist processes to replace application.UpdateBatch

  • The application.UpdateBatch trigger runs when an application record is updated.

Create custom school-scoped checklist processes to replace application.UpdateDefer

  • The application.UpdateDefer trigger runs when an application record is updated.

If one of the above items apply to your Slate database, it is using a custom SQL trigger to determine whether and/or how school-scoped items appear on application checklists. This custom SQL trigger can be replaced with newer Slate functionality.

Refer to the School-Scoped Checklists and School-Scoped Materials documentation for detailed instructions on customizing school-scoped checklist items.

Query

Merge Query

Create a Merge query to replace application.QueryMerge

  • The application.QueryMerge trigger runs when an application is opened in the Reader.
  • It generates merge fields for the Reader that are not already available by default or need additional formatting.

MergePublic Query

The application.QueryMergePublic trigger runs when a decision letter is viewed.

  • The application.QueryMergePublic trigger runs when a decision letter is viewed.
  • It generates merge fields for the decision letter that are not already available by default or those that need additional formatting.

If any of the above items apply to your Slate database, it has custom SQL triggers that can be replaced with queries.

Refer to the Slate Knowledge Base for detailed instructions on creating Merge queries and MergePublic queries.

Rules

Application Rules

Create rules to replace application.UpdateBatch

  • The application.UpdateBatch trigger runs when an application record is updated.

Create rules to replace application.UpdateDefer

  • The application.UpdateDefer trigger runs when an application record is updated.

Create rules to replace application.UpdateSubmitted

  • The application.UpdateSubmitted trigger runs only at the time of application submission.

If any of the above items apply to your Slate database, it uses custom SQL triggers that can be replaced with rules.

Refer to Slate Knowledge Base for documentation and instructions on rules and automations.

Application Checklist Rules

Create rules to replace application.UpdateChecklist

  • The application.UpdateChecklist trigger runs when an application record is updated.
  • It is used to create checklist groups.

If the above applies to your Slate database, you can create checklist rules rules to replace the trigger.

Refer to the Checklists and Rules and Automations documentation in the Slate Knowledge Base for instructions on creating checklist rules.

Person Rules

Create rules to replace person.UpdateDefer

  • The person.UpdateDefer trigger runs when a person record is updated.

If the above applies to your Slate database, it's using a custom SQL trigger that can be replaced with rules.

Refer to Slate Knowledge Base for documentation and instructions on rules and automations.

Test Optional Rules

Create Test Optional rules to replace application.UpdateBatch

  • The application.UpdateBatch trigger runs when an application record is updated.

Create Test Optional rules to replace application.UpdateDefer

  • The application.UpdateDefer trigger runs when an application record is updated.

Create Test Optional rules to replace person.UpdateDefer

  • The person.UpdateDefer trigger runs when a person record is updated.

If one of the above items apply your Slate database, it's using a custom SQL trigger to determine which person records have the Test Optional flag. The custom SQL trigger can be replaced with rules.

Create a prospects Test Optional rule type to set the Test Optional Flag for specific tests for specific people. The Test Optional Flag will hide the test score on the Profile >> Scores tab, and the auto-generated checklist item for that test type will be suppressed. Refer to Slate Knowledge Base for documentation and instructions on rules and automations.

Dataset Rules

Create rules to replace dataset.row.Update

  • The dataset.row.Update trigger runs when a dataset record (e.g., organization, organization contact, etc.) is updated.
  • It can perform actions such as:
    • Add additional information to be searchable when searching for an organization record
    • Specify information displayed when an organization record is searched for
    • Hide dataset records from public autosuggest
    • Set dataset record status to inactive or active
    • Set dataset usernames and PINs. 

If the above applies to your Slate database, it's using a custom SQL trigger that can be replaced with rules.

Refer to the Creating Custom Datasets and Rule Formulas documentation for instructions on creating dataset rules that set values using a formula. 

Was this article helpful?
0 out of 0 found this helpful