1 BEST ANSWER
Best Answers
Hi Vincent,
Please find a diagram below I created to illustrate the concept of different initialisation modes.
Use Auto-initialisation, you are able to call any action in any objects and each will be executed in a first-come-first-serve manner. You as the calling user do not need to handle any sessions associated with the call. Objects with any run-modes can be queued in the same session. This is usually the simplest for the caller to manage but depending on the request volume you may encounter delayed responses. 1 license is used for that runtime. This is the method most of the people would use.
Use Manual-initialisation, you must explicitly invoke Initialise and Clean-up actions methodologically. Calling an action from a new object cannot reside in existing sessions not associated with the same object. As you can see there is a lot of management you must do in coordinating those sessions in a runtime. People use Manual-initialisation if they want full controls over the session creation, and often that is only achievable through programming. Depending on the number of active sessions, multiple licenses may be required on the same runtime.
Hope this helps.
Regards,
------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------
Please find a diagram below I created to illustrate the concept of different initialisation modes.
Use Auto-initialisation, you are able to call any action in any objects and each will be executed in a first-come-first-serve manner. You as the calling user do not need to handle any sessions associated with the call. Objects with any run-modes can be queued in the same session. This is usually the simplest for the caller to manage but depending on the request volume you may encounter delayed responses. 1 license is used for that runtime. This is the method most of the people would use.
Use Manual-initialisation, you must explicitly invoke Initialise and Clean-up actions methodologically. Calling an action from a new object cannot reside in existing sessions not associated with the same object. As you can see there is a lot of management you must do in coordinating those sessions in a runtime. People use Manual-initialisation if they want full controls over the session creation, and often that is only achievable through programming. Depending on the number of active sessions, multiple licenses may be required on the same runtime.
Hope this helps.
Regards,
------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------
Hi Vincent,
Please find a diagram below I created to illustrate the concept of different initialisation modes.
Use Auto-initialisation, you are able to call any action in any objects and each will be executed in a first-come-first-serve manner. You as the calling user do not need to handle any sessions associated with the call. Objects with any run-modes can be queued in the same session. This is usually the simplest for the caller to manage but depending on the request volume you may encounter delayed responses. 1 license is used for that runtime. This is the method most of the people would use.
Use Manual-initialisation, you must explicitly invoke Initialise and Clean-up actions methodologically. Calling an action from a new object cannot reside in existing sessions not associated with the same object. As you can see there is a lot of management you must do in coordinating those sessions in a runtime. People use Manual-initialisation if they want full controls over the session creation, and often that is only achievable through programming. Depending on the number of active sessions, multiple licenses may be required on the same runtime.
Hope this helps.
Regards,
------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------
Please find a diagram below I created to illustrate the concept of different initialisation modes.
Use Auto-initialisation, you are able to call any action in any objects and each will be executed in a first-come-first-serve manner. You as the calling user do not need to handle any sessions associated with the call. Objects with any run-modes can be queued in the same session. This is usually the simplest for the caller to manage but depending on the request volume you may encounter delayed responses. 1 license is used for that runtime. This is the method most of the people would use.
Use Manual-initialisation, you must explicitly invoke Initialise and Clean-up actions methodologically. Calling an action from a new object cannot reside in existing sessions not associated with the same object. As you can see there is a lot of management you must do in coordinating those sessions in a runtime. People use Manual-initialisation if they want full controls over the session creation, and often that is only achievable through programming. Depending on the number of active sessions, multiple licenses may be required on the same runtime.
Hope this helps.
Regards,
------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------
