Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Delete this page properties table before pushing to Viewport.
Page Properties
Note
VX.XX Anything else clients want to know about integrations?

Status

Status
colourRed
titlenot visible to public
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status
titleDraft
Remember to lock the page before saving!
,resolution
serverId3f12f153-bffd-3ed0-b47b-ead9f2659362
keyJDT-81

Type

How to / Reference / Explanation / Tutorial

Reader

Clients / Exhibitors / Sponsors / Speakers / Moderators / Attendees

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

Review deadline

Notes for reviewers

Integration is a way to transfer information from your data management system (DMS) to your JUNO platform. The development of any integration is a team effort between the Client and JUNO teams. This guide outlines that process so that you know what to expect.

...

After the kickoff meeting, the JUNO Success Manager sends the Client team a Google form and allowlist to complete as homework.

Panel
bgColor#F4F5F7

Your homework, due by the Integrations meeting:

📄 API Registration Form or 📄 SSO Form
📋 Allowlist for Integrations

2. Integrations meeting

During the meeting, the JUNO Success Manager, JUNO Integrations Team, and Client team walk through the mapping document and requirements.

...

Panel
bgColor#E3FCEF

(tick) You will review test and approve the final build. Then the integration is complete!

...

After the kickoff meeting, the JUNO Success Manager sends the Client team a Google form and allowlist to complete and as homework, along with a mapping document and video to review as homework.

Panel
bgColor#F4F5F7

Your homework, due by the Collecting Content meeting:
📄 Content Integration Form (to complete)
📋 Allowlist for Integrations (to complete)
📄 Content Mapping Document (to review only, not complete)

Supporting Resources:
🖥 Training video: How to use the Content Mapping Doc
📄Example of a completed Content Mapping Doc

2. Collecting content meeting

...

Panel
bgColor#F4F5F7

Your homework, due by the Integrations meeting:
📄 Content Mapping Document (to complete)

Supporting Resources:
🖥 Training video: How to use the Content Mapping Document
📄Example of a completed Content Mapping Document

3. Integrations meeting

Using the completed homework documents, the JUNO Integrations team pulls an initial payload of information before the meeting.

...

  1. The JUNO Success Manager gives the mapping document to the JUNO Development team. They also add the Client team’s tags to the platform.

  2. The JUNO Integrations team pulls a sample payload .The JUNO Integrations team and JUNO Success manager work together to import and imports the sample onto the site. There are 2-3 pieces of content per content type.

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
bgColor#E3FCEF

(tick) You will review the sample mapping.

6. Pull full payload

The full payload is pulled 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

  1. 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.

  2. If needed, the JUNO Development team makes edits.

...