By action 'Lock' in Editor an interlocking condition can be created but is not used in the Runtime.

• Related Articles

• deleting via tree of action or command group with linked intelocking condition can cause strange behaviour of Editor

  Summary when in command group some action has linked interlocking condition and you delete the action or the group via tree then even when the condition formula was empty it can cause memory corruption in Editor. Description when in command group ...

• When you copy command group with an action with invalid interlocking conditions - the new group disappears after project reopen

  Summary In Command processing module you can copy actions from one command group to another. When you copy an action also all linked interlocking conditions are copied. But when in the aim group there are no variables for pasted conditions then: - ...

• Changing the result variable used at an interlocking is not correctly taken over in the runtime after reload

  Summary Changing an interlocking with a "result variable" linked in the editor is not correctly taken over in the runtime after reload, even though the interlocking seems to compile correctly in the editor DescriptionChanging an interlocking with a ...

• Under specific circumstances a new time cannot be created in the Production & Facility Scheduler in the editor and runtime.

  Summary When creating a new time in the Production & Facility Scheduler in the editor or runtime, the new absolute time point cannot be created if the same set time was used before when configuring a relative point of time. Description When creating ...

• Command Processing: no interlocking text when action fails at second stage, while at first stage there was no interlocking yet.

  Summary Command Processing, two-stage action 'command': issue when at first stage (i.e. Select) the interlocking condition is OK, but at second stage (Execute) - not anymore. Then when user press button to execute - the action cancels automatically ...