--- title: "Standard parameters for all actions" description: "The general parameters available on most SyncTool actions: step control, error handling, timeout, etc." url: https://support.sapera.io/en/articles/648-standard-parameters-for-all-actions collection: "SyncTool" updated: 2026-10-04 language: en alternates: [da] --- # Standard parameters for all actions The general parameters available on most SyncTool actions: step control, error handling, timeout, etc. Most SyncTool actions share a set of general parameters that control the step itself — independently of what the action otherwise does. They are empty (off) by default. - **Disable step** (DisableStep): turns the step off without removing it. When true, the step is skipped during a run. - **E-mail errors** (EmailErrors): if the step fails, the error message is sent by e-mail (requires e-mail sending to be configured). Sent only once per run to avoid spam. - **Ignore errors** (IgnoreErrors): let the run continue to the next step even if this step fails, instead of stopping the whole job. - **Command timeout** (CommandTimeout): maximum time in seconds a database command may run before it is aborted. Empty = the server default. - **Succeed even without input file** (SucceedEvenIfNoInputFile): for file imports — if the input file is missing, let the step succeed (skip it) instead of failing. - **Debug enabled** (DebugEnabled): writes extra detailed log output for troubleshooting. - **Process all in one batch** (ProcessAllInOneBatch): processes all rows in a single batch instead of smaller chunks. Can be faster for small data volumes. - **CultureName** (CultureName): the culture/language (e.g. da-DK) that controls how number and date formats are interpreted on export. ## Date tokens in parameter values Every parameter field understands a small set of tokens that are translated into today's value when the step runs. That lets one setup behave differently depending on the day it runs — without you maintaining a copy of the setup for every variant.

Token

Becomes

<IsWeekday:Sunday>

true on Sundays, otherwise false. Several days: <IsWeekday:Saturday,Sunday>

<IsDayOfMonth:1>

true on the 1st of the month, otherwise false. Several dates: <IsDayOfMonth:1,15>

<Weekday>

The name of the day, e.g. Sunday

<Today>

Today's date, e.g. 2026-08-23. Custom format: <Today:ddMMyy>

Type the token straight into the value field — including in fields that expect true/false. Set **Disable step** (DisableStep) to , for example, and the step is skipped at weekends and runs Monday to Friday. Tokens also work inside a longer text, so a file name can be export\_.csv and carry today's date. Good to know: - Day names are written in English (Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday) regardless of the language you use. Capitalisation and spaces make no difference, so works too. - The token is translated the moment the step starts. A run that begins on Saturday evening and continues past midnight therefore counts as Saturday all the way through — every step in the same run gets the same answer. - The day changes at midnight in the server's own time. - A misspelt day name gives false — never true. A typo therefore switches the feature off instead of turning it on every day. Check the spelling if a weekly run never happens. - If you have created a global parameter with the same name as a token, your own parameter is the one that applies. **** is true on every weekday except those listed (here Monday to Friday). **** is true on every day of the month except those listed.