Skip to main content
alizee
VIP ⭐️⭐️⭐️⭐️⭐️
January 24, 2023
New Idea

Clone JO participant source

Related products:CS Journey Orchestrator
  • January 24, 2023
  • 3 replies
  • 86 views

I’d really love to be able to clone a participant source within a program. Here’s a use case that I think is pretty universal:

  • I have to send the same email to all customers. 
  • I use 3 participant sources: one for APJ, one for EMEA, one for Americas so they can sync independently from each other to send emails out at decent o’clock for every participant.

I know the new rules engine/data designer/query builder should help save a dramatic amount of time and enhance our experience in that area.

But realistically, I wouldn’t build a new data design for every variant of a data set (for example, EMEA, APAC...). I would something global, fetch it in my participant query, and then apply filters to exclude or include certain things for that specific participant source. 

With that in mind, I’d want to clone my source to make a couple of changes to filters which would be so much quicker than fetching the data design, reapplying filters etc., would avoid creating designs for one-off transformations.

So in short, can we please add a “clone participant query” option, alongside the edit, delete and sync options below?

 

3 replies

saltamash
Helper ⭐️⭐️
January 24, 2023
alizee
alizeeAuthor
VIP ⭐️⭐️⭐️⭐️⭐️
January 24, 2023

@saltamash Thanks, it didn’t pop-up up as a similar idea when I started writing.

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
Contributor ⭐️⭐️⭐️⭐️⭐️
June 15, 2023

I need this! Similar use case, that I always have 3 regions that I build a query for. This is to be able to have a different scheduled time that each query runs, for different time zones. Typically there’s just 1 filter that needs to be different for all queries. 

To replicate this query x2, for example, it took me around an hour to re-build the query. In could have taken 5 minutes instead, to clone, and change 1 filter!