Please refer to the exhibit.

Single Object Design:

According to Blue Prism best practices, it is generally recommended to minimize the number of objects and actions to keep the solution simple and maintainable.

Actions:

Get Account Details: This action retrieves account information from the screen.

Apply New Limit: This action applies a new limit to the account.

Decision-Making Logic:

The decision-making logic (checking for high-risk code) should be placed in the process, not the object. This separation ensures that the object focuses on interacting with the application, while the process handles the business logic.

References:

Blue Prism best practices on object design and separation of concerns between objects and processes.