Posts

RPA Technical Story: Our production BOT system went down

Image
In this technical story, we will be answering the below questions and would understand the problem first before before jumping on the solution What was the issue ? .      In the middle of BOT execution, we saw that system went down and later got disconnected from the server We could not take remote into this BOT runner system and therefore were forced to involve client IT server maintenance team. Server maintenance team performed a restart on the said system and remote connection was restored How this issue occurred ? BOT was executing VbScript on an bulky excel file (rows > 100k) extracted from an ERP system VbScript/Excel calculation caused CPU usage to reach 100% and maxing out of the system resources To prevent further damages, system went down and disconnected itself from server Note:  We were unaware about the impact of high CPU usage on the BOT execution and on the system. Thanks to our client’s serve

Working with EML files in Pega Robotics Solution

Working with EML files in Pega Robotics Solution In my recent RPA project for an insurance & finance major, we caught up with situation where the format for the input found to be different in production environment with respect to the UAT. This deviation was mainly the change of the input file type from MSG to EML. Let’s talk about EML file format; EML is file extension for an email message saved to a file in the MIME RFC 822 standard format by Microsoft Outlook Express as well as some other email programs. It contains email header, subject, body, hyperlinks and attachments etc. MSG is file extension for email message used as default by Microsoft outlook and exchange. It contains email header, subject, sender, body, hyperlinks, attachments etc. Earlier during the development phase, it was only MSG files we received from the source application and we were able to parse it using Microsoft Office Interoperability framework. However during go-live we discovered tha

Consuming REST services in OpenSpan

Image
This topic is about consuming REST web services in OpenSpan. Problem Statement Process to be automated involves REST service calls to retrieve data from a website. OpenSpan only supports WSDL services and therefore calls for creating a custom component that can be integrated with OpenSpan. Solution Creation of C# based custom component that takes 3 parameters namely URL, Method and Body and output the JSON string result. This result can be further parsed by converting it into XML and later on iterating through the required nodes. Automation Logic Calling Rest Web Service via C# public void CreateObject(string _URL, string _BODY, string _method, out string response) { string URL = _URL.Trim(); string DATA = _BODY.Trim(); response=string.Empty; HttpWebRequest request = (HttpWebRequest)WebRequest.Create(URL);             request.Method = _method;             request.ContentType = "application/json";             request.Conte