Skip to Content
0
Former Member
Apr 21, 2008 at 12:06 PM

ChaRM - reusing action for sending mail

240 Views

Hi Folks!

I am trying to set up automatic email notification on status change.

In a nutshell:

On the one hand I would like to use one action for sending a mail several times each time a certain status is reached but on the other hand would like to prevent the action to be performed several times when the save button is pressed AND the status did not change.

In detail:

The particularity is that I want to reuse the action in case a certain status is reached a second or a third time.

For instance:

- Developer sets document from "in developement" to "to be tested"

- email is sent to Tester (in background)

- Tester perfoms tests and sets document from "to be tested" back to "in developement"

- Developer corrects his coding and sets status to "to be tested".

- email is sent to Tester (again)

Basically everything works fine but to get this working I had to set action time to "processing when saving document" and action merging to "Set Highest Number of Processed Actions" --> "Number of Processed Actions: umlimited"

This allows me to reuse the action for sending the mail to the Tester over and over again when the specified status is reached but also has the side effect that the Tester gets a mail each time the Developer presses the save button within this status.

(Developer uses action to set status to "to be tested" -> save button -> mail is sent -> Developer adds some information for the Tester -> save button -> mail is sent again -> Developer exits transaction crmd_order -> system asks if the transaction should be saved -> yes -> mail is sent again)

If I set action merge to "Max. 1 Action for Each Action Definition" the save-button-problem is solved but I cannot reuse the action.

I also tried to use immediate processing but this doesn't seem to solve the problem either.

What I also tried:

At last I tried to use one action for sending mail with option "delete after processing", no schedule condition and start condition when "to be tested" is reached.

And another one with option "delete after processing", schedule condition: status "to be tested", start condition: "in developement".

But it looks like schedule conditions are not working as I would like them to when using automatic actions. Obviously the action is marked as processed after schedule condition is reached. So it gets deleted by the system and would never get to the point where the start condition is met.

I hope someone has a solution. Maybe I am missing something here and do not recognize it yet.

To all of you who made it to the end: Thanks a lot in advance 😉

Best Regards,

Christian