Good afternoon,
Good afternoon,
Hi Maike Mak,
this is how it works on my system:
1. the target module is emails
2. the start event runs on "new records only" and the criteria is Email Status is not "draft"
3. a wait event follows with a duration of 1 minute to let other workflows change teams or whatever on the email (important as several after save automatisations are running on case email import and are affecting criterias below)
4. an exclusive gateway follows checking for "Email created by is not the assigned user" AND "Case ID is not NULL"
5. if the criteria match, send your email to the assigned to of the case via message event, elsewise quit the process
Done :-)
Bests
Björn Canales Pfisterer
Technical Support Manager
provalida GmbH
--
support ( at ) provalida.de
Great summary - The Wait Event is critical as is the New Records as it it refers to a new record in the Emails module
Great summary - The Wait Event is critical as is the New Records as it it refers to a new record in the Emails module
Indeed, once the email is saved sugar goes ahead and creates the ticket and runs the after save hook to create the Ticket ID, also case assignment is running after save. This takes some time. Therefore we need the wait event until the case ID is available :-)