Managing Payments in Dashboards and Automated Workflows

Several improvements have been made to better support online payments in the dashboard and automated workflows. The following describes how to implement this, using a combination of new and existing tools:

New Motion 2 Trigger: Create Campaign

Select a Site Channel, Campaign Category, and Content Folder. Create a Campaign Name Template, and choose the Campaign Owner role. Choose a goal type, and amount, and set a max amount if desired. Select Add to Cart, if you would like the total goal amount to be added to the cart of the person completing the task. If adding to the cart, This task should be used in conjunction with the redirect trigger in order to redirect to the checkout page in the dashboard.

New Spark Triggers

Two new Spark Triggers, Contribution Campaign Goal Reached (Active Recurring Donor), and Contribution Campaign Goal Reached (Campaign) have been added so that actions related to a campaign and its donors can be taken when a goal is reached. For example, you may want to cancel recurring gifts and notify donors when a campaign goal has been reached.

Financial Section in the Engagement Detail Module

The Financial section in the Engagement Detail Module displays the Total Due, Amount Paid, and Amount Remaining, as well as a link to Make a Payment. After clicking the link, a cost breakdown will appear, and the user will be able to choose an amount. Upon clicking submit, they will be redirected to the checkout component published in the dashboard. For more information, please reference the section below on payments in the dashboard/Motion 2 automated workflows.

Checkout Component

The checkout component can be published in the dashboard, allowing payments to be made without leaving the dashboard. A checkout thank you page with static content should also be configured in the dashboard.

Content Grid Module

This module can be configured to display campaigns that the primary role (i.e. Team Leader) owns and allows them to view the campaign on the public website. When used in combination with the Motion 2 trigger that creates a new campaign, this allows a primary role to see campaigns that correspond to their trips or events. To do this, configured a hidden filter so that the owner ID equals the logged-in person. Next, configure columns for the content item name, and owner name. Finally, configure an action to Redirect with Parameters, title the action as View Page, choose the page on the site where the page can be viewed, and Pass the Alias. We also suggest adding static content above the module that explains that they can click the Actions button and select “View Page”.

Historic Transaction Grid

This module can be used to display payments made to a giving campaign related to a trip. When configuring this module, add a hidden filter for the accounting code (the accounting code should be configured as default content on the Site Planner campaign folder in Site Planner that will also be used in the Create Campaign Motion 2 Trigger). If this instance of the module will be displayed for the primary role, add an additional hidden filter so that the receiving person ID equals the logged-in person. 

Trip Balances Report

Our reporting tool can be used to configure reports that show trip balances. This report can then be published for the primary role and/or administrators. Please note that reports are only available for clients on Linux servers running MariaDB 10.3.x or higher. The reports must also be configured directly by WMTEK, so a small additional cost is required to implement this report.