Clone 'Program Steps' in Dynamic JO

Yet another “Private Beta Group Post Locked Behind the Group” issue… 

To sum up that post from 9 months ago:

alizee

I’m going to be annoying but… could we possibly have the ability to clone steps?

AubreeSorbo

Yes! This would be great - cloning steps and cloning programs would be amazing!!

Elana Cipin

+1!

dayn.johnson

Cloning steps (especially evaluate steps) would be AWESOME.

Take my +1, @alizee!

… 

Has there been any update on whether cloning steps might be a future roadmap item?

And on that note… could we maybe make a saved evaluate step library to pull from for those complex evaluate steps that are the same in EVERY program? (ex: active customers that are not in churn and...)

We basically need to be able to clone any and every asset we can create in Gainsight. 
 

It’s not a toxic trait to want to clone everything. Or is it ? 😅

On my 1st advanced program in the redesigned JO, I desperately see a need for this. It’s fantastic to disconnect steps and connect them elsewhere but any time saved on rebuilding steps is now being used to manually clone steps

Checking in on this over a year later.

Use case: currently building an 8-email journey (spans 1 year), and need to build the SAME evaluate step 7 times to confirm that yes, the participant is still the primary contact and they have an active subscription. We can clone emails, email versions, programs, rules, etc. Why can’t we clone steps INSIDE our programs?

Please create a cloning task force to get this available everywhere. Feels like a good chunk of the time we save through the (smart) automations we design is wasted into cloning steps or other stuff. 

Hey, maybe we’ll be able to pull these elements into Claude via MCP and create a markdown library so we can push configs for evaluate steps, calculated fields, etc. straight into data designer, rules engine, or JO queries. #MCPallthethings! 😂

Hi ​@revathimenon -- could we get some PM eyes on this one? Feels like a good time (post Pulse) to ask about building out an evaluate steps/calculated fields/etc library -- especially with the new JO features for AI JO… create the assets once, let AI pull from an admin pre-approved asset library when creating JOs. That would hopefully cut down on errors when AI builds all the things.

On it ​@dayn.johnson 

Thanks everyone for the continued feedback. Dayn, appreciate you flagging this directly. 

Quick note on the AI angle, we're actually thinking about this at the whole program level, where AI can suggest and scaffold entire programs rather than individual steps, to build a new program.

A couple of questions to help us understand the scope better - 

1. Which step types matter most to you — Evaluate, Send Email/Survey, or all? Are there some you'd prioritize?
2. If AI is scaffolding whole programs, would a step library still be valuable or does the program-level approach cover the need? ​@dayn.johnson