Donations - Vision2 Follow
Focus Missions integrates with Vision2 through a series of Apis creating a bi-directional sync with the thought that majority of the work would continue to happen in Focus Missions with that data being moved to Vision2.
To set up the integration between Focus Missions and Vision2, an organization user must be created inside Vision2 (this must be a new account, not an existing user). A great example is to make the NEW user with a First Name: Focus Missions Last Name: API User Email: focusmissions@[[yourdomain]]
This organization user will be inputted into Focus Missions so that Focus Missions can interact with Vision2 on behalf of the user.
1. Inside Vision2, select Administration
2. Click the + next to "Find" for Users.
Fill out the information necessary, selecting "OrganizationAdministrator and Finance" as the roles. Please be sure to remember the password as you will need that in Focus Missions when setting up the integration. It is also a good idea to try to login to V2 with this new user to verify the account set up.
Associate in Focus Missions
After the Organization User has been created in Vision2. It is time to connect that user to Focus Missions. Navigate to Focus Missions and then click on Admin > Settings. On the submenu from Settings, click on Software Integrations / Vision2
Make sure to have your password for the Organization User created in Vision2 handy in Focus Missions
To setup the integration in Focus Missions, there are three fields that are required.
1. Vision2 Organization Name: The subdomain that is used when interacting with your Vision2 instance.
2. Api User: The admin user that was created in Vision2 from above.
3. Api User Password: The admin user password that was created in Vision2 from above.
4. Click "Turn on Integration"
The integration between Focus Missions and Vision2 can be turned off at anytime by clicking the 'Turn Off Integration' button on the Vision2 Software Integration screen. This will suspend any activity and syncing between the two systems.
After successful setup, Focus Missions will create 2 volunteer roles in Vision2 that will be used when team members are added to a trip in Focus Missions.
1. Focus Missions Team Leader
2. Focus Missions Team Member
These two volunteer roles are used with creating volunteer participants in Vision2. It is highly recommended that those two roles are not deleted.
Data Subscriptions
Vision2 uses data subscriptions in order to inform Focus Missions of new / changed data so Focus Missions can update data elements of people and donations / payments.
It is important that data subscriptions are turned on in Vision2. Without them, any transaction made from Focus Missions through Vision2 will not be captured in Focus Missions.
In order to set up a data subscription in Vision2, navigate to the data subscriptions section inside Vision2.
1. Click on Administration
2. Click on Data Subscriptions
3. Click on Add a new Data Subscription
Payment Data Subscription
Create a data subscription for payments by filling out the necessary fields to inform payments to go to Focus Missions. Below is a chart to indicate the values to put in each field.
NOTE: For the Host Field, the "FocusMissionssubdomain" set that to the subdomain that you use to log into Focus Missions.
| Vision2 Field | Value To Fill |
|---|---|
| External System | FocusMissions |
| Subscription Type | Payment |
| Host | https://<FOCUSMISSIONSSUBDOMAIN>.focusmissions.com |
| Integration Target Type | Vision2 |
| Max Retries | 10 |
| Retry Interval | 5 |
| Authentication Type | Basic |
| User Name | Note: Same username that is used when setting up integration with Focus Missions. |
| Password / Confirm Password | Note: Same password created with user that was created when setting up integration with Focus Missions |
| Comments | Focus Missions Payment Data Subscription |
After setting up the basic information, next select the Push Change Actions. Focus Missions understands the action of adding a record and updating a record. Click the update for "Add Record" and "Update Record"
| Add a Record | |
| Resource | /ajax/vision2/subscriptions/payment/create |
| Method | POST |
| IncludeDeceased | unchecked |
| Update a Record | |
| Resource | /ajax/vision2/subscriptions/payment/update |
| Method | POST |
| IncludeDeceased | unchecked |
After setting up the resources click "Save & I'm Done"
Individual Profile
Create a data subscription for individual profile by filling out the necessary fields to inform Focus Missions of changes on individual profiles within Vision2. Below is a chart to indicate the values to put in each field.
NOTE: For the Host Field, the "FocusMissionssubdomain" set that to the subdomain that you use to log into Focus Missions.
| Vision2 Field | Value To Fill |
|---|---|
| External System | FocusMissions |
| Subscription Type | Individual Profile |
| Host | https://<FOCUSMISSIONSSUBDOMAIN>.focusmissions.com |
| Integration Target Type | Vision2 |
| Max Retries | 10 |
| Retry Interval | 5 |
| Authentication Type | Basic |
| User Name | Note: Same username that is used when setting up integration with Focus Missions. |
| Password / Confirm Password | Note: Same password created with user that was created when setting up integration with Focus Missions |
| Comments | Focus Missions Individual Profile Data Subscription |
After setting up the basic information, next select the Push Change Actions. Focus Missions understands the action of updating a record. Click the update for "Update Record"
| Update a Record | |
| Resource | /ajax/vision2/subscriptions/profile/update |
| Method | POST |
| IncludeDeceased | unchecked |
After setting up the resources click "Save & I'm Done"
Focus Missions interacts with Vision2 around Trip Management by creating and maintaining the trip data from Focus Missions to Vision2. When creating a trip in Focus Missions, there will be a 'Vision2 Options' section to set information that is important to Vision2.
There are two ways to connect a Vision2 trip to a Focus Missions trip. The process will start with providing a designation code for the trip. Focus Missions will search Vision2 for that designation code.
If the designation code exists, then Focus Missions will use the found designation code to connect the trip to Vision2 and not attempt to create an addition trip in Vision2.
If the designation code provided does not exist in Vision2, a few extra fields will be presented that will be used to create the mission trip in Vision2.
'Designation Code' The unique designation code that Vision2 requires to create the designation.
'Account Segment': The account segment used in Vision2 for a quick lookup code.
'Fund': The fund that all donations and trip payments will go to in Vision2.
'Non Charitable Fund': The fund in Vision2 that payment of type fees will go to (example: Background Check fees)
When searching for individuals to add to a trip from an admin perspective, Focus Missions will search Vision2 for the person based on first name and last name. If the individual exists in Vision2, the information about the individual is displayed to be selected.
Focus Missions will add people to Vision2 when they do not exist and will update person information when information about the person is updated in Focus Missions. Furthermore, when people information in Vision2 is updated, that information will be moved over to Focus Missions.
Below is the mapping of data fields from Focus Missions and how they are populated in Vision2 for a person.
| Vision2 Field | Focus Missions Value |
|---|---|
| First Name | Legal First |
| Middle Name | Middle |
| Last Name | Last |
| GenderType | Gender |
| BirthDate | BirthDate |
| Address | Address |
| CellPhone | Phone |
Focus Missions assigns volunteer participants to the mission trip opportunity in Vision2 for team members going on the trip. These team members can be seen under Volunteering > Mission Trips > <<TRIP NAME>>
When an individual applies for a trip, the process starts to add that person to the group in Vision2. Depending on the rules set on the trip in Focus Missions, the is added in one of three statuses.
- Pending Review (if the individual applied and has not been accepted to the trip yet in Focus Missions)
- Accepted (if the individual is actively on the trip either by being accepted or added to the trip in Focus Missions
- Declined (if the individual was specifically rejected as an applicant)
- Removed (if the individual was removed from the trip but not rejected as an applicant)
As the individual goes through the process, Focus Missions will continue to update Vision2 on changes to the volunteer participant
Below is the mapping of data fields from Focus Missions and how they are populated in Vision2 for a volunteer participantPartici.
| Vision2 Field | Focus Missions Value |
|---|---|
| Individual Profile | The person found or created from Focus Missions |
| Volunteer Role (Role is set up in Vision2 through Focus Missions) | Team member or Team Leader. |
| Participant Status | Based on what stage the individual is in on the trip
|
Focus Missions does bi-directional syncing of donation information to and from Vision2. Any donation made in Focus Missions will be moved to Vision2 as a payment with applied payment details.
Any online donation given to a volunteer participant in Vision2 will be moved over to Focus Missions.
When a donation is made in Focus Missions, a transaction will be created in Vision2. It is possible for a transaction to have multiple applied payment details associated to it, depending upon how the money needs to be allocated to team members. For instance, if a group 3 people apply for a trip and want to pay a $100 deposit, a transaction of $300 will be recorded in Vision2 and then 3 different $100 applied payment detail records will be created and associated with the 3 volunteer participants going on the trip.
Focus recommends that cash and check donations are recorded first in Vision2. This will allow Focus to pick up the donation and record it in Focus Missions