Skip to main content
sarahmiracle
VIP ⭐️⭐️⭐️⭐️⭐️
December 7, 2023
New Idea

Clone fetch tasks in Horizon Rules

Related products:CS Rules Engine
  • December 7, 2023
  • 5 replies
  • 88 views

Posted 5 years ago for a Bionic rules enhancement, and now created again as an ask for a Horizon Rules enhancement.

It’d be awesome if we could “clone” fetch tasks in Horizon Rules.

 

 

5 replies

sarahmiracle
VIP ⭐️⭐️⭐️⭐️⭐️
December 7, 2023

bionic rules enhancement request:

 

Customer Success Systems Admin @ Amplitude, 3x Gainsight CS Ops Product Council Member
alizee
VIP ⭐️⭐️⭐️⭐️⭐️
December 8, 2023

You got my vote for anything that’s got to do with cloning - I encounter this kind of need so often. 

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.
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
December 8, 2023

Clone all the things!

Evaluate steps, program action steps, queries… everything!

#product-parity❗

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
spencer_engel
Expert ⭐️
December 10, 2024

Can we please merge this idea with the following? 

Also, this question is marked as “solved” and ​@rakesh mentions the ability to clone being on the roadmap. Any idea if that is still planned soon? It’s been more than a year since the latest update. 

 

TMaier
Helper ⭐️
December 10, 2024

While I appreciate the intention behind the new ability to save task templates for rules / data designer, I feel like that fills a different intent in the workflow for repeatably deploying more complex task trees. It would be very convenient to be able to select “duplicate” from the context menu on a single task within the config screen while building for smaller copy actions.

 

Sidebar: I’m also not 100% comfortable using an aged asset in the form of a template, given that we sometimes see issues with “metadata corruption” affecting rules. There’s no easy way to tell whether a template contains this kind of corrupted metadata, and I’d hate to spread it around by using an affected template. May be a bit of paranoia on my part but I thought I’d add that in because it’s one of my concerns with templates in general.