Reply posted on December 2, 2019 by DivyaG93
Hi Aditya Menda, Thanks for your Response ...But is there any possible way to solve it?
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
This week we recognize Cloe Walker as our Participant of the Week! Cloe is using the PSC in an effective manner by actively driving their discussions forward and acknowledging the community for the responses received; thus, building successful solutions. Hope to see you around and Congratulations!
Update from SR- Step to resolve the issue- "Go into the OpenSpan.Runtime.exe properties and modify the high DPI settings " Thanks.
Hi Tom, Can we pass the table data (output as DataTable) from robotic automation to Pega application? If yes, what are the options and how to do? Thanks,
Permissions on the Packages directory needed to be updated to make it 'writeable'. Thanks
Here's a quick example you might use to give you some ideas. For this though, it will be much more efficient to do in C# or with a third-party library.
We resolved this by launching the Robot Runtime Engine directly (C:\Program Files (x86)\Pegasystems\Pega Robot Runtime\OpenSpan.Runtime). By default, the 19.1 Pega Robotic Automation Installer created a shortcut to "C:\Program Files (x86)...
No. Studio is required to publish package metadata to Robot Manager. The package itself gets uploaded to the package server and not actually into Robot Manager.
I believe your issue is with the automation. It seems as though it is corrupted. I would recreate the automation and delete it from your existing solution. It must have changed which left something behind that is not valid. If you do have your code...
Please wait while we search for PDN content that suits your question.