...
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
- Gabe
- Matt Merrill
- 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.
...
Integration is an alternative to importing users, using JUNO’s free registration, and/or importing content. It’s an extra cost that’s agreed upon in the contract process.
| Info |
|---|
No integration is needed with JUNO’s free registration. It allows users to create their accounts directly through the JUNO platform. Use this when you have a free event with no ticket types and no system in place that already has registration or member information. |
With API registration integration and Single Sign On single sign-on (SSO) integration,our goal is to get users registered on the siteplatform. With content Content integration, our goal is to get content onto the platform.
API registration 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 (SSO) integration
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 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 (see above).
If JUNO is sending email/password or magic links, go over email template and if passwords will be randomly generated or universal.
Go over email templates. The Client team will provide images and copy for the email template.
The After the meeting, the JUNO Success Manager sends the Client team the mapping document and training video to complete as homework.
| Panel | ||
|---|---|---|
| ||
Your homework, due by your third meeting with JUNO: Supporting resources: |
3. Test the endpoint
...
📔 Example completed API Registration/SSO Integration Mapping Document - Spargo |
3. JUNO pulls a sample payload and reviews the initial mapping document
Initially, the JUNO Integrations team pulls a sample payload to ensure we can access the endpoint.
...
Then once the Client team delivers the full mapping document, the JUNO integrations team reviews it. If they have any questions about the data, they bring them to the Client team and make revisions.
4. Sign off on the test
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.
| Paneltip | ||
|---|---|---|
| ||
|
4. Coding begins
...
5. JUNO develops the integration
The JUNO Success Manager
...
adds the Client team’s tags to the platform.
...
The JUNO Integrations team creates an Integration Spec Document that the JUNO Development team
...
5. Review
uses to build the integration.
6. Review the testing environment (“Dev”)
In the testing environment, we can see how your site looks while in development. On a weekly call, the JUNO Success Manager reviews a small sample of each user type with the Client team. Together, they look at the
...
users' information in the content management system, on the profile page
...
, and in the directory.
If needed, the JUNO Development team makes edits.
| Panel | bgColor | #E3FCEF
|---|
| Tip |
|
...
7.
...
JUNO deploys to the production environment (“Prod”)
The JUNO Development team pushes the build from the
...
test environment (
...
“Dev”) to the live production site (“Prod”).
8. Review the production environment
The Client team tests users on the production site to ensure the integration is flowing correctly.
...
| Panel | ||
|---|---|---|
| ||
| Tip | ||
When you approve the final build. Then , the integration is complete! |
...
| 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: |
3.
...
JUNO pulls a sample payload and reviews the initial mapping document
Initially, the JUNO Integrations team pulls an initial payload of information before the meeting.Then during a sample payload to ensure we can access the endpoint.
Then once the Client team delivers the full mapping document, the JUNO integrations team reviews it. If they have any questions about the data, they bring them to the Client team and make revisions.
4. JUNO creates test content
The JUNO team uses sample data provided by the Client team to map and import test content.
5. Integrations meeting / Sign off on the test content
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.
| Tip |
|---|
You will confirm that the test content was successful. |
| Panel | ||
|---|---|---|
| ||
Your homework, due by the discussed date: |
4. Pull a sample payload
...
6. JUNO develops the integration
The JUNO Success Manager
...
adds the Client team’s tags to the platform.
...
The JUNO
...
5. Review sample
On a weekly call, the JUNO Success Manager reviews the content samples with the Client team. They look at the content on the site to make sure it looks correct. They note change requests for the JUNO Integrations team.
| Panel | ||
|---|---|---|
| ||
|
6. Pull full payload
The JUNO team pulls the full payload and the JUNO Development team begins coding. If they have questions, they pass them along to the Client team or join a meeting.
7. Review full mapping
Integrations team creates an Integration Spec Document that the JUNO Development team uses to build the integration.
7. Review the testing environment (“Dev”)
In the testing environment, we can see how your site looks while in development. On a weekly call, the JUNO Success Manager
...
and Client team
...
review content on the site to make sure it looks correct.
If needed, the JUNO Development team makes edits.
| Panel | bgColor | #E3FCEF
|---|
| Tip |
|
8.
...
JUNO deploys to the production environment (“Prod”)
The JUNO Development team pushes the build from the testing test environment (.dev“Dev”) to the live production site . Integration (“Prod”).
9. Review the production environment
The Client team reviews content on the production site to ensure it is correct.
| Tip |
|---|
When you approve the final build, the integration is complete! |