Customization

Add auto - as a prefix to these attributes. For example, auto-sync.

sync

It is of boolean type and can be added only to the argument tag. This attribute determines whether API calls should be executed sequentially or concurrently during automation.

• true: When set to true, API calls will be executed one after another in a sequential manner. This ensures that each API request is completed before the next one starts. It is useful when the execution order is crucial, or when subsequent calls depend on the results of previous ones.

• false: When set to false, API calls will be executed concurrently, allowing multiple API requests to run simultaneously. This is beneficial when the API calls are independent of each other and faster execution is preferred, as it reduces the overall time taken for the automation process.

dependency

It is of boolean type and can be added only to the argument tag. This attribute indicates which argument must be considered as dependencies during the resource loading process.

• true: When set to true, this attribute ensures that the specified arguments are treated as dependencies. This means that the resource loading process will wait for these arguments, which is essential for scenarios where certain operations rely on the results of others.

• false: When set to false, the specified arguments are not treated as dependencies. The resource can load without waiting for these arguments, which can speed up the process.

skip-execution

It is of boolean type and can be added to the operation tag. This attribute allows you to skip the execution of the specified operation during automation.

• true: When set to true, the specified operation will be skipped entirely during the automation process. This is useful for scenarios where the operation is no longer relevant or needed, preventing unnecessary execution and saving time.

• false: When set to false, the operation will be executed as part of the automation sequence. This is the default behavior and is suitable for scenarios where the operation is essential for the overall process.

self

It is of boolean type and can be added to the operation tag. This attribute enables you to skip self-loading for the specified operation.

• true: When set to true, this attribute prevents the operation from self-loading. This is beneficial in cases where the operation should not trigger its own execution, thus avoiding potential loops or redundant processes.

• false: When set to false, the operation is allowed to self-load as part of its execution. This is useful when the operation’s self-loading behavior is required for proper functioning.

skip-call-back

It is of boolean type and can be added to the url tag. This attribute allows you to skip callback verification for the specified operation.

• true: When set to true, callback verification for the operation will be skipped. This may be used when the callback is not essential for the process, streamlining the automation by eliminating unnecessary checks.

• false: When set to false, callback verification will be performed as usual. This is important for ensuring that the operation’s results are verified through the callback, maintaining integrity in the automation process.

call-back

It is of boolean type and can be added to the operation tag. This attribute marks an operation that should be used for callback verification.

• true: When set to true, the operation will be marked for callback verification. This means that the results of this operation will be checked through the callback mechanism, ensuring the expected behavior is confirmed.

• false: When set to false, the operation will not be marked for callback verification, meaning that the results will not undergo callback checks. This can be appropriate for operations where callback verification is not necessary or desired.

skip-verify

It is of boolean type and can be added to the URL tag. This attribute allows you to skip verification for the specified URL.

• true: When set to true, the callback verification will be skipped.

• false: When set to false, the callback verification will not be skipped. This is the default behavior