Recent searches


No recent searches

Daniel Dobrzensky's Avatar

Daniel Dobrzensky

Joined Oct 16, 2021

·

Last activity Feb 22, 2024

Following

1

Followers

0

Total activity

29

Votes

4

Subscriptions

13

ACTIVITY OVERVIEW

Latest activity by Daniel Dobrzensky

Daniel Dobrzensky commented,

Community comment Developer - Zendesk APIs

Ansar KA You'd do this through the Admin Center. 

See: Managing triggers

View comment · Posted Jun 20, 2022 · Daniel Dobrzensky

0

Followers

0

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Developer - Zendesk APIs

Your trigger to fire the email probably doesn't include updates via the API:

 

It could be other things, but that's a good place to start. 

Just be sure you don't have other API updates that shouldn't fire an email. If you do you'd just need to add some conditions to exclude those/only include this one (like comment is present, etc.) 

View comment · Posted Jun 09, 2022 · Daniel Dobrzensky

0

Followers

0

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Feedback - Ticketing system (Support)

There's a Chrome extension for this! Solves the problem perfectly. 

https://chrome.google.com/webstore/detail/zendesk-quicktab/moiloihigegdbekeabannnkibekfnekf

View comment · Posted Mar 05, 2022 · Daniel Dobrzensky

0

Followers

3

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Tickets and email

I don't think Zendesk has a similar reference doc for CSS in emails, but they do go over some good info here: 

Customizing your templates for email notifications

I'm also not sure if you'll be able to apply classes inside of triggers and automations (if that's what you meant). Zendesk intentionally limits what you can do there. 

I suggest you stay away from adding too much code in your triggers and update your email template instead if possible. There's so much more flexibility there. 

View comment · Posted Feb 27, 2022 · Daniel Dobrzensky

0

Followers

0

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Apps and integrations

You can configure Jira to send values into custom fields in Zendesk when you link a ticket to a Jira issue. After that, you can use placeholders for the custom field in the webhook. Hope that helps. 

View comment · Posted Feb 26, 2022 · Daniel Dobrzensky

0

Followers

0

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Help center and community

Ok - I tested this and got it figured out!

The issue was ultimately related to the data type of each value. The category ID is an integer, while the setting value is a string.

I found a way around this by looking at the URL with the filter helper.

Here's the code I used

In the manifest.json file:

{
"label": "Category ID Setting Group",
"variables": [
{
"identifier": "category_first",
"type": "text",
"description": "Category ID Value Description",
"label": "Category ID Value Label",
"value": "1234"
}
]
}

You'll put the numeric category ID in the settings panel (listed as "1234" above). This will allow you to use the ID and it will work for any translated languages you may have. 


In the home_page.hbs file: 

{{#each (filter categories on="url" contains=settings.category_first)}}
{{name}}
{{/each}}

The filter helper looks for the value you entered in the setting panel, which should be the category ID. It's technically possible that you may have two categories that contain the same string of numbers, but it's highly unlikely (for example category 1234 and category 12345). If that happens, you can add a the leading or following hyphen after the number, but I doubt that should be necessary. 

Important note: This must be utilized on the home page template. The categories object is only available on that page. 

I think this will get you there! I hope this helps 😁

View comment · Posted Jan 06, 2022 · Daniel Dobrzensky

0

Followers

1

Vote

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Help center and community

This should be pretty simple then. You have a couple options. 

Option 1 - simplest.

{{#if settings.category_first}}
{{code to render if a value is present}}
{{/if}}

In this case, the block will render whenever you have some value in the theme setting. You can put anything there and it would render. If it's empty, it won't render. 

Option 2

{{#if (compare category.id "==" settings.category_first)}}
{{code to render if true}}
{{/if}}

In this case, the block will only render when the category ID matches what you have in the theme setting. If you input a different value, or leave it blank, it won't render. A note here - you may want to play around with the "==" operator. If it doesn't work, try "=" instead. 

If you later want to exclude that category from an each iteration you can use the unless helper to do that. 

Also, Handlebars has a way to reference steps in an iteration. So you could target the first item, for example. More info here

Hope that helps. 

View comment · Posted Dec 30, 2021 · Daniel Dobrzensky

0

Followers

2

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Help center and community

Gotcha - I was a bit misunderstood. 

Just to clarify - are you hoping to only show the category you enter into the template settings? Or are you trying to display that category in one way, while displaying the all of the others in another? What's your ultimate goal here? 

View comment · Posted Dec 30, 2021 · Daniel Dobrzensky

0

Followers

1

Vote

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Help center and community

Hey Serhii, 

It looks like the syntax is a bit off. When you're using a settings object in an is helper you're comparing the "identifier" on the left, to the "value" on the right. 

Try something like this: 

{{#is settings.category_first "4409347111442"}}
{{your code to render when true}}
{{/is}}

I'm not entirely sure if you need to escape the settings object in this case - you'll want to play around with that. 

Also note the category ID is listed within quotations - this is because the type is listed as text, so it's evaluated as a string instead of an integer. This is important because the is helper uses a strict comparison. 

You might also try just placing the settings.category_first object within your each helper, just to see if it prints out ok. You'd expect a text value for each of your categories. If that works, then add in the is helper. That's just what I like to do to troubleshoot. 

Hopefully this helps you get something working. Good luck! 

 

View comment · Posted Dec 29, 2021 · Daniel Dobrzensky

0

Followers

2

Votes

0

Comments


Daniel Dobrzensky commented,

Community comment Q&A - Help center and community

Zenplates has example code for that in the Documentation section of their site:

https://zenplates.co/framework/plugins/scrollspy

We just updated our help center and we have this feature. You can see it here: 

https://support.scribd.com/hc/en-us/articles/210135426-What-is-Scribd-

 

 

View comment · Posted Nov 07, 2021 · Daniel Dobrzensky

0

Followers

0

Votes

0

Comments