A technical presentation on how to use the Process Automation tools in iMIS RiSE to build engaging alerts and efficient automated tasks. Slides by Molly Verduzco, presentation by myself and Sarah Hoddinott.
3. Alert Usages - Public
Personalize website experience and engage
members and donors
• Reminder about upcoming events, due dates, etc.
• Personalized call to action
• Suggestions about possible areas of interest based on
user’s data
4. Alert Usages - Staff
Notify and highlight important information
• Important information when viewing a specific contact
• Notification about something that requires attention
• Highlight recent system events
5. Alert Definition
• Created using an automated task
• Uses IQA query as a driver
• Added to an Alert Set
• Displayed using an iPart
6. Anatomy of an Alert
Alert Display iPart
Alert Set
Automated Task
IQA Query
Add to content Apply CSS styles
Group alerts Set order
Hide from unauthorized users
IQA data sourceHTML
When does alert appear
What data is included in alert text
Does it pertain to selected contact
Who is authorized to see it
Personalized version
7. IQA Query
• Use to determine when to display alert
• Filter to selected contact if necessary
• Include columns to use in alert text
– Use an appropriate alias
– Include keys or IDs to construct URLs
– Display conditional text
10. • Send communications on a scheduled basis
– Confirmations or additional order information
– Reminders
– Renewal notices
– Invoices/reminders of outstanding balance
– Communication with attached dynamic report
Scheduled Task Usages
11. • Run static reports and send via email
• Run stored procedures
• iMIS 200: Issue gift receipts automatically
– Based on receipting preference, schedule
monthly, quarterly or yearly
Scheduled Task Usages
12. • Trigger: When the task should run
• Conditions: Restrict the task to run only
under certain conditions, defined using
IQA
• Actions: What the task will do
Scheduled Task Definition
13. • Triggered on a schedule
– One time, daily, weekly, monthly
• Future: When a system event occurs
– Item purchased, gift received, event
registration, membership join, etc
• Future: When data changes
– Data is created, updated, or deleted
– Property changes to a specified value
Task Triggers
14. • Add one or more IQA queries as data
sources
• If any of the queries returns results, the task
actions will be performed
Task Conditions
15. • Send a communication
• Run a report
• Run a stored procedure
• Issue gift receipts (iMIS 20-200 only)
Task Actions
16. • Scheduled: New member welcome
email
• Run a report: Recurring donation
enrollments
Examples