May I know what will be the possible pros and cons on the created queue if the “Enforce unique references” is being checked?
This checkbox determines whether or not duplicate items can be added to a queue. There are certain pros and cons here but it depends on your project requirement & perspective.
- Enforcing unique references can help ensure that data in the queue is not duplicated or overwritten, which can improve the accuracy and reliability of your processes.
- By preventing duplicate items from being added to the queue, you can reduce the likelihood of errors caused by processing the same item multiple times.
- If you accidentally try to add a duplicate item to the queue and the “Enforce unique references” option is enabled, the item will not be added and the data may be lost. This can be particularly problematic if the item represents critical information.
- If you need to retry a failed transaction, you may need to create a new item in the queue rather than simply processing the existing one again.
Hope this helps,
Reference - The reference of the added QueueItem. The reference can be used to link your transactions to other applications used within an automation project. Additionally, this feature enables you to search for certain transactions, in Orchestrator, according to the provided string.
This property is available starting with v2017.1.
Additionally, references are not compatible with the 2016.2 or lower versions of Orchestrator or Robot.
You can find it in the Add queue item activity as in the screenshot below.
Maybe you are using 2016.x version of the Studio?
If you have it available on the activity, you just have to pass a string with the ID to the input argument.
Hi @arjunshenoy and @GANESH_BALAGAM
Thank you for your inputs and solutions. Both are helpful. I really appreciate it.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.