* Defined within the Object Layer:
* Blue Prism Business Objects are defined and created within the Object layer. This is where objects interact with external applications, providing a way to encapsulate the application's functionality into reusable components.
* Actions Built to No Specific Hierarchy:
* Actions within a Business Object are not required to follow a specific hierarchy. They are built to perform specific tasks or operations and can be executed independently of one another.
* Incorrect Options:
* B. Will always have a Launch action: Not all Business Objects require a Launch action, as it depends on the nature of the application being automated.
* C. Can be used as a stand-alone process: Business Objects cannot be used as stand-alone processes. They are designed to be invoked by processes.
* D. Do not share any stages with the Process Studio: Business Objects share many stages with
* Process Studio, such as calculations, decisions, and data items.
References:
* Blue Prism documentation on the Object layer and Business Objects.

To ensure that only credit transactions are included when calculating the total of customer credits, the 'Credit Transaction?' decision stage needs to check if the transaction code is between 50 and 99. Given that transaction codes are stored as text, we need to convert these values to numbers before performing the comparison.
* Customer Transactions Collection:
* The 'Transaction Code' column contains text values representing the transaction codes.
* Credit Transaction Identification:
* Credit transactions have transaction codes between 50 and 99.
* Therefore, the correct condition should convert the text transaction code to a number and check if it is greater than or equal to 50.
* Decision Stage Expression:
* The correct expression is ToNumber([Customer Transactions.Transaction Code]) >= 50, which ensures that only credit transactions are included in the total calculation.
References:
* Blue Prism Process Design guidelines
* Data type conversion functions in Blue Prism

* Understanding the Process Diagram:
* The diagram includes a calculation stage named "Get Date of Previous Day" and a data item named "Result Date".
* The Calculation Properties window shows the expression Yesterday() used in the calculation stage.
* Analysis of the Calculation Stage:
* The Yesterday() function is used to get the date of the previous day.
* The result of this function is stored in the "Result Date" data item.
* Data Type Considerations:
* Option A: This option is incorrect because there are correct statements regarding the process diagram.
* Option B: If "Result Date" is configured as a Text data type, a 'data type mismatch' Internal Exception will indeed be thrown because the Yesterday() function returns a date, not text.
* Option C: If "Result Date" is configured as a Date data type, the Yesterday() function will correctly set "Result Date" to the previous day's date.
* Option D: This option is incorrect because the Yesterday() function is valid and will not throw a
'Failed to evaluate expression' Internal Exception if used correctly with a date data type.
* Conclusion:
* The correct statement is:
* C. If the 'Result Date' data item is configured as a Date data type, then the 'Result Date' data item will be set to the date of the previous day on execution of the Calculation stage.
References:
* Blue Prism Developer Documentation: Date Functions
* Blue Prism Training Material on Calculation Stages and Date Manipulation