DecoupagePlanning batch
The DecoupagePlanning batch is used to divide scheduled items of more than one day into several one-day items. This breakdown is only done on scheduled items for which the start date is before today's date.

1 | Go to Tools > Setup, then open Batches > Batch creation and modification. |
A results screen opens to display the list of existing batches.
2 | In the results screen, click on |
3 | In the New Batch screen, fill in the batch's Code and Label, then select DecoupagePlanning from the drop-down list of the Batch template field. |
Note
The code must be unique for each batch, all companies combined.
4 | Specify the batch parameters. For details about these parameters, refer to Setting up the batch. |
5 | Save the batch. |
When the batch is started, all the scheduled items for which the start date is before today's date are analyzed. The scheduled items divided by the batch are the following:
- Schedules with a duration of strictly more than one day
- Schedules that are not done (not transferred into timesheets)
- Schedules on actual resources (not on generic resources)
The corresponding scheduled items are therefore divided into several one-day items.
Example
For a scheduled item of 2 days on Monday / Tuesday, the batch will divide this item into 2 one-day items: one day on Monday and one day on Tuesday.
For a scheduled item of 1.5 day on Monday afternoon and Tuesday, the batch will divide this item into 2 items: a half day on Monday and one day on Tuesday.

Code | Description | Type | Required |
---|---|---|---|
BATCH_DEBUG_PARAMS
|
When the parameter is set to True, details about the batch parameters are displayed in the logs. | Boolean | No |
BATCH_LOG_CONSOLE
|
When the parameter is set to True, logs are displayed in the console. | Boolean | No |
BATCH_LOG_FILE
|
Name of the directory where the log file is saved. |
String Ex: |
No |
BATCH_LOG_ID
|
Log file ID. | String | No |
BATCH_LOG_LEVEL
|
Log level. |
String Ex: LOG;WARN |
No |
BATCH_MAIL
|
Email address of the logs' recipient in case of an error. |
String Ex: support@akuiteo.com |
Yes |
BATCH_MAIL_ADV
|
Email address of the recipient for the Sales Administration-type alert. At the end of the batch, a single email is sent, containing the list of scheduled items that were processed. |
String | No |
BATCH_MAIL_CC
|
Email address of the logs' cc recipient in case of an error. |
String Ex: support@akuiteo.com |
No |
BATCH_MAIL_CCI
|
Email address of the logs' bcc recipient in case of an error. |
String Ex: support@akuiteo.com |
No |
BATCH_MAIL_FROM
|
Email address of the logs' sender in case of an error. |
String Ex: support@akuiteo.com |
No |
BATCH_MAIL_REPLY_TO
|
Email address to use when answering the email sent with the logs. |
String Ex: support@akuiteo.com |
No |
BATCH_PWD
|
Password of the user who starts the batch. This password must be linked to the BATCH_USER specified. |
String | Yes |
BATCH_USER
|
Login of the user who starts the batch. | String | Yes |
CODE_ETABLISSEMENT
|
Codes of the entities to be included in the batch process. Each code must be separated by a slash /. If no entity code is specified, all entities are taken into account by the batch. |
String Ex: ENT1/ENT2/ENT3 |
No |
MAIL_ADV
|
When the parameter is set to True, an email with all the error logs will be sent to the email address specified in the |
Boolean |
No |