Queue - Mutliple Tags (5 Collection - 5 Dept => 5 Add to Queue(Tag mention))

=============================
Queue - Status
Current Status of your excution

01 - Records Added
02 - Records Processing
03 - Exception Occured (Exception)
04 - Record Completed Successfully
05 - All records Processed
===============================
Queue - ItemKey

=============================
Queue - Defer
Keep records in pending state for future time (It will not fetch the records till
the time passes)
1. When Adding records into the Queue
2. By Using Defer Action
======================================
Queue - Mark Completion & Exception
Acions for both the operations
==========================================
Application Modeller Sharing

=======================================
Active Queue
- Advance version of Queue
- Creation can be done in System tab -> WorkQueues -> Active queue checkbox need to
be selected and allocate the published process & Resource Group
- Combination of Session management and Queue Management
- User friendly UI for checking/monitoring session as well as Queue updates

1 Active Queue (BPTravel_Queue) -> 1 Process (BPTravel Operation) -> Multiple

Resources
============================================================================

Q - When are we getting a ‘stack imbalance has occurred’ exception?

A - This error is thrown when you are in recover mode an exception has already
occurred but has not been cleared by a resume stage and
manually set to run another stage and another exception occurs again.

---------------------------

>Multi Bot Architecture

-Multi bot architecture means multiple bots are assigned on single process to
divide process workload
-It reduces time to complete the work of process because multiple bots are working
together to complete Specific task
-work will gets divided with multiple bots.
-Functions like Environment locking and Work Queue are useful in multiple bot
Architecture.
-Environment lock uses the concept which uses token system, the bot which acquire
the lock first will get
the token and other bot cannot access that process part until first bot releases
the lock or the token so
we can prevent multiple bots from accessing same part of a process
-And using work queue, work is distributed with multiple bots, each record of work
queue has different
status, like pending, Locked, Exception and Complete, so if any record is pending
that record gets picked by
the available bot machine.

2 resources - 1 ABC, 1 XYZ

============================
Thick client Application
Thin client Application

Environment Locking
Stopping Methods (Request Stop, Immediate Stop)