Hi,
Difference between Linear process and Transactional process
Thanks
jayakumar S
Hi,
Difference between Linear process and Transactional process
Thanks
jayakumar S
Thanks, i would like to know this actually.
Difference between Iterative process and Transactional process???
Hi @JayakumarSanthanam
There are three different types of processing.
All three differ on how data is fetched and processing is done.
Linear: Data is fetched once and processing is done once.
Iterative: Data is fetched in bulk and processing is done iteratively.
Transactional: Here data fetching and processing are independent from one another as they are split into different states. In iterative if a single data point results in a failure, whole workflow can fail but in transactional as transactions are independent of one another a single data point never results in breaking down of complete workflow.
hello sir.can you make a video in english ?
This is a quick description for that
1. Linear Process:
2. Iterative Process:
3. Transactional Process:
4. Sequential Process:
Choosing the Right Process
Linear: Ideal for simple, one-time tasks.
Iterative: Efficient for processing large datasets.
That isn’t at all what linear vs transactional processes are.
@postwick could you explain what they are then?
Others in the thread already did.
Sorry your post stating this isn’t what they are wasn’t a reply to any of the other posts so I didn’t know which one you were saying was wrong
Hi @JayakumarSanthanam
Linear Process: A linear process follows a straightforward, sequential path where each step or task is completed in a specific order, with each step dependent on the previous one.
Transactional Process: A transactional process involves a series of actions or steps that are grouped together to achieve a specific goal, where each action is treated as a transaction that must be completed successfully or rolled back if any part fails, ensuring data integrity and consistency.
In the UiPath context a transactional process is when you break the work down into smaller chunks called transactions. Usually (but not exclusively) transactions are stored in a Queue in the Orchestrator. The process will get the next transaction from the queue, process it, then get the next one.
The strength here is that, should the process fail, you should be able to pick up where you left off because the work has been divided into all these smaller distinct chunks.
A linear process on the other hand deals with a single process and as such it does not get smaller transactions or units of work from a queue, but just processes whatever it needs to do once, in a linear fashion.
Its been explained plenty of times above, Paul was just reacting to some AI generated stuff people post to try to increase their post count.