RE: Task Scheduler and Automating SL
I've found this issue a few times. I still don't really get it.
As I've seen, SL is strictly a 2tier application. The SL client works as a presentation layer only. You can do automation and scheduling, but that means we are talking about a presentation layer on steroids, not really a separated layer where you can instantiate business objects.
Operating system wise, this means you got to have a Window station to really make things work. The internal messaging between SL executables need this. No Window station, no message pass through. The web apps manage to bypass this
As a workaround, I setup a separated Application Server to perform the actual tasks. You can still trigger actions through the Application Server task queue. The triggering process can be scheduled and doesn't need the Window Station, but the actual Application Server session does.
Each task under SL could be classified such as:
- Doesn't require a Window Station (i.e.: App Server automation, Web service).
- Requires Window station, but could be minimized or stand by (i.e.: Transaction Import on GL journal, PATRN).
- Requires a Window station with an active Window. (i.e.: Transaction Import on Purchase Orders)
Screen customization may change some screens behavior on this.
As a weird suggestion, watch Inception. Transaction Import, scheduling and automation are all trying to work with a slept SL client and make it work as if an actual user is interacting with it. Sometimes you need to trigger a screen to call on another screen... that's second level dreaming.