Búsquedas recientes
No hay búsquedas recientes

Jason Littrell
Incorporación 11 ene 2022
·
Última actividad 27 dic 2022
Seguimientos
0
Seguidores
0
Actividad total
30
Votos
5
Suscripciones
20
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Jason Littrell
Jason Littrell hizo un comentario,
Hey Sal. Here's one way to can accomplish that (whitespace added for clarity):
{% assign names = ticket.requester.name | split: ' ' %}
{% for name in names %}
{% if name contains "'" %}
{% assign split_name = name | split: "'" %}
{% for part in split_name %}
{{part | capitalize}}{% unless forloop.last %}'{% endunless %}
{% endfor %}
{% else %}
{{name | capitalize}}
{% endif %}
{% unless forloop.last %}{{' '}}{% endunless %}
{% endfor %}
Here it is without spaces:
{% assign names = ticket.requester.name | split: ' ' %}{% for name in names %}{% if name contains "'" %}{% assign split_name = name | split: "'" %}{% for part in split_name %}{{part | capitalize}}{% unless forloop.last %}'{% endunless %}{% endfor %}{% else %}{{name | capitalize}}{% endif %}{% unless forloop.last %}{{' '}}{% endunless %}{% endfor %}
That last `unless` block has a placeholder with a single space text string because a regular space kept getting collapsed when I applied the code with a macro. If you use the code in a dynamic content placeholder, a regular space should work fine and you could even use the first code block by adding a dash inside the opening or closing tags where you want whitespace to be removed (see here for more info).
You'll probably need to test for edge cases, and the code doesn't account for user names formatted as ", ", but hopefully it's enough to get you started.
Ver comentario · Publicado 23 ago 2022 · Jason Littrell
0
Seguidores
0
Votos
0
Comentarios
Jason Littrell hizo un comentario,
Agents with the "Requested by end users in their organizations" ticket access can still view private group tickets linked to their organizations. Is this an issue that needs to be fixed or a limitation of the private group functionality?
Ver comentario · Publicado 28 jul 2022 · Jason Littrell
0
Seguidores
1
Voto
0
Comentarios
Jason Littrell hizo un comentario,
I tried to add a Lookup field as a conditional field on a form (as a shown field, not a field the conditions are applied to), but attempting to save the form conditions gave me an error message:
Child field: '<Lookup field name>' is an unsupported child field type.
The About custom field types article doesn't mention that form conditions aren't supported. Is this a known limitation that wasn't listed, or is it an issue that is going to be addressed?
EDIT: Received confirmation here that a fix will go out next week.
Ver comentario · Editado 19 jul 2022 · Jason Littrell
0
Seguidores
1
Voto
0
Comentarios
Jason Littrell hizo un comentario,
Hey Ashley Johnson,
Based on the error description, I'm guessing that the "organization_memberships" parameter has more than one array, like this maybe:
{
"organization_memberships": [
{ "user_id": 12345, "organization_id": 9001 }
],
[
{ "user_id": 67890, "organization_id": 9001 }
]
}
instead of one array with multiple objects, like this:
{
"organization_memberships": [
{ "user_id": 12345, "organization_id": 9001 },
{ "user_id": 67890, "organization_id": 9001 }
]
}
If that isn't the case, though, could you post a sample of the full JSON payload that triggers the error?
Ver comentario · Publicado 27 ene 2022 · Jason Littrell
0
Seguidores
0
Votos
0
Comentarios
Jason Littrell hizo un comentario,
Hi Dean Kongslie,
In the create ticket payload, you can add an 'author_id' property to the 'comment' object (check out the Ticket Comments documentation for more info). The 'current_user.id' placeholder should work for the 'author_id' value, assuming the webhook trigger runs when the agent applies the macro and submits the ticket. Here's a sample payload:
{
"ticket": {
"comment": {
"body": "Something something",
"author_id": {{current_user.id}}
},
...
}
}
Note: per the Author id documentation, the updater of the ticket will still be the authenticated user, so it could have an impact on business rules and views.
Ver comentario · Publicado 13 ene 2022 · Jason Littrell
0
Seguidores
0
Votos
0
Comentarios