Skip to main content
sarahmiracle
VIP ⭐️⭐️⭐️⭐️⭐️
October 5, 2022
New Idea

Allow calculated GSID field to be used in JO program CTA Owner

  • October 5, 2022
  • 5 replies
  • 130 views

I have a longer running program that fires off a CTA to the CSM on the account. I learned recently that I cannot use a calculated field to ensure the CTA is being assigned to the new CSM on the account, if there was an account transition that took place during the time of the journey. 

Please allow us to use calculated fields in the CTA Owner dropdown for CTAs created from JO. This means that I will not be able to use the JO functionality to create the CTA and will instead need to use a Rules Engine.

5 replies

mindy
Helper ⭐️
May 14, 2024

We were just trying to build a scenario at PAL in the new JO and we wanted to use CSM GSID for the CTA Owner. Make it possible! CSMs change while people are going through the program and we need to know that we’re assigning CTAs to the right person.

dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
May 14, 2024

YEEEEESSSS!

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
Stuart
Helper ⭐️⭐️
May 15, 2024

+1, this just makes so much sense - without it Admins must create a number of calculated fields to ensure the email is sent from, or the CTA is assigned to the correct CSM.  If CSM assignment changes while the participant is mid-journey, I’m struggling to think of an example where we’d want the email to send from, or assign the CTA to the previous CSM.

romihache
VIP ⭐️⭐️⭐️⭐️⭐️
May 15, 2024

💯
The Company data is dynamic and features should make it easy to align with that flow.

Continuous improvement is better than delayed perfection
Stuart
Helper ⭐️⭐️
June 28, 2024

Came across this again today. It would be good to hear from Vijay or someone else on the PM team close to JO if a calculated GSID field isn’t allowed, how we should ensure the current CSM receives the CTA, unless the CTA action is pulled out of JO into a rule and, if that’s the case, doesn’t it make having CTA as an action in JO a bit redundant if we can’t ensure triggering the CTA in JO will assign the correct CSM?