Make CTA types inactive without re-assigning closed CTAs

  • 2
  • Problem
  • Updated 1 month ago
  • Acknowledged
  • (Edited)
When we want to de-activate an old CTA type, we need to re-assign the old CTAs to a different (active) CTA type before we deactivate them. But this is a weird behaviour since you would want to keep the old/closed CTAs as it is for reporting purposes. Why do we need to reassign all the CTAs to a different CTA type even when they are closed in order to deactivate a type?
Photo of Meenal Shukla

Meenal Shukla, Employee

  • 1,606 Points 1k badge 2x thumb

Posted 1 month ago

  • 2
Photo of Aditya Marla

Aditya Marla, Product Manager

  • 3,104 Points 3k badge 2x thumb
Hi Meenal,

Thanks for sharing this. Agree that there should not be a need to change anything in already existing CTA types when you want to make it as inactive (inactive should only prevent users from using the CTA type in the future).
Today, before allowing a user to make a CTA type as inactive we check whether it is being used in rules OR if any CTA's exist with the CTA type. We will need to change this behavior when making a status as inactive (and remove the second validation...the check to see whether the CTA type is being used in Rules engine will still be present). Will keep you posted as and when we take this up