...
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 | ||
|---|---|---|
| ||
| Tip | ||
You will confirm that this was successful. |
...
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 | ||
|---|---|---|
| ||
| Tip | ||
When you approve the final build, the integration is complete! |
...
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. |
...
If needed, the JUNO Development team makes edits.
| Paneltip | ||
|---|---|---|
| ||
|
...
The Client team reviews content on the production site to ensure it is correct.
| Panel | ||
|---|---|---|
| ||
| Tip | ||
When you approve the final build, the integration is complete! |
...