I’m working with a set of 100 queued items, each containing information that must be entered into two different forms: one in SAP and one in a web application.
The main requirement is to first process the 100 items in SAP. Once that step is completed, the same 100 items must be processed in the web application. It’s essential that these two steps run sequentially, not simultaneously.
Furthermore, it’s mandatory to use a single queue to manage the items and a single REFramework-based project for the entire process.
Solution designing shouldn’t be restricted on the basis of factors like one queue or one bot.
Regarding your situation here, I think entering data in SAP and web application in one go after one another would be most efficient way. This will avoid retouching the same data twice.
Until and unless you have any business logic which states you can’t proceed both right after each other, I would suggest to follow this approach.
Yes, that is more efficient, but the client has their own business rules and wants it to be done first in SAP and then in their web app, all within the same process.
YES, it is not the most efficient solution but it is the way the client requests its development, he tells me that with another RPA tool it can be done
technically, this way also, its gonna happen first in SAp and then in web app but one by one rather than bulk.
i understand that its been requested by client, but I would say its worth understanding why such requirement is being raised by them, is it just a preference or if there is any actual business logic that can get hampered when its not done like they requested. Also, which other tool they are mentioning? is this some kind of PoC project wherein you are looking to see if it can be done via UiPath or not?
Doing 100 in SAp and then referring those 100 in web app is not the right way to do it as when you pick a queue item for SAp processing, it would go in in-progress state already and then it cant get picked again. You would have to either go with 2 queues( in same or 2 separate projects(more better)) or do it one by one with first SAp and then web app in the sequence.
Two separate automations, two separate queues. First automation picks up the queue item and does the SAP steps then creates a queue item in the second queue.
First thing if you ask if this can be done then yes Iitcan be done..with only one queue and pne process yes..but it just complicates the process
May be business has a requirement of first sap and yhen web app for all items and what happens if one fails? You want to stop all?
And why is the business requirement only to use one queue and one process? That cannot be a business requirement but should be a design consideration
But just for the sake of making it happen you can ..by using reference in queues..and then using dynamic variable for reference and then change the reference value once all 100 items are processed so next 100 will start..but again there are so many thing sot consider if you want 100 as set then if new items add then they have to be controlled if something is failed and retried need to check those etc..