Hey..

I checked the help file.. and it says it all!

Once a Job is compiled (a feature only available in WinAutomation Pro), it exists as a standalone executable file (as "name".exe). Since it is standalone, it has nothing to do with WinAutomation any more, and therefore the Service won't be able to trigger the compiled Job (only). Thus when a job is converted to EXE all Triggers associated with the Job are ignored.

 Hi Samantha, 

thanks for your reply.  It's disappointing and this fact is not mentioned here:

http://www.winautomation.com/features/automation-j...

So to get the job to run on my other PC I have to either:

1. run it from Windows scheduler

2. install Winautomation on the other PC and not run it as an exe.

Tony

Well, the thing is that Windows' executables in general, cannot have any scheduling information "attached". However, I have used a workaround in the past:

- I have created a job that contained an endless loop
- Then with a conditional inside the loop I determined if I wanted to run it at the specific time
- I also added a "Wait" action at the end of the loop so that the job would check the time at predefined intervals (in my case 30 minutes = 1800 seconds)

that's a clever idea.  Does the job consume any resources while it's sitting there in the endless loop?

Samantha??

Im confused. If we create a job that uses TRIGGERS and we create a stand alone EXE

i understand that these TRIGGERS will not be in the compiled job as theyre outside of winautomation.

But will they, in NEAR future, release a compiled DLL/sevice module , so that if we give the JOB to one of our staff, they can run it???

As it stands some of my jobs i made are useless as they NEED the triggers to run on a different machine, WITHOUT having to install winautomation.

How can this be accomplised?

I have a job, and the RECCURING TRIGGER would be fantastic, but alas, it wont work as a standalone as the trigger not included. surely there is a way around this?

Its been a while since an update and was wondering if this could be included somehow as were sort of limited in the EXE we can give to our staff....

Thanks,

Robbie

oh..um, LOL...this is a support question i guess, but you seem to be 'connected' in some way...thats a compliment HAHA  :P

Chow!

Hello there,

well.. unfortunately things are a bit more complicated than what you have things configured.

WinAutomation runs a service that communicates with the rest of the system, making sure that the jobs will run when needed (triggers).

When you compile a job to an executable job, you only have a file, that can perform some actions, whenever called.

It is more complicated trying to build a service that will run the jobs, when you can simply buy the standard edition, and have all that functionality you are after.

:)
Samantha