Publishing & Versions

Score CRM uses a draft/publish model for journeys, ensuring you can safely edit live journeys without disrupting customers currently in flight.

Draft vs. Published

Aspect	Draft	Published
Visibility	Only in the editor	Live and processing
Customer enrollment	No customers flowing	Customers actively progressing
Editable	Fully editable	Read-only (create new draft to edit)
Multiple can exist	One draft at a time	One published version active

Publishing a Journey

When your journey design is ready:

1. Click Publish in the journey builder
2. The current draft becomes the published version
3. Customers begin enrolling (based on the entry trigger)
4. The journey is now live

What Happens on Publish

• The draft version is promoted to "published" status
• A version snapshot is saved (for rollback)
• Entry triggers become active
• Customers already enrolled (from a previous version) continue on their current path

Editing a Published Journey

You cannot directly edit a published journey. Instead:

1. Go to the published journey's page
2. Click Create Draft
3. A new draft is created as a copy of the published version
4. Make your changes in the draft
5. Click Publish to deploy the updated version

Impact on In-Flight Customers

When you publish a new version:

• Customers already in the journey continue on the previous version's path
• New enrollments use the new version
• This prevents disruption to customers mid-journey

Version History

Score CRM keeps a history of all published versions:

1. Go to the journey's detail page
2. Click Versions to see the version history
3. Each version shows:
   • Version number
   • Published date
   • Who published it

Reverting to a Previous Version

If a new version has issues:

1. Open the version history
2. Click Revert on the desired version
3. A new draft is created from that version
4. Review the draft
5. Publish to make it active

info

Reverting creates a new version (not a true rollback). The version history always moves forward, maintaining a complete audit trail.

Discarding Drafts

If you've created a draft but decide not to publish it:

1. Go to the journey's draft view
2. Click Discard Draft
3. The draft is deleted and the current published version remains active

Journey Lifecycle

Pausing and Resuming

Independent of the draft/publish system, you can pause and resume a published journey:

• Pause: Stops all processing. Customers remain at their current step but don't advance. No new enrollments occur.
• Resume: Restarts processing. Customers continue from where they were paused. New enrollments resume.

This is useful for:

• Investigating issues without unloading customers
• Seasonal pauses
• Maintenance windows

Best Practices

• Always test drafts: Enroll test contacts before publishing to the full audience
• Use version history: Before major changes, note the current version number in case you need to revert
• Minimize published edits: Plan your journey thoroughly before publishing to reduce version churn
• Pause before reverting: If something goes wrong, pause the journey first to stop customer progression while you investigate