Hi,
After the concept of scope, here is another one that took a lot of energy as part of PcVue 12.

Support for SCADA Basic verbs and modes is widely improved in version 12, as well as the corresponding documentation.

This note is quite long, just in case you do not have time to read it all, I start with a special tribute and a big thank you to everyone who spent time on this.
It should have been done for years. With a re-designed WebVue it was now or never. It proved to be as hard and time-consuming as expected, and it has been achieved because a few of you made a mission to complete it. I am personally convinced it was worth the effort, I hope you will find it helpful and handy.

Step 1 - First things first: What works and what does not work ?
It all started in ... 2017 with tests covering the full list of verbs and modes to establish a check list of bugs, incorrect return codes and other mis-behavior of SCADA Basic instructions when executed in WebVue context.

Step 2 - The next stage took place in 2018: Fix as many mis-behaviors as possible, and ... re-test
By mis-behavior we mean any situation such as:
- The instruction returns a success, but nothing is done
- The instruction returns a failure, but in fact, it works
- The instruction works, but it should not, because it is not applicable to WebVue context, or can even be dangerous for the back end station and therefore should not be executed
At that stage many return codes were reworked, the applicability of some instructions have been defined...

Want examples, here are some:
- Verb SYSTEM mode Login and Logout: By design, they apply to the PcVue environment. In a WebVue context, the only way to login is via the Login page, and Logout can only be done via the WebVue system toolbar. As a consequence, the implementation was changed so that they return a failure and do nothing on the back end station in case they are executed in a WebVue context.
- Verb CAPTION: By design, it applies to the PcVue desktop application, to change the label in the title. And no, you actually DO NOT want a script executed from a WebVue client to change the web back end station's workspace. The implementation was changed so that it returns a failure and do nothing on the back end station in case it is executed in a WebVue context. In the same category, the verb SVKEY, designed to handle the license. Do you really want to affect the web back end license from a WebVue client. The answer is no, and we ensured that a useful error code is returned in this case.
- Many verbs and modes where not working properly and have been improved (fixed...), so that they are effective and return a proper success/failure return code when executed in a WebVue context.
- The verb SESSION was created so that you can retrieve information about the current session context by script. This instruction works properly in all types of contexts, WebVue and PcVue desktop.
- Verbs corresponding to graphic controls that are not supported in WebVue context now all return failure codes if executed in WebVue: CHART, PIE, SELECTOR...
- Some modes of the verb WEBVUE are now considered obsolete (and documented as such), replaced by a verb/mode that is also effective in PcVue desktop context so that you can design generic scripts whatever the execution context: Stuff dealing with session management, session Id retrieval...
- ...

Step 3 - Document all that stuff in an helpful way
Last but not least, support for SCADA Basic used to be documented as part of the WebVue book, with a quite simple list of instructions known as 'not supported'. This was of very limited help to project designers because it was not available as part of the SCADA Basic topics.
As of v12, indications of applicability and support for SCADA Basic verbs and modes in WebVue context is directly within the SCADA Basic documentation, and thus directly accessible when you are in the SCADA Basic editor and press the F1 key.
In each topic dealing with a SCADA Basic verb (the A to Z instruction reference), the general description comprises a generic indication: WebVue support - Yes | No | Partial | Not applicable.
If support is partial, the table of modes now has an additional column indicating for each mode if support in WebVue context is ensured or not.
Want examples, go check the A to Z list :whistle: CAPTION, LOGDISPLAY, MAPDISPLAY, SYSTEM, FILETOBUF... are good examples

In addition, information have been added in many places when the execution in a WebVue context comes with a behavior worth being aware of.
For example, all instructions dealing with:
- Files (FILETOBUF BUFTOFILE, EXPORT...),
- Network resources (EMAIL instruction with its SMTP ServerHost param),
- Computer clock (DATETIMEVALUE...),
- And noticeably the LAN instruction.
Because SCADA Basic instructions executed in a WebVue context are actually executed by the PcVue web back end station, all these resources (filesystem, clock, network resources...) are as seen from the Web back end, and not as seen by the web client.

Want examples, search for the keyword "If executed in a WebVue session context this instruction is processed by the computer that hosts the web back end" in the SCADA Basic help.