...
Example of a parameterisation:
Appendix C: Parameter shiftAction
This paragraph gives an explanation about what shiftAction is and how to use it.
...
shiftAction is a parameter than can be passed when launching EVSg.
Using shiftActions ensures that the dates of the tests are within a usable range. Not in the past and not too far in the future.
Because of this the dates of the tests don't need to be manually altered anymore.
...
shift_and_tag ensures that all other dates in the XML-file are adjusted in reference to today's date.
Afterwards it will update the "recorddatetime"-tag.
Suppose that today's day date is :
| Original date | Date after shift_and_tag | |
|---|---|---|
| <recorddatetime> |
|
|
| transaction 1: tomorrow |
|
|
| transaction 2: yesterday |
|
|
| transaction 3: three days from now |
|
|
| Note |
|---|
...
The "recorddatetime"-tag needs to exist in the XML-file prior to executing it, else it will not change the dates according to today's date but it will add a "recorddatetime"-tag. |
no_tag_and_no_shift will not create or update the "recorddatetime"-tag and it will not adjust all other dates according to today's date.*
| Note |
|---|
If a "recorddatetime"-tag already exists in the XML-file and you run EVS with no_tag_and_no_shift, the tag will be removed. |