It would be great to have the ability to allow for tasks to be setup that have filters that are responsive to changes made to underlying tags instead of only utilising the rules that were applied at the start of a recording.
For instance, currently the process is this.
- Create Filter (With a set of tags and CSDL rules for a source)
- Create a Recording/Task to capture and store the interactions.
Now if I make a change to a set of tags within a filter, these changes are not picked up until a new recording is made.
In addition, if I create a tag template and add in one or more new tags, that tag template is now assigned a new tag id.
All existing running tasks will use the old tag template and for them to access the new tag template now (with a new id) I have to manually go through all existing recordings that utilise this tag template and update the tag id accordingly. This means a stop/recreate of a recording in our case.
It would be nice if the following was true.
When you create a filter, have the ability to specify a tag template as a “dynamic” template.
Maybe something like **!**tags “abcdefghijklmnop1234567abcd” (note the ! char to specify the “dynamic type”.
What this means is that whenever I make a change to that tag filter, any existing filters that are using it will automatically be notified and pick up the change. In our case, this would save a lot of time of having to “Restart” tasks for when tag templates are changed. (And yes in our case, we are always adding to these tag templates)