mccabe.tonna

@Andrew 

If their primary email is verified; you can search your user functions.

this looks promising via API https://developer.zendesk.com/api-reference/ticketing/users/user_identities/#make-identity-primary although I've never done this before. 

 

@Andrew 

can you give an example of what you're looking to achieve?

the checkbox logic should actually be swapped.

{% if ticket.ticket_field_ contains 0 %}
checkbox is unchecked
{% else %}
checkbox is checked
{% endif %}

should actually be

{% if ticket.ticket_field_ contains 1 %}
checkbox is checked
{% else %}
checkbox is unchecked (or null)
{% endif %}

reason: when a checkbox is not visible on a form; it returns null value. This accounts for explicitly checked boxes

@Ali van de Poll 

I had a similar issue where the user's name was either their name or their email address

Instead of having a separate field, why not utilize the requester's name?

I created a liquid-markup dynamic content field that accomplishes something similar

I named the Dynamic content "name" so referencing it is {{dc.name}} on all macros and content

{% if ticket.requester.email == ticket.requester.name %} there{% else %} {{ticket.requester.first_name}}{% endif %}

Example: Hi {{dc.name}},

produces, Hi there, or Hi McCabe,

 

Similarly you could remove the "there" portion and leave it blank

@... in your help-center, go to your theming, customize, edit code (bottom)

access your script.js function and plop this in there.

Then submit

This will hide the form selector IF they end up on this form. You may need to reference this form via URL directly.

var form = $('#request_issue_type_select').val();
     if (form == 1900000215705){
$('.form-field.request_ticket_form_id').hide()
}

In your script.js file, it should look like this.

Let me know if this works for you

@... which field are you trying to hide? 

What Do You Need Help With? or the form? 

@Administradores IZA

Set or get?

If you're trying to set a value you need to include what value you're trying to set - zafClient.set('ticket.customField:custom_field_360018041180', value)

but a Get could look like the following if you want to store to a var - i use this method below to get multiple values at once

client.get(['ticket.customField:custom_field_360018041180']).then(function(data){

     let value = data['ticket.customField:custom_field_360018041180']

})

@ryan Can you screenshot the triggers that are firing when a ticket is made?

Ticket Created (1st trigger)

 

 

This trigger at bottom  (this is the "your request was received) (note this trigger does not have any "your ticket was created or updated conditions") 

And since it sits below the setting the no-reply target it gets hit just after the address is set

 

this is ticket received looks like:

Sorry for all the blur - have to keep PII safe 

Hi Ryan,

Oh try this - try swapping the order of your triggers around. 

(i had a long hypothesis written up, but this might be a quicker solution) 

 

My order is set the No-reply with the target

then below is the actual email the requester

 

Okay so the email should not go out on the Ticket is received Trigger.

Notify the target after your ticket is updated using the first trigger

 

Does that make sense?