SOLVED

Alternate Token Scenario

Go to solution
Highlighted

Alternate Token Scenario

Hi All,

I have a scenario and would require help on the same.We are builiding a lead notification to our sales team and would like a resolution on this.

In the subject line we are using - {Company} wants to say bye to their {Current Solution}, we're add the following tokens:

1. Company

2. Current solution - In this scenario, there may be customers that will select "other" from landing page. We want to make sure it doesn't say ie. "Company "wants to say bye to their Other(which is an option on the landing page to select). Is there any way to prevent this from happening? For those that mark "other", can we create a generic subject line that shows as {Company} wants to say bye to their current solution?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 5

Re: Alternate Token Scenario

Hi Vikas,

You can achieve it via using tokens in the flow step {{Field Name}} and if the value of other is selected in the drop down pass the same value of others and in the flow step you can use If {{ Field Name}} has value of other change it to {{Your required Value}}

Make sure you add Member of program step in the smart list to be sure you are not appending other values.

View solution in original post

2 REPLIES 2
Highlighted
Level 5

Re: Alternate Token Scenario

Hi Vikas,

You can achieve it via using tokens in the flow step {{Field Name}} and if the value of other is selected in the drop down pass the same value of others and in the flow step you can use If {{ Field Name}} has value of other change it to {{Your required Value}}

Make sure you add Member of program step in the smart list to be sure you are not appending other values.

View solution in original post

Highlighted
Level 10 - Community Moderator

Re: Alternate Token Scenario

I would not use a flow to change the value. There's no reason for that to be a permanent change.

Use a dirt-simple Velocity token:

${lead.Company} wants to say bye to their

#if( $lead.CurrentSolution.equals("Other") )

current solution

#else

${lead.CurrentSolution}

#end

Ensure that the appropriate field names are checked off in the tree in Script Editor, so they'll be readable from Velocity:

https://s3.amazonaws.com/blog-images-teknkl-com/script_editor_tree.png

After checking them in the tree, drag the fields to the Script Editor canvas (the left-hand side) temporarily to get their Velocity $lead.token names. (Those aren't necessarily the same as their {{lead.token}} names used directly in emails.)