Related Posts
Hi All,
I joined Tech Mahindra for 5 days only and didn't find suitable timing for my project and emailed resignation mail to manager and HR. After that HR asked me to resign over portal but at the same time blocked my portal. After requesting many times they didn't unblock my portal and pretended like they want to unblock but there is some issue going on and marked my profile absconded. I have cleared fnf but they are not providing reliving letter but added pf amount also. What to do?
Hi Fishies, I was hired for wealth and asset management project EY . It is capital market domain. Any body have any idea about this project going on in EY and the tools used for it.
Please advise if anyone have idea about it.
Just want to know any global tool they use for wealth and asset management, so it's a plus for me to join.
Thanks in advance
Conversation Starter
More Posts
Conversation Starter
When is a 3 page resume acceptable?
Hey sharks
I got offer on Citiustech Healthcare Technologies
May I know how WLB in this company, I see in glassdoor and ambitions contains positive and negative. Is it worth to join? Is it useful for me to enhance my career for long run? How about the retention pay? If we leave the company we need to pay entire retention pay?I have other wipro and CTS, which company is better to join?
Visual Storyteller
Subject Expert
Additional Posts in Robotic Process Automation (RPA)
Worst consulting company to work for ?
Anyone hiring for RPA roles in your company ?
You two should talk
Any good book recommendations?
New to Fishbowl?
unlock all discussions on Fishbowl.
APIs are a much better approach to obtaining data, compared to UI.
Limitation is availability, both in them existing and IT being willing to provide access.
For Operations groups looking to circumvent their IT counterparts, asking for API access can be a hard no.
Short answer, in most cases leveraging the API is the best strategy.
Thank you both for your answers. However, i wonder what kind of challenges companies could have to set up APIs:
1) effort to set up couple of web-services should't take more than half-day/1 day per web-service. It amount to maybe a week or 2 if a lot of services are needed.
2) you can limit the type of actions of your services to "GET" if allowing "POST" actions is too risky. Knowing that people who would be given access to these web services already have access to the actual data through the app, what kind of additional risk are we talking about?
@M1
When you said that leveraging the API is usually the best strategy, did you mean combining API and RPA? Or simply use RPA if API isn't possible?
My group combines RPA with APIs. A typical process includes: pull data via the API, carryout necessary data manipulation or processing and then upload into another system via API.
Simple example, but using APIs is proving much more stable from a support perspective.
Why would you use RPA in that instance and not simply an ETL tool? I 100% agree that APIs should be leveraged where possible but the criteria for applying RPA should generally include some constraint (technical or organizational) where executing the multi-step process requires interacting with UI.
Performance and robustness as it can the UI dependency. Have you used/suggested APIs in a RPA project before? What are thoughts about this matter?
APIs are great if/ when they exist. Also for an api to work there has to be cross compatibility and that’s where things get murky even the hundreds of different application clients use and not to mention in-house apps