Búsquedas recientes


No hay búsquedas recientes

Jakub's Avatar

Jakub

Incorporación 30 sept 2022

·

Última actividad 02 ene 2025

Zendesk Customer Care

Seguimientos

0

Seguidor

1

Actividad total

179

Votos

3

Suscripciones

74

RESUMEN DE LA ACTIVIDAD

Última actividad de Jakub

Jakub hizo un comentario,

Comentario de la comunidad Q&A - Help center and community
Hello Taeha,
 
as the code provided by Damon is specific to his use case it is essential that it is reviewed on per case basis, as general answer would be misleading for somebody trying to achieve a similiar goal, each costum code solution should be tailered 

Ver comentario · Publicado 02 ene 2025 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Users, groups, and organizations
Hello,
 
within Zendesk it is possible to achieve using a webhook and trigger to pass data from one field to another.

Ver comentario · Publicado 02 ene 2025 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Help center and community
Hello ,
 
You can achieve this by customizing your section template:
 
Guide Admin > Themes > Customize > Edit code and locate the element you want to include the button in. This would be the element for subsections:
 

Ver comentario · Publicado 02 ene 2025 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Tickets and email
Hello,
 
satisfaction.rating_section is the placeholder for the old csat experience (Good/Bad).
 
If you activated new experience with scale, the placeholder that needs to be used is satisfaction.survey_section.

Ver comentario · Publicado 02 ene 2025 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Objects, workspaces, and rules
Hello,
 
Templates have access to various properties of your help center. For example, the New Request Page template has access to an object named new_request_form that has properties as per the form requested by the User. You can use dot notation to pluck information from the object. 
 
Example:
{{new_request_form.ticket_fields}}
 
Now, as the new_request_form object outlines > https://developer.zendesk.com/api-reference/help_center/help-center-templates/objects/#new-request-form-object
 
You can access its property > ticket_fields
ticket_fields array An array of ticket field objects containing all the standard and custom fields of the selected ticket form
 
You can see the array of Fields for this Form :
console.log(props.requestForm.ticket_fields)

 
Which will render the array of ticket fields for this Form selected :

 
And then if you want to know the level of subkeys/subprops for this Ticket Field Object, here it is > https://developer.zendesk.com/api-reference/help_center/help-center-templates/objects/#ticket-field-object
 
Then you can set the Field value as the property/attribute is accessible.
 
And thus something like :
props.requestForm.ticket_fields[0].value = "Description from Props"
As the index [0] from this Array is indeed my description field.
 
Would set the value, example (basic example use case) : 
 

 
Result:

 
You can tailor this process for CC field accordingly

Ver comentario · Publicado 02 ene 2025 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Help center and community
Hello ,
 
Yes, this still would involve working with custom code to perform this level of customization as natively the descriptions are plain text.

Ver comentario · Publicado 02 ene 2025 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Tickets and email
Hello ,
 
This is possible but will require some development on your side, as this is not a straight out-of-the-box solution. Please note that Zendesk does not support or guarantee custom code as this fails outside of our support scope.
 
These steps are only for instructional purposes (i used user field, but the same logic follows for organization field)
 
1. Create a webhook (https://support.zendesk.com/hc/en-us/articles/4408839108378) and select Triggers and Automation (screenshot)
 
In the name put whatever you want to call it, in Endpoint put: https://bluumhelp.zendesk.com/api/v2/tickets/13126643 ,  Request Method PUT, Format JSON, and the method you want to authenticate it with.
 
2. Create both fields, ticket and user field, if you already have them, skip this step. We will need the field id and user field key:
 
3. We need to create a trigger that will make a call to our webhook whenever a set of conditions is met, so you can set whatever you want this action to trigger, I only set the Ticket is Updated for test purposes:
 
The actions is what matters here, select Notify an active webhook and the webhook you created in step 1. Put there:
 
{`
`"ticket": {`
`"custom_fields": [{ "id": 19355046105108, "value": ""}]`
`}`
`}
 
This is important, change the id for your ticket field id, and in the value placeholder the last part after custom_fields you need to put the user field key I have shown you before.
 

Ver comentario · Publicado 30 dic 2024 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Objects, workspaces, and rules
Hello,
 
My name is Jakub and I am contacting you from Zendesk. From what you said, I've noted you would like to map user fields to custom ticket fields.
 
This is possible but will require some development on your side, as this is not a straight out-of-the-box solution. Please note Zendesk does not support or guarantee custom code as this fails outside of our support scope.
 
These steps are only for instructional purposes:
 
1. Create a webhook and select Triggers and Automation (screenshot)
 
In the name put whatever you want to call it, in Endpoint put: https://chimecrm.zendesk.com/api/v2/tickets/{{ticket.id}} , Request Method PUT, Format JSON and the method you want to authenticate it with.
 

 
2. Create both fields, ticket and user field, if you already have them, skip this step. We will need the field id and user field key:
 

 

 
3. We need to create a trigger that will make a call to our webhook whenever a set of conditions is met, so you can set whatever you want this action to trigger, I only set the Ticket is Updated for test purposes:
 
The actions is what matters here, select Notify an active webhook and the webhook you created in step 1. Put there:
 
{
"ticket": {
"custom_fields": [{ "id": 19355046105108, "value": "{{ticket.requester.custom_fields.user_field}}"}]
}
}
 
This is important, change the id for your ticket field id, and in the value placeholder the last part after custom_fields you need to put the user field key I have shown you before.
 
That's done!

 
 

Ver comentario · Publicado 27 dic 2024 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Help center and community

The subscription to a section is not going to change upon locating a section in another category. You can place it somewhere else, and your users will keep receiving notifications. 

Ver comentario · Publicado 25 nov 2024 · Jakub

0

Seguidores

0

Votos

0

Comentarios


Jakub hizo un comentario,

Comentario de la comunidad Q&A - Help center and community

Hello Jan Slansky 
 

Templates in your help center have access to various properties. For instance, the New Request Page template includes an object named new_request_form, which contains properties based on the form requested by the user. You can utilize dot notation to retrieve information from this object.

Example:

{{new_request_form.ticket_fields}}

 


As detailed in the New Request Form Object documentation (https://developer.zendesk.com/api-reference/help_center/help-center-templates/objects/#new-request-form-object), you can access its property: ticket_fields.


ticket_fields

  • Type: Array
  • Description: An array of ticket field objects that includes all standard and custom fields of the selected ticket form.

To view the array of fields for this form, you can use the following code:

To view the array of fields for this form, you can use the following code:

 

console.log(props.requestForm.ticket_fields);


This will render the array of ticket fields for the selected form.

If you need to explore the subkeys or subproperties of the Ticket Field Object, refer to the Ticket Field Object documentation.

 

You can set the field value since the property/attribute is accessible. For example:


props.requestForm.ticket_fields[1].value = "Description from Props";


In this case, the index [1] corresponds to my description field, and this line would set its value.

 

 

 

Ver comentario · Publicado 08 nov 2024 · Jakub

0

Seguidores

1

Voto

0

Comentarios