What would be great, is to be able to filter for exclusionary terms. For example:
Name: != 'SETUP' (This would omit any name that 'SETUP' exists in)
Of course, we can filter all day long in the Excel Export, but the need for this, goes along with the hyperlinked interactive result set, that allows you to manage the object referenced from the list.
Case in point: I have about 100 workflows, with 2 Bursts in each folder, One is the 'SETUP' Burst that generates the recipient list from BOBJ's CMS and the other is the actual "MAIN" Burst for the Job.
Understanding that a good workaround is to overload the Description of Objects to have terms embedded to query 'for' later, (such as 'MAIN JOB BURST' as I have done already, but putting this out there to spark juices for improvement of an already invaluable new functionality that is proving "super useful". :)
1 Comment
Bryan Baca
said
9 months ago
Thanks for the input. At this time, we have no plans to implement this feature.
Kirc Breden
What would be great, is to be able to filter for exclusionary terms. For example:
Name: != 'SETUP' (This would omit any name that 'SETUP' exists in)
Of course, we can filter all day long in the Excel Export, but the need for this, goes along with the hyperlinked interactive result set, that allows you to manage the object referenced from the list.
Case in point: I have about 100 workflows, with 2 Bursts in each folder, One is the 'SETUP' Burst that generates the recipient list from BOBJ's CMS and the other is the actual "MAIN" Burst for the Job.
Understanding that a good workaround is to overload the Description of Objects to have terms embedded to query 'for' later, (such as 'MAIN JOB BURST' as I have done already, but putting this out there to spark juices for improvement of an already invaluable new functionality that is proving "super useful". :)