* 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