Búsquedas recientes


No hay búsquedas recientes

Matt Owens's Avatar

Matt Owens

Incorporación 15 abr 2021

·

Última actividad 08 may 2023

Curious person who dabbles in technical fields. Long time user of Zendesk.

Seguimientos

0

Seguidores

0

Actividad total

29

Votos

6

Suscripciones

13

RESUMEN DE LA ACTIVIDAD

Última actividad de Matt Owens

Matt Owens hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

Hey team, 

Wanted to see if this was something in the works? I know the Custom Object Look-up fields are on the horizon, so wasn't sure if this would be part of that work?

Best,

Matt

Ver comentario · Publicado 08 may 2023 · Matt Owens

0

Seguidores

0

Votos

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Q&A - Users, groups, and organizations

I'd like to also add another use case for the team. 

Currently we have an integration with Workday that leverages the Create or Update endpoint and external ID for any changes. Mostly we have user fields that hold information such as location, cost center, employee type, etc. 

An issue we have is when a user is converted from Contractor to Full Time. We have different email domains, one being @companycontractors.com and the other being @company.com. While we are able to add the new email (conversions typically are contract to FTE, rare cases reversed) it's not set as the new primary email. There is a grace period before we remove access to the old domain. In some situations employees are submitting tickets without seeing any notifications back as the email is secondary. 

Ideally we'd like to have the option in the Create or Update endpoint to specify Primary Identity when doing these calls. 

Best,

Matt

Ver comentario · Publicado 18 nov 2022 · Matt Owens

0

Seguidores

0

Votos

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

Hey Eric, 

Currently we implemented the above use case, and are indeed blocked because there is no way to have anonymously read objects. The authenticated experience is great, but the experience would be next level with anonymous endpoints. 

I've also shared feedback that this will need to be in place if there is any hope to have Look-Up fields be end-user editable for un-authenticated support contacts leveraging objects. 

 

Ver comentario · Publicado 17 nov 2022 · Matt Owens

0

Seguidores

0

Votos

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

I think that's pretty much it, happy to clarify anything if there are questions. 

Best, 

Matt

Ver comentario · Publicado 16 jul 2021 · Matt Owens

0

Seguidores

0

Votos

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

Hey Jessica, 

There are some good resources here about customizing text on the widget. 

Ver comentario · Publicado 21 jun 2021 · Matt Owens

0

Seguidores

0

Votos

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

Hey Jon, 

Do you already have the object associated to the User object with a relationship? If so you'd just need to use the List Related Object Records endpoint with the User ID. 

  function userKits(client, id) {
var kits = {
url: '/api/sunshine/objects/records/zen:user:' + id + '/related/{relationship_type}',
type:'GET',
dataType: 'json',

};

From there you just parse and display the data in the object record you want to show. 

If you don't yet have the user associated to an object record, then you'd need to set up your relationship type, and then have a mechanism to associate the two

Matt

Ver comentario · Publicado 21 jun 2021 · Matt Owens

0

Seguidores

2

Votos

0

Comentarios


Matt Owens creó una publicación,

Publicación Developer - Zendesk APIs

Hey team, 

Wanted to see about the feasibility of having an anonymous read-only permission on some of our object types? We had the following use case that we are trying to support. 

Use Case: User scans QR code that has URL which contains the Object ID in the params. On the HC site we fill values from the object to hidden fields on the ticket. User then submits information about the location (think bathroom, needs cleaning). The object look-up should be allowed anonymously as the user isn't required to be signed in to submit a ticket via QR scan. 

Currently we have tested 90% of this, but it appears we'd have to store some generic end-user credentials to make the call. Ideally I'd like to have an option for anonymous read-only for this, or possibly for catalog items in the future. Objects are currently updated via integration to another service, so we want to preserve the URL as opposed to having to update the URL & QR with params when values/names change. 

Publicado 14 jun 2021 · Matt Owens

2

Seguidores

5

Votos

8

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

Anyone have an example application that is pulling related Objects on a user?

url: '/api/sunshine/objects/records/zen:user:' + id + '/related/object_record_name',

 

Ver comentario · Publicado 26 mar 2021 · Matt Owens

0

Seguidores

0

Votos

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Feedback - Ticketing system (Support)

Thank you @... for the additional context! 

Also adding in a vote for this, we have some confirmation checkboxes that would greatly benefit from allowing line breaks and bolding. Looks like URLs auto-format to href links, so maybe opening the scope of the HTML used would be super helpful on our end. 

Ver comentario · Publicado 03 ago 2020 · Matt Owens

0

Seguidores

1

Voto

0

Comentarios


Matt Owens hizo un comentario,

Comentario de la comunidad Feedback - Ticketing system (Support)

Hey Zendesk Team, 

Wanted to check on this, I found a similar conversation from 5 years ago in the About Ticket Fields thread with the following comment

There were two links included, both are dead now. 

Feature Request: HTML in Ticket Field Descriptions as well as Customizing Ticket Field Descriptions With HTML.

Any insight on if the feature was closed as "Won't Do" or if there is a way to get around the HTML scrubbers, of we could get that article published again as "use at own risk"?

Ver comentario · Publicado 03 ago 2020 · Matt Owens

0

Seguidores

1

Voto

0

Comentarios