Activity for DC
-
DC posted a comment on discussion Help
Andreas, you are a life saver. The new article with screenshots is exactly what I needed to help. I did not have the WorkflowsRef set to ref=any. After that I was able to go back to the defaults and get notifications working. Thank you for taking the time to explain out and submit a new article to help. I greatly appreciate it.
-
duplicated the post.
-
I hear you, but I will say again, obviously I am being dense. What is the purpose of the notification settings on the job options itself if they don't work? In the demo (which I was able to get in to, thank you), you have a job resource for "eMailOnFailure", but that is inaccessible to see the actual settings of it. I apologize, but this was so easy in JobScheduler V1 and I just feel like something is off in V2 here. 100% my fault.
-
I hear you, but I will say again, obviously I am being dense. What is the purpose of the notification settings on the job options itself if they don't work? In the demo (which I was able to get in to, thank you), you have a job resource for "eMailOnFailure", but that is inaccessible to see the actual settings of it. I apologize, but this was so easy in JobScheduler V1 and I just feel like something is off in V2 here. 100% my fault.
-
Unfortunately I can't access the online demo, and the URL (https://kb.sos-berlin.com/display/PKB/JS7+-+Online+Demo+-+Folder+-+12_Notification) doesn't actually have the setup listed. The download for demos also doesn't include the 12th chapter for examples. In JobScheduler this was easy to set in the JOE, but I am on the struggle bus with JS7 here. I have imported the defaults and set them. The workflow has the job resources set. The job itself has notifications set to success/error and a to: set....
-
Applied the patch from https://sourceforge.net/p/jobscheduler/bugs/140/ and appears to be good again. Thanks!
-
That appeared to fix it for me. I'll continue to monitor. Thanks!
-
Seeing the same issue coming from 1.12.5 to 1.12.7.
-
Rebuilt my servers because I thought I had broke something, but seeing the same issue going from 1.12.5 to 1.12.7.
1
