Pesquisas recentes
Sem pesquisas recentes

Matt Owens
Entrou em 15 de abr. de 2021
·
Última atividade em 08 de mai. de 2023
Curious person who dabbles in technical fields. Long time user of Zendesk.
Seguindo
0
Seguidores
0
Atividade total
29
Votos
6
Assinaturas
13
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Matt Owens
Matt Owens comentou,
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
Exibir comentário · Publicado 08 de mai. de 2023 · Matt Owens
0
Seguidores
0
Votos
0
Comentários
Matt Owens comentou,
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
Exibir comentário · Publicado 18 de nov. de 2022 · Matt Owens
0
Seguidores
0
Votos
0
Comentários
Matt Owens comentou,
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.
Exibir comentário · Publicado 17 de nov. de 2022 · Matt Owens
0
Seguidores
0
Votos
0
Comentários
Matt Owens comentou,
I think that's pretty much it, happy to clarify anything if there are questions.
Best,
Matt
Exibir comentário · Publicado 16 de jul. de 2021 · Matt Owens
0
Seguidores
0
Votos
0
Comentários
Matt Owens comentou,
Hey Jessica,
There are some good resources here about customizing text on the widget.
Exibir comentário · Publicado 21 de jun. de 2021 · Matt Owens
0
Seguidores
0
Votos
0
Comentários
Matt Owens comentou,
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
Exibir comentário · Publicado 21 de jun. de 2021 · Matt Owens
0
Seguidores
2
Votos
0
Comentários
Matt Owens criou uma publicação,
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 de jun. de 2021 · Matt Owens
2
Seguidores
5
Votos
8
Comentários
Matt Owens comentou,
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',
Exibir comentário · Publicado 26 de mar. de 2021 · Matt Owens
0
Seguidores
0
Votos
0
Comentários
Matt Owens comentou,
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.
Exibir comentário · Publicado 03 de ago. de 2020 · Matt Owens
0
Seguidores
1
Votos
0
Comentários
Matt Owens comentou,
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"?
Exibir comentário · Publicado 03 de ago. de 2020 · Matt Owens
0
Seguidores
1
Votos
0
Comentários