...
Status
...
| Status | ||||
|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Type
...
How to / Explanation
...
Reader
...
Clients
...
Reader goal
...
Understand the integration process so they know what to expect.
...
Contributors
...
Amira (info from internal doc)
...
JUNO version
...
Reviewers (check the box when you’re done!)
...
- Amira
- Travis
...
Review deadline
...
...
Notes for reviewers
Integration is a way to transfer information from your data management system to your JUNO platform. The development of any integration is a team effort between the Client team and the JUNO team. This guide outlines that process so that you know what to expect.
...
With API registration integration and Single Sign On single sign-on (SSO) integration,our goal is to get users registered on the platform. With Content integration, our goal is to get content onto the platform.
API Registration Integrationregistration integration
Use this when your users register for the event in one place but have not created a password or other login credentials before. API Registration Integration takes user information from your database and pulls it into your JUNO platform. Then JUNO generates a “magic link” that users click to log in without a password.Single Sign On sign-on (SSO) Integrationintegration
Use this when your users already have login credentials for your organization’s external site. SSO Integration takes user credentials from your database and pulls them into your JUNO platform. This means that people log into JUNO using the same usernames and passwords as on your member sites. When logging in, users are briefly redirected to enter their credentials on your organization’s site, then brought back to JUNO once the credentials are verified.Content integration
Use this when ___your existing content is already housed on a third-party content management system. Content integration takes text, image, and video content from your database and pulls it into pulls the content directly from that third party and displays it on your JUNO platform.
| Info |
|---|
...
| Panel | ||
|---|---|---|
| ||
Your homework, due by the Integrations meeting: |
...
During the meeting, the JUNO Success Manager, JUNO Integrations Team, and Client team walk through the mapping document and requirements.
☑ Agenda:
Walk through the tabs of the mapping document.
Go over any specific access codes; Staff, Exhibitor, etc.
Discuss any specific dimensions JUNO should be pulling over from registration; City, Country, etc.
Discuss any business rules.
Discuss attendee communication.
Go over email templates. The Client team will provide images and copy for the email template.
...
| Panel | ||
|---|---|---|
| ||
Your homework, due by your third meeting with JUNO: 🖥 Supporting resources: |
3. JUNO pulls a sample payload and reviews the initial mapping document
...
The JUNO team checks the attendee count in the sample payload and shares it with the Client team. If the Client team confirms the count is correct, it’s time for JUNO to begin coding.
| Panel | bgColor | #E3FCEF
|---|
| Tip |
|
...
If needed, the JUNO Development team makes edits.
| Paneltip | ||
|---|---|---|
| ||
|
...
The Client team tests users on the production site to ensure the integration is flowing correctly.
| Panel | bgColor | #E3FCEF
|---|
| Tip |
|
...
| Panel | ||
|---|---|---|
| ||
Your homework, due by the Collecting Content meeting: Supporting resources: |
2. Collecting content meeting
During the content meeting, the JUNO Success Manager and the Client team discuss the mapping document.
☑ Agenda:
Review the Content Integration Form.
Review key milestones and timelines.
Review mapping document needs. Discuss each type of content and discuss how to fill the document out.
| Panel | ||
|---|---|---|
| ||
Your homework, due by the Integrations meeting: |
...
During the meeting, the JUNO Success Manager, JUNO Integrations Team, and Client team walk through the mapping document and requirements.
☑ Agenda:
Review each tab of the Content Mapping Document.
Address questions from the Integrations Team.
Review the test content. The Client team signs off on the test content, if possible.
Discuss necessary edits.
Discuss a due date for edits and action items.
| Panel | ||
|---|---|---|
| ||
| Tip | ||
You will confirm that the test content was successful. |
| Panel | ||
|---|---|---|
| ||
Your homework, due by the discussed date: |
...
If needed, the JUNO Development team makes edits.
| Panel | bgColor | #E3FCEF
|---|
| Tip |
|
...
The Client team reviews content on the production site to ensure it is correct.
| Paneltip | ||
|---|---|---|
| ||
|
...