Durée de conservation des commandes

-- HikaShop version -- : 4.2.2
-- Joomla version -- : 3.9.12
-- PHP version -- : 7.2.24
-- Browser(s) name and version -- : firefox 70.0.1

Hello,
Is there a possibility to assign a maximum lifetime to the orderss?
Under the DGMP, it would be convenient to be able to automate the task.

Thank you in advance

Bonjour,
Y a t il une possibilités d'assigner une durée de vie maximum aux commandes?
Dans le cadre de la RGPD, ce serait pratique de pouvoir automatiser la tache.

Merci d'avance

Hi,

Yes.
You can create a mass action like this:
monosnap.com/file/RP7UGrLXFLqod8yPK3UqFZq4KlyqNK
where X is to be replaced by the number of seconds of life you want to allow orders.
Make sure that the cron task is setup and working first:
www.hikashop.com/support/documentation/5...ashop-cron-task.html

Thank you!
I had started looking at mass actions but I wouldn't have had the idea to express time in seconds!

Just a question : why order_invoice_created < {time}-X instead of order_invoice_created > {time}-X

That seems not intuitive

For cron task, no problem !

Thanks again!

Hi,
Just another question regarding cron task ans mass actions.
I have created a cron task on my server and a mass action for orders on my site ->ok

But I want to create others mass actions regarging prices but I dont want to automate them.

Prices change regarding price of gold, so, this mass action has to be done manually after update of values.

So, does all the mass action be triggered by the same cron task ?

Regards
Patrick

Hi,

1. order_invoice_created is the number of seconds since 01/01/1970 up to the time the order was confirmed.
{time}-X is the the number of seconds since 01/01/1970 up to now minus a number of seconds.
So you want the orders older than {time}-X , hence the order_invoice_created<{time}-X

2. The cron task you configure will trigger all the plugins and the mass action process every 15 minutes (or something else based on how you configured your cron task on your server).
Then, each plugin (and the mass action process for each mass action) will check if it needs to run or not.
So if the mass action is configured to run every minute, and that the cron task triggers every 15 minutes, the mass action will run every 15 minutes.
If the mass action is configured to run every day, and the cron task triggers every 15 minutes, the mass action will run once every day.
And if you don't set any trigger to the mass action, then it won't be triggered by the cron task at all and you'll have to click on the "process" button to trigger it manually.
Several mass actions can potentially be triggered at the same time at some point, but that's not necessarily the case. It really depends on how you configure them.

Thank you for your explanations !
All is clear now.

Regards,
Patrick