Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


interlinkONE
2015-03-10T15:20:04Z
It's probably not feasible but it'd be helpful if variables were processed in Job and/or Task Names. We have 100s of identical jobs for varying customers. We currently use groups, which are great!, and parse them as "Customer (DBA / config / other)".

As a result we end up with tons of identical results in the VisualCron Log. We have email notifications configured to return us the relevant data we need so this isn't a high priority item. Just would be nice to have.

thanks for the superb product
Sponsor
Forum information
Support
2015-03-10T15:39:57Z
What about using Job Variables instead of User Variables?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
interlinkONE
2015-03-10T15:48:20Z
Right!

{REGEX(MatchGetGroup|{JOB(Active|Group)}|\((.*?)\)|1)} doesn't seem to parse when used in the Job Name. It seems to just be used as a literal string when used in the Job or Task names
Scroll to Top