最近搜索


没有最近搜索

Jason Littrell's Avatar

Jason Littrell

已加入2022年1月11日

·

最后活动2022年12月27日

关注

0

关注者

0

活动总数

30

投票

5

订阅

20

活动概览

的最新活动 Jason Littrell

Jason Littrell 进行了评论,

社区评论 Q&A - Users, groups, and organizations

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.

查看评论 · 已于 2022年8月23日 发布 · Jason Littrell

0

关注者

0

投票

0

评论


Jason Littrell 进行了评论,

评论Team members and groups

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?

查看评论 · 已于 2022年7月28日 发布 · Jason Littrell

0

关注者

1

投票

0

评论


Jason Littrell 进行了评论,

评论Ticket customization

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.

查看评论 · 已于 2022年7月19日 编辑 · Jason Littrell

0

关注者

1

投票

0

评论


Jason Littrell 进行了评论,

社区评论 Developer - Zendesk APIs

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?

查看评论 · 已于 2022年1月27日 发布 · Jason Littrell

0

关注者

0

投票

0

评论


Jason Littrell 进行了评论,

社区评论 Developer - Zendesk APIs

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.

查看评论 · 已于 2022年1月13日 发布 · Jason Littrell

0

关注者

0

投票

0

评论