Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send article body #905

Closed
AdiosOnline opened this issue Mar 29, 2017 · 12 comments
Closed

Send article body #905

AdiosOnline opened this issue Mar 29, 2017 · 12 comments

Comments

@AdiosOnline
Copy link

AdiosOnline commented Mar 29, 2017

Infos:

  • Used Zammad version: 1.4.x

Hi,

I set a Trigger to send Public Notes per Mail to the Customer. (Trigger Described in #298 ).
I thought that the Line:
"

Ihr Agent weist auf folgendes hin:
#{article.body}

"
would send the actual content from the last Public note. But the Email the Customer receives looks like:
"

Ihr Agent weist auf folgendes hin:

Ihre Anfrage (Ticket#87473): (Neuen Zamad Agent "Webdesigner"?) wurde vom Support
Team vollständig bearbeitet.

Für weitere Informationen klicken auf den Nachfolgenden Link:[1]
http://zammad/#ticket/zoom/473

Ihr Gruppe - Helpdesk Team

[1] http://zammad/#ticket/zoom/473

"

I searched the Documentation in zammad.org for Possible Tags I can insert to the Mail Body, but i can't find any overview about that and therefore no Solution for my Problem.

Would be glad to get a complete overview about possible content Strings. If not possible a direct Solution for my Problem would be nice.

Thanks a lot!

J. Müller

Edit:
After Reading #800 I tried over and over to recreate my failure. I think the Trigger for sendig public Notes is not possible while closing the Ticket. If done this way the Trigger sends the "closed-Notification" as Article.body. Is there a workaround to get the actual Public Note sent instead of the Closing Notification?

@martini
Copy link
Collaborator

martini commented Mar 31, 2017

@AdiosOnline currently only "#{article.body}" is supported which is the last article of an ticket.

You looking for something like:

#{ticket.article_customer_last.body}
#{ticket.article_system_last.body}
#{ticket.article_agent_last.body}

?

Or, what do your mean with "public notes"?

@AdiosOnline
Copy link
Author

Hi @martini ,

Thnaks for your feedback.

That would be what I am looking for, but when i put it into a Trigger, the Email content look like
Ihre Anfrage (Ticket#87502): (TEst) wurde vom Support Team bearbeitet.

Ihr Agent weist auf folgendes hin:
#{ticket.article_agent_last / no such method}

Für weitere Informationen klicken auf den Nachfolgenden Link

Which bodys can be used in Triggers?

Thanks

@martini
Copy link
Collaborator

martini commented Mar 31, 2017

Which bodys can be used in Triggers?

Currently just "article.body" which is the latest article. -> So we need to add additional names to have them accessible via placeholder tags.

I have an change to the last list, how about this possibilities to access the last/first article by sender type?

#{ticket.articles_customer.last.body}
#{ticket.articles_system.last.body}
#{ticket.articles_agent.last.body}

#{ticket.articles_customer.first.body}
#{ticket.articles_system.first.body}
#{ticket.articles_agent.first.body}

Feedback is welcome!

@AdiosOnline
Copy link
Author

Hi @martini ,

I think we talk about different things. What I need is an Element to place the last Article Body of a Public Note into a Email.
image

The Placeholders you posted seems not working on sent Emails.
image

The working Quote is not working when the Ticket gets closed with the note. When we close the Ticket with the public Article, the sent Email looks like
image
and its content is the "Your case is closed" Trigger Mail:
image

i hope we get it working on this way.. Thanks for your further Feedback

@martini
Copy link
Collaborator

martini commented Mar 31, 2017

The Placeholders you posted seems not working on sent Emails.

Thanks correct. I'm talking about, what placeholder you would need - we need to implement them. :)

-> I just want to clarify what you needs is (to do not work/implementation several times).

@AdiosOnline
Copy link
Author

AdiosOnline commented Mar 31, 2017

I need a Placeholder that send the Last Article (Note!!) even if the Ticket gets closed. Can yo reproduce my Situation and know why the #{article.body} is not working every time for me? Or are the Triggers above "Incompatible" to each other?

@martini
Copy link
Collaborator

martini commented Mar 31, 2017

Or are the Triggers above "Incompatible" to each other?

One more question, how many triggers do you have (and with which options)?

Background: Indeed I think we are talking from different things. I want to setup you use case to see what's going wrong.

@AdiosOnline
Copy link
Author

hi @martini ,
sorry for my late response.

My active Triggers are the both from above, and these:
image

image
image
image

@AdiosOnline
Copy link
Author

AdiosOnline commented Apr 1, 2017

We could set up a Remote Session on monday if it's easier for you. Have a nice Weekend.

@AdiosOnline
Copy link
Author

Hi @martini ,

did you recreate my error? Anything new about a solution?

@rlue
Copy link
Contributor

rlue commented May 25, 2018

Currently just "article.body" which is the latest article.

I might be mistaken, but if I understand the issue correctly, I believe that 5dd699c (written for #1543) fixes this. Previously, the trigger would use ticket.articles.last for the email template; after this commit, it uses the article that originally fired the trigger in the first place.

@thorsteneckel
Copy link
Contributor

@MrGeneration can you please check if this is actually resolved as @rlue pointed out?

@MrGeneration MrGeneration self-assigned this Jul 12, 2019
@MrGeneration
Copy link
Member

I could verify that the current Zammad-Version does take the correct article-body.
For this I had a second trigger that fired right before the other trigger which would add a private note.

I'll be closing this. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants