I was wondering if anyone has or knows of a comprehensive list of all the variables, constants, and parameters available for use when building custom tags that incorporate automatic inheritance, etc.

I’ve come across a few that are detailed in the help files, such as:

\Value
\DisplayAddress
Here’s the link I’ve found so far: file:///C:/VTScada_12_0_42/VTSHelp/Content/Scripting/Tasks/pro_TagOptionalVariables.htm?tocpath=Scripting%7CCustom%20Tag%20Types%7CThe%20Tag%20Variables%20Section%7C_2

However, I’ve also seen other parameters scattered across various help topics, like:

\DriverServerListName
\ModiconTypedAddr1Offset
Does anyone have more to add to this list or know where I can find a complete reference? Any help is appreciated!

Thanks!

Listening - would love this too!

Can you create a new tag widget containing a text object and within the text object look at all the linked tag properties available?
I haven’t used it in a while but I thought source debugger could drill down into tag properties too.

Any word from Trihedral?

If you open the Source Debugger and look at your application, you can typically look at any tag type and see most of the properties and methods available. This is a more advanced method but, if you can learn the basics of the source debugger, you will probably find it very helpful to find tag properties.

That isn't really what I am getting what I am getting at.
There are parameter/variables that you can add to a custom type

For example,
\DriverServerListName
If you add a parameter named "DriverServerListName" all child driver tags will inherit the supplied ServerListName based on what is entered into the DriverServerListName parameter of the root context.

i am looking for a comprehensive list of all these parameters that generate automatic inheritance as they are little hidden gems that are scattered though the help files.

Would this be better for me to just submit this as a support ticket? I just thought this would be something some of the super users on here could benefit from.

Understood. I don't believe that there is an extensive list of these but essentially any application property can be defined at a node and will affect any children of the node which use that property.

For those who are reading this and are not aware; application properties defined in the OEM Layer can be overwritten at an application level in the application properties. From there, you can define any properties in a context tag or custom tag type. Doing this will only affect tags calling those properties which are children of the context tag.

A good example of this is using custom Alarm Message Template properties in context tags to change the message delivered by the alarm dialer, for alarms in different areas of the tag tree in an application.

More here: https://www.vtscada.com/help/Content/D_AlarmSystem/Dev_AlarmMsgTemplates.htm

that is another thing i was looking into thanks i will take a peek at it.

Would this work the same way like a Driver Redirect?

I am told that the dev team is currently studying the best way to implement this feature.

i am basically using GetTagList and ModifyTags to accomplish this. It works fine and as excepted but of course this shows the tags as overridden. Could i get put in the right direction on how to handle this like the Polling Driver does to the ScanRate parameter of child tags to show grayed out.

I would assume they are overriding the PEditField\View by monitoring if there is a Polling Driver tag in the scope in the Tag Configuration plugin. That would be my best guess on how the backend is done witch I definitely cannot do.