Use Two-Step or Three-Step Commands in PCS 7 V8.2 APL Faceplates

In the described PCS 7 V8.2 project, @APLCommandExecutionSteps selects two- or three-step command execution across APL faceplates. The available evidence does not establish a Siemens-supported per-object override for one critical object. Modifying standard faceplates or switching the global tag dynamically can affect other controls; retain the documented project-wide setting unless a release-matched supported design is confirmed.

What the global setting controls

The PCS 7 V8.2 project described uses the WinCC internal tag @APLCommandExecutionSteps to select two-step or three-step command execution. The source reports this as a project-wide setting affecting all APL faceplates: value 2 applies a command without the extra OK confirmation, while value 3 adds a confirmation step. The archived discussion establishes no Siemens-supported per-object override for one critical process object.

Per-object confirmation is not established

The responder suggested modifying faceplates and their scripts, but did not provide a validated implementation; the original poster decided the risk and effort were not justified. Changing the internal tag dynamically according to user level would still change a project-wide value and could affect other open faceplates. Do not present either technique as a supported per-object feature without documentation for the installed APL release.

Safer engineering decision

Keep the standard project-wide behavior unless an applicable Siemens APL manual documents an instance-level option. 2. For a high-criticality control object, review command authorization, process interlocks, and operating procedure under the site's safety and alarm-management rules. 3. If a bespoke faceplate is considered, treat it as a custom application: document the required behavior, obtain approval, test all command paths and user roles, and confirm upgrade compatibility with Siemens or the system maintainer. 4. Do not silently change the global tag to simulate a per-object rule.

Verification

Check both the tag's configured value and actual behavior on representative APL faceplates after login, project reload, and Runtime restart. If a custom implementation is developed, verify that the extra confirmation applies only to the intended object, that other faceplates preserve their standard behavior, and that user authorization and process interlocks remain effective.

Limitations and Operational Precautions

The ticket identifies PCS 7 V8.2 but not the APL library version or a release-matched Siemens document for per-instance control. The two/three-step behavior and global scope are reported in the thread and corroborated by a related Siemens CEMAT V8 reference manual, not independently by the PCS 7 APL V8.2 faceplate manual. No custom script or faceplate procedure is provided.

Engineer FAQ

Can one PCS 7 V8.2 APL faceplate require an extra confirmation while others do not? The available evidence establishes only a project-wide internal tag, not a supported per-object override.

What does @APLCommandExecutionSteps do in the described project? The thread reports value 2 for immediate execution and value 3 for an additional OK confirmation.

Can I switch the tag according to user authorization? The forum suggested this but provided no validated method; because the tag is project-wide, such switching may affect other faceplates.

Should I modify the standard APL faceplate scripts? Not without a supported design and controlled testing. The thread's responder explicitly cautioned against that approach.

How should a high-criticality object be protected meanwhile? Use the site-approved process interlocks and authorization design; do not rely on a visual confirmation dialog as the only protective measure.

Technical References

CEMAT V8 System Reference Manual, section “Setting the multiple step operation,” documents the global @APLCommandExecutionSteps tag with values 2 and 3 in the CEMAT V8 faceplate context. It does not establish a per-object override for PCS 7 APL V8.2; the large PDF could not be opened through the research tool.
No opened Siemens PCS 7 APL V8.2 reference documenting an instance-specific two/three-step command setting was located.