Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    JPKelliher
    JPKelliherContributor ⭐️⭐️⭐️⭐️⭐️

    Launch engagement, guide, article, etc. from engagement, button. link, etc.New Idea

    Reposting for upvote capability. (Thanks @link_black  😁) I have scoured the PX community in search of all questions and requests regarding forcibly launching an engagement from a variety of different triggers; embedded links, buttons, badges, emails, etc. I wanted to combine all of these into a single request where we might be able to get enough people to vote this up as a critical feature request.  I can see this goes back at least three years in some form or another, but I believe that all of us have at some point desired the ability to  launch an engagement based on the user’s own choice. Offering the user to option to start an engagement from a link, or a badge in the product, or a URL embedded in and email. I will take it as far as to state that not just engagements, but articles, or even a knowledge bot itself would ideally be able to be called up at any time if a user needs it and we can “point” to the unique GCP id that contains the content we need to share. We have tried all of the workarounds (many of which you shared with the community, and thank you) but we cannot find a way to execute them consistently or without opening up security issues.  I was hoping we could all “up vote” this request and hopefully get it prioritized. Please share with your colleagues, business partners, or maybe just someone you bumped into at Pulse. 😁 Let’s get some momentum behind this and see if Mickey’s team can make it possible. I think we all voted for this in some manner or another,  but this way we will have a unified request.Example@harshibanka @link_black  @jared2095 @KPedroza @dzilli @alextran @dileepnalla @mikewohlwend  @christopher_sanderson @angelo @lila_meyer @suryanarayana @sai_ram @bostojic @Ekta Kumari @JayS @anirbandutta @IO Community Account  @rketharaju @cakrit @catchprakash @michael_sweeney @richiemin @Jef Vanlaer @acheslow @jean.nairon @john_apple @shireesha_reddy @jp_lingamaneni @bostojic @Ekta Kumari @Aphrodite @aharkut @chase @sgage @Lake1211 

    bradley
    bradleyExpert ⭐️

    Improve SFDC Picklist and MDA Picklist Comparison in Horizon Rules/Data designerNew Idea

    Context:If you have an SFDC Picklist and an MDA Picklist that both have the same values, you cannot easily compare them. For example, your picklist in both systems looks like this:Value 1 Value 2 Value 3with your field names of MDA_Picklist and SFDC_PicklistIf you want to filter records where MDA_Picklist = SFDC_Picklist it won’t work, because the picklists are treated as GSID and SFDCIDs, respectively, and obviously won’t match.To date, you’ve had to solve this by adding transformation steps and Case fields (which are tedious and hard to manage) to convert a particular Picklist value to a String output, and then compare those case fields. Or fully duplicate picklists as string fields. Problem:Data Designer (DD) and Horizon Rules (HR) give us the ability to easily duplicate an MDA Picklist as a String picklist “Label” field. That only solves half the problem.SFDC Picklists can be “mapped” to an MDA picklist but you still cannot compare it to an MDA Picklist in a filter such as MDA_Picklist = Converted_SFDC_Picklist.You also do not have the option to duplicate an SFDC Picklist to a String label equivalent like you do with an MDA Picklist.While Gainsight states that “SFDC Picklists are treated as Strings”, that is ONLY true for joins, and possibly if you’re using DD and publishing it as an MDA. It does not work in data prep to compare values. Request:The request is to solve this requirement to use case statements in data prep if you want to compare MDA and SFDC Picklists. An example of a useful solution would be to give us the same duplicate to string Label field like we have for MDA picklists. Another example would be when you map an SFDC Picklist to an MDA picklist, actually let you compare values to an MDA Picklist as if it were one.