@Reeza I looked at the post and I am trying to determine where it fits in to what I am doing. Is it in the code inside the EG process flow? Let me take a step back, I may have confused the issue. So, when I created the process flow, I scheduled it based on the schedule creator inside EG. It automatically generates a .vbs file and adds it to the windows scheduler to run. Windows scheduler runs the .vbs file directly. There is no .cmd file involved in that scenario. In my case, I don't use the task scheduler to kick of a .vbs file for a process, I use a .cmd file to kick it off. @echo off
wscript "\\pncbank.com\corp\NECD\Group\PFS\mortgage\MSR Reporting\Automation\SAS EG Project Automation\FHLMCDaily.vbs" If you run the process flow manually with EG open and you have a prompt that was created in prompt manager, once the process gets to the task calling for the prompt, I enter a date and that is passed to the variable in the code and it completes. I am wanting that prompt to pop for the user if the .vbs file is run without EG being open, regardless of how the .vbs file is being executed. Maybe this article can do that but I am having trouble determining how to apply it.
... View more