Reason: After resume stage the exception is dead so the Re thrown will not worked.

* Revisiting the Issue:
* Similar to Question No: 130, the developer is unable to pass collection data as an input parameter because the collection is not visible under the available data items.
* Analyzing the Possible Reasons:
* Option A: As previously explained, collections need to be set to global to be visible and usable as input parameters.
* Option B: A block surrounding the collection does not impact its visibility.
* Option C: The number of fields in a collection does not affect its visibility as an input parameter.
* Option D: Undefined fields in a collection cause functional issues but not visibility issues.
* Conclusion:
* The reason the collection is not visible as an input parameter is because A. The referenced Collection is not set to global.
References:
* Blue Prism Developer Documentation: Collections and Global Data Items
* Blue Prism Training Material on Data Item Scope and Visibility

* Understanding the Scenario:
* The developer is unable to make changes to the elements in the Application Modeller.
* This could be due to several reasons including permissions, application state, or system configurations.
* Possible Reasons for Inability to Edit:
* Option A: If the shared application model is locked for edits, it prevents any changes from being made until it is unlocked.
* Option B: If the user account does not have the necessary permissions, they will be unable to make changes to the application model.
* Option C: The run mode of the object being set to Exclusive would affect execution but not the ability to edit in Application Modeller.
* Option D: The target application not being launched or attached would affect element spying but not the ability to edit existing elements.
* Option E: If Application Modeller is opened during process runtime, it could limit some functionalities but should not generally prevent editing.
* Conclusion:
* The two reasons that prevent the developer from making changes to the elements in the Application Modeller are:
* A. Shared Application Model is locked for edits.
* B. User account does not have the permissions.
References:
* Blue Prism Developer Documentation: Application Modeller Permissions
* Blue Prism Training Material on Shared Application Models and User Permissions

* Session Variables:
* Session Variables are data items whose values can be changed while a process is running.
* Updating Session Variables:
* Variable Repository in System Manager (Option A & B): This refers to managing variables at the system level, which is not used for updating running process variables directly.
* Calculation Stage (Option C): This can be used within the process to update the value of a session variable during runtime.
* Control Room (Option D): Allows operators to update session variable values for running processes via menu options.
* Conclusion:
* The correct methods to update the value of a data item exposed as a 'Session Variable' while the process is running are:
* C. Through a Calculation stage in the same process.
* D. Selecting the running Process in Control Room and then using the menu options to push a new value to the data item.
References:
* Blue Prism Developer Documentation: Session Variables and Data Items
* Blue Prism Training Material on Control Room Operations