Skip to main content
spencer_engel
spencer_engel
Expert ⭐️
October 16, 2020
New Idea

Allow more outputs for Case Expression (dates, emails, etc.)

  • October 16, 2020
  • 10 replies
  • 233 views

In the Rules Engine, there are many use cases where it would be helpful to be able to output a date as well as email. Right now, we can only output booleans, numbers, or string fields.

    10 replies

    phani_kumar
    phani_kumar
    Gainsight Employee ⭐️⭐️
    October 17, 2020

    +1. My :ballot_box: to this idea.

      ana_g
      Helper ⭐️
      October 20, 2020

      Have definitely had this need come up before. +1!

      Anastassia Goidina
      cnichols
      cnichols
      Helper ⭐️
      October 30, 2020

      +1 from me! 

       

      This would be a great help. 

      kumaranbcak
      Contributor ⭐️⭐️⭐️⭐️⭐️
      October 12, 2021

      ​​​​​​Definitely needed

      Muthu Kumar Karuppiah
      jkolle
      Helper ⭐️
      November 23, 2021

      I require this functionality for a date output in case expression.

        narayanan_s
        narayanan_s
        Contributor ⭐️⭐️⭐️⭐️⭐️
        November 24, 2021

        +100 Votes, Can we get this as Idea for people to vote. 

        @pgeorge Could you please get this to the right team visibility as it becomes a long time wait, thanks!

        Narayan
          anirbandutta
          anirbandutta
          Expert ⭐️
          November 25, 2021

          In the Rules Engine, there are many use cases where it would be helpful to be able to output a date as well as email. Right now, we can only output booleans, numbers, or string fields.

          @spencer_engel , I’m missing a convert-to-Idea-from-a-discussion magic on the platform currently so I’d request if you could pl post this as one. And help us expanding on some of the usecases and impact, examples, etc. Thank you.

          It's an opportunity for engagement
          spencer_engel
          spencer_engelAuthor
          Expert ⭐️
          November 29, 2021

          In the Rules Engine, there are many use cases where it would be helpful to be able to output a date as well as email. Right now, we can only output booleans, numbers, or string fields.

          @spencer_engel , I’m missing a convert-to-Idea-from-a-discussion magic on the platform currently so I’d request if you could pl post this as one. And help us expanding on some of the usecases and impact, examples, etc. Thank you.

          Will we lose all the likes and upvotes we’ve already gotten? Pretty sure things have been converted to ideas plenty of times in the past...

            jparker
            jparker
            Contributor ⭐️⭐️⭐️⭐️⭐️
            March 4, 2022

            I’ve added this as a product/feature request for better visibility so feel free to vote on that if this still a feature that you need:

             

            Looking for my next role: Gainsight Lead / CS Ops Product Council Member. Let's connect: https://www.linkedin.com/in/jon-parker/
              anirbandutta
              anirbandutta
              Expert ⭐️
              March 7, 2022

              In the Rules Engine, there are many use cases where it would be helpful to be able to output a date as well as email. Right now, we can only output booleans, numbers, or string fields.

              @spencer_engel , I’m missing a convert-to-Idea-from-a-discussion magic on the platform currently so I’d request if you could pl post this as one. And help us expanding on some of the usecases and impact, examples, etc. Thank you.

              Will we lose all the likes and upvotes we’ve already gotten? Pretty sure things have been converted to ideas plenty of times in the past...

              I have moved it to the CS Ideas forum and it auto converts to an ‘Idea’ given that’s the only content-type it allows. Guess, I understand the system better now and thanks for the challenge @spencer_engel , the ‘Likes’ have become ‘Votes’.

              cc @rakesh 

              It's an opportunity for engagement
                Terms & ConditionsAccessibility statement