cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Execute Jobs when cancelling a transaction

Solved
Contributor

Execute Jobs when cancelling a transaction

Hello all,

 

I know that's possible to execute job when dispatching a transaction.

 

But is there a way to execute Jobs when cancelling a transaction ?

 

Regards

Stéphane

Tags (3)
5 Replies
Contributor

Re: Execute Jobs when cancelling a transaction

Hello Stéphane,

 

thank you for your post.

 

Please can you give an example what do you want to do exactly?

 

Salah

Contributor

Re: Execute Jobs when cancelling a transaction

At the creation of some type of object, we create some external temporary files.

We also add a job to delete those files when dispatching.

 

But I also need to be able to delete those temporary files when a user cancel is transaction.

 

 

MEGA

Re: Execute Jobs when cancelling a transaction

Hello Stephane

 

I suppose you need to trigger code when a transaction is abandoned (discarded)

 

I am not aware that such a function is available with MEGA 2009 SP5.

 

As you probably know, you can trigger code in the following situations:

  • RunJobBeforeDispatch: Code executed systematically when dispatching the transaction.
  • RunJobAfterDispatch: Code executed if dispatch is a sucess.
  • RunJobOnFailedDispatch: Code executed if dispatch create an error.

See also:

http://community.mega.com/t5/custom/page/page-id/mega-kb-solution?sid=50120000000mr6CAAQ

Jerome
Contributor

Re: Execute Jobs when cancelling a transaction

Hello Jerome,

 

I am alreday using code triggering when dispatching a transaction.

 

Triggering code when a transaction is discard is excatly what I need.

 

Do you prefer that I open a case for that point because it would be interesting to add this function in a future version of Mega?

 

For the moment I execute the script when a user opens/resumes a transcation.

 

Stephane

 

MEGA

Re: Execute Jobs when cancelling a transaction

Hello Stephane

 

As the expected feature does not exist, it must be handled as a n improvement request

 

It is indeed better to open a case and describe the use case.

By use case, I mean functional description of what would be possible with this feature (what you want to do with it)

 

You can use this form

http://community.mega.com/t5/custom/page/page-id/mega-support-case

 

Jerome