Joey

Agnieszka Pyzik any idea when the limit of 100 will be increased? 

This is so very annoying when you do not want to create child tickets but still want to show ongoing side conversations to agents. The fact that views visualize tickets isn't really an excuse, it might be the way it currently works, but it shouldn't. 

This only works if you enable Turn on child tickets on the side conversations page. Very frustrating if you don't want to enable this functionality but still want a view.

Hey David Hall 

We have noticed some new features in the deployment functionality, mainly that webhooks are now being flagged as dependencies which is great.

Have there been any other added functionality that we might not know about?

(I just noticed this post is about automations, my question is about triggers)

Single line text fields can be cleared in triggers by setting them to __NULL__

Am I correct to understand that cloning a trigger in sandbox will make it not show up in the deploy list?

Steps: clone trigger in sandbox -> go to deploy screen -> notice the cloned trigger isn't there.

The original trigger shows up as changed, which it wasn't.

Edit: looks like it shows up when you archive it (probably any following save) 

Edit edit: When adding a trigger in the middle somewhere it will consider all triggers below as changed so now you have to go through the whole list of triggers trying to find what you changed. In our case, we changed 12 triggers but now the deploy list has over 250 changed triggers on that day. Good luck finding those 12 with no search on that page.

I'm trying to deploy a few automations but get the error “This configuration has dependencies that aren’t supported, so it can’t be deployed.” with no indication what dependency is causing the error. There is also no link to the automation in production to quickly check.

The fields exist in both so my assumption here is that the dynamic content is missing (can't search DC, so.), could this cause the error?

The dependencies are definitely a headache creator, after changing three automations in sandbox I now have to go into production and change these three again.

@...,

Good to hear that deployable functionality will be expanded but please first fix these trigger issues. 

Great request.

Ideally it would relate the secure attachments setting to private groups, in our instance those groups deal with sensitive information that should always be secured. But our main support teams deal with non-secure screenshots and images.

Thanks Shawna, but I find it more useful to give feedback and read about other user experiences within the articles.