User manual will soon include how to use Cloned environments management
As a summary :
- on parameters, define limits for each profile and frequency for generation (generation is not immediate, it is scheduled to be sure to control performance on production)
- on Cloned environments management, you have the list of existing cloned environment (empty at start-up) : click on + to add one
- if cron is running, enrironnement will be created (in background) at the expected time
- on Cloned environments management, on the list of existing cloned environment : you'll have a link to access the environment

Thanks for your explanation.

I attached some screenshots, while it seems that I don't have the option to add a new environment.
Also Icons for menu-points seems missing.

I downloaded and installed on monday morning - has there been a new zip-file of the version since then?

Best regards

Hi,
Please post screenshots in English, it will help us 😉
Also clean your browser cache : some icons are missing because of not updated cache, so possibily javascript is also not up to date.
Also check in parameters that you have rights to create environments (depending on your profile)

Thanks - you were right! Clearing Cache did the job *banghaedagainstwall*

Hello,
I would test this new function and i have this error:
2019-09-20 11:15:04.104 ===== TRACE ===== Bruno Villedieu - Début de création de l'environnement
2019-09-20 11:15:04.104 ** ERROR ** [V8.2.0] ERROR **
2019-09-20 11:15:04.104 ** ERROR ** [V8.2.0] on file '/var/www/html/model/DataCloning.php' at line (480)
2019-09-20 11:15:04.104 ** ERROR ** [V8.2.0] cause = mkdir(): Permission denied
2019-09-20 11:15:04.104 ** ERROR ***** [V8.2.0] Erreur simulation - Impossible de créer un répertoire cible

What is the parent directory for chenge rules acces ?
Thanks

php user must have write access on directory projeqtor/simulation

Very thanks for your answers. for feedback the directory is not created during the upgrade without error.

or feedback the directory is not created during the upgrade without error.

This is a deployment issue.
Will be fixed on next patch.
Thanks for pointing out.

it's normal thanks for you for your excellent work