Question
Nestle Operational Services Worldwide S.A.
BR
Last activity: 22 Aug 2017 12:52 EDT
SAP Backgorund Automation
Hi everyone!
I'm working in a SAP automation and I have a question: Is possible to run an automation in background task (hidden or minimized)?
The idea is: start the automation using a SAP transaction and allow the user to use the same transaction but out of the automation.
My current problem is: when I start my automation, it is working fine but when I open a new window with the same transaction when the automation still running, the automation is injecting its controllers in that new window making the original window opened by the automation not controlled anymore.
Is there anyone that already faced this topic?
Pegasystems Inc.
US
Nestle Operational Services Worldwide S.A.
BR
Thank you very much for the explanation.
I'll perform some tests here. Any news I'll keep this topic updated.
Nestle Operational Services Worldwide S.A.
BR
I tried to perform some tests as you said but I depend of my SAP Logon be started by my automation.
The reason is: If I opened a window before my automation starts, my SAP Logon is started automatically (its default for each transaction that I open). That way when I'm monitoring all (MonitoAll in StartMethod) my SAP Logon is already opened when my aplication starts to run.
In other words, if I start my transaction before my automation, the injectable controllers can't find a SAP Logon instance once it's already running. But If I let my start method as Start, I face my original issue.
Any tips about it?
You likely need to examine how the "new" window is being launched, and examine your StartMethod and HookChildProcess settings on your adapter to compensate. Some applications only allow one instance of themselves, and Pega Robotics wouldn't change that behavior. If this application can run two instances independently, then you may be able to launch a second one without being hooked by Pega Robotics. Are you using the StartMethod "MonitorAll"? If so, the only way not to hook an instance of that application would be to start it before the adapter was started. Once that adapter is running, all instances will be hooked. If you truly cannot avoid hooking it, then you could potentially "key" the main window and only allow your automations to interact with a specific key.
This might be challenging to assist you with via forums, however if you open an SR with support, I'm sure one of our personnel can assist with this rather easily. If you do open an SR, please post the SR number here for tracking purposes.
The following article will be help you in creating an SR-
You likely need to examine how the "new" window is being launched, and examine your StartMethod and HookChildProcess settings on your adapter to compensate. Some applications only allow one instance of themselves, and Pega Robotics wouldn't change that behavior. If this application can run two instances independently, then you may be able to launch a second one without being hooked by Pega Robotics. Are you using the StartMethod "MonitorAll"? If so, the only way not to hook an instance of that application would be to start it before the adapter was started. Once that adapter is running, all instances will be hooked. If you truly cannot avoid hooking it, then you could potentially "key" the main window and only allow your automations to interact with a specific key.
This might be challenging to assist you with via forums, however if you open an SR with support, I'm sure one of our personnel can assist with this rather easily. If you do open an SR, please post the SR number here for tracking purposes.
The following article will be help you in creating an SR-
My Support Portal explained for Pega Robotic Automation (formerly OpenSpan)