Wildcards in the middle of Tag Change paths: Intentional in 8.3.4?

Ignition
,
1

Hello everyone!

I'm developing a custom device driver module and trying to make a tag change script scalable to watch the same tag across multiple devices using a path like this:

[MyDevicesProvider]*/ConfirmHandshake/Req

In my researches, the * wildcard should only work at the end of the path (see topic below).

I tested this on 8.3.3 and it indeed didn't work. However, testing the exact same path on 8.3.4, it works perfectly!

My main question is: Is this change in 8.3.4 an intended feature that I can rely on for future releases, or is it an accidental side effect that might get patched?

Context & Alternatives: If this wildcard behavior isn't reliable, I'll need a different approach for my module to notify projects of device events. I'm considering:

  1. Gateway Messaging: Broadcasting a message that projects can listen to.

  2. Centralized Triggers Folder: Creating a specific folder to use the wildcard: [MyDevicesProvider]Triggers/*

  3. Module Event Scripts: Exposing a custom Event Script (like Sepasoft). I find this the most elegant approach, but I'm afraid it will add too much complexity to the module development process.

Any insights on the wildcard reliability or advice on the module architecture will be highly appreciated!

2

This is intentional, there's an open ticket for the docs team to update the docs and examples.

3

Thanks for the fast confirmation, Kevin!