Salesforce

General - Configuration File Flags (Magic xpi 4.5)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

General – Configuration File Flags (Magic xpi 4.5)

This table describes other flags that can be edited in the ifs.ini file.

Flag

Definition

DisableSecurity=

This flag controls security settings:

N (default): Security is enabled.

Y: All security options configured in the Magic xpi Studio are cancelled.

Use this flag in a testing environment, where external access to the environment is blocked, bypassing the internal Magic xpi security mechanism and facilitating faster flow runs.

StepRetryLimit=

This flag determines the number of times that the Magic xpi Server will retry to execute a step when the Error Policy is set to Retry.

StepRetryClearError=

If you have a step with the Error Policy set to Retry and the limit defined in the StepRetryLimit flag is reached without the Magic xpi Server executing the step, the last error is saved in the c.sys.ErrorCode context variable.

This flag controls whether or not the last error will be cleared from the c.sys.ErrorCode variable.

N (default): The last error will not be cleared.

Y: The last error will be cleared.

If the flag does not exist, the default value is N.

Since version: 4.5

StepRetryDelayTnSec=

If you have a step with the Error Policy set to Retry, the Magic xpi Server will attempt to execute the step again if an error occurs.

This flag controls the delay between retries.

You should set a value greater than 0 expressed in tenths of seconds (10=1 second). An entry of 0 or less means that there will be no delay.

Since version: 4.5

RuntimeVariableTypeValidation=

This flag determines whether Magic xpi checks if the default values of its variables are valid. The flag's default value is Y. To increase performance, you can set this flag to N.

CleanTemp=

This flag is used to determine whether you want to clean the <main Magic xpi folder>\temp folder when the server starts. Setting the flag as Y enables this feature. The default value is N.

JMSStartupConnectionFailurePolicy=

When inter-server communication is facilitated through JMS, this flag determines whether the server should try to reestablish a connection if the prior connection is terminated. You can choose from the following options:

  • Retry (default)

  • Ignore

  • None

FlowTimeoutGraceTime=

This flag determines the length of time (in seconds) that the mgxpiserver.exe will wait after the end of the flow timeout in order to terminate the relevant worker threads that serve the same Root FSIDs.

If the flow is running and the timeout has passed, the flow (not the worker) will be terminated once it finishes its current step, even if the grace time has not yet elapsed. However, if the flow is stuck on a specific step, the full grace time will elapse before the worker is terminated.

It is a best practice to set the FlowTimeoutGraceTime flag in the ifs.ini file per a machine where a project is executed, which can vary, for example, from a strong machine to a weak machine. This can be used as an additional offset for the other timeout you can define for a flow.

The FlowTimeoutGraceTime is taken into account only if the flow timeout is not zero.

The default value (in seconds) is 300.

For additional information about flow timeout policy, click here.

Since version: 4.0a

Reference
Attachment 
Attachment