Gateway Events: Tag Change

[nicholas.gutt]

I am building a tag provider which will synchronize to a SQL data model. UDT instances will be created dynamically when valid entries are made into the data model. The tag provider will perform different database operations using Gateway Event Tag Change scripts.

As of now there is one way to batch tag paths which will trigger a Gateway Event/Tag Change script. My understanding is we can use a '*' at the end of a path only.

Since I am scripting UDT instance creation and those instances could have predictable names like 0001-9999 I had a thought of adding a bunch of tag paths to the tag change script that do not exist, yet. Once the instance creation script creates an instance of that name the gateway event tag change will just work instead of manually adding instances to the list each time one is created.

I have 2 questions:
Does this make sense?
If so is it a bad idea?

I did a test and the gateway does not complain outside of the diagnostics box where the tag paths are setup.

[dkhayes117]

Give an example of a full tag path in this scenario.

[pturmel]

This is one of the situations where I recommend the combination of tag valueChange events that delegate to a queue drained by one or more timer events. As described here:

Java concurrent queue for tag change scripts

Continuing the discussion from [SOLVED] Are tag Value Changed scripts running asynchronously?: We've got code in our standard library that I need to log a value change on a tag and then associate various data points with that value change. The value is located in a UDT, and because this is part of our "standard" library we use for our customers, the number of tags is variable and quite possibly numerous so having a gateway tag event script isn't feasible for this solution. I was reading up on …

[nicholas.gutt]

Thank you. I will give queueUtil.py a go.