Smart offers Financials users the ability to 'chain' business processes together, enabling easy execution of end-to-end Financials tests by allowing Test Runs to reference objects created by previous test cases within the same Test Run.
A Financials Chain test run can be constructed by adding the business processes in the correct sequence. At a very basic level, the most simple Financials Chain is the Journal Chain. This consists of the Create Journal business process and the Unpost Journal business process. The Create Journal template is populated with data in the standard format. The Unpost Journal template then needs to be populated with the journal number created as a result of Create Journal.
Smart can do this by using the operator '<FROM_TEST_CASE: XXXXXX>' (where XXXXXX is a Test Case ID) in the Unpost Journal template. When Create Journal runs, Smart keeps a record of the journal number within the test case information. '<FROM_TEST_CASE: XXXXXX>' instructs Smart to take the resulting Journal number from the specified test case and use it in the specified field. This allows the creation and unposting of a journal to be handled with no manual interaction.
From a technical perspective, the '<FROM_TEST_CASE: XXXXXX>' operator fetches the generated Financials data from the specific test case in the same test run (whether it is a purchase order number, supplier number, invoice number) and uses it at the point in which the operator is specified in a template. This means users can for example run Create Journal, then run Integrations for reporting purposes, and finally run Unpost Journal which will still reference the original journal that was created.
See the images below for an example of how a simple Financials Chain would appear in the Create BP/Integration Test screen, as well as how the Create Journal and Unpost Journal templates would look when populated.
At present Smart supports chaining in six different Workday Financials Functional areas. These are illustrated in the image below. As with the simple Financial Accounting chain example provided above, users can run these chains with Integrations or other Business Process tests in the same Test Run, however the structure from top to bottom must not change in relation to the Financials tests.
The steps listed in each of the Chains are not required, allowing users to start at any point in the chain, as well as end at any point. Additionally users can choose not to carry out a particular BP if it is not needed (e.g. go straight from Create Customer to Create Billing Schedule, skipping the Create Customer Contract BP if the tenant configuration allows this).
The Financial Accounting example provided above is a demonstration of the basic functionality of Financials Chains, chaining one test to another. Smart offers the ability to chain together multiple Financials test cases in one test run, even if these tests are outputting different types of Financial data. This enables users to run large amounts of Financials tests and create complex chains within each workflow.
Using the above Chain Types table as a reference, users can plan what path their test is going to take and then build the templates accordingly using the <FROM_TEST_CASE: XXXXXX> operator in the required fields to reference the required test case.
Additionally, if the Financials test case outputs Financials data that contains multiple lines (e.g. in a Supplier Invoice), the <FROM_TEST_CASE> operator can be used to reference a specific line by referencing its index. For example, if a Supplier Invoice was created containing 3 service lines, if users wish to reference the third line in this Supplier Invoice they could specified <FROM_TEST_CASE: XXXXXX, 3>.
See the image below for a visual representation of a scenario using multiple chains. In this particular scenario, the user has created three Suppliers. Two of these Suppliers are going to be used in order to Create Supplier Invoices. One Supplier is going to be used with Create Ad Hoc Payment, then Create Settlement Run will be executed for all three tests.
The key to referencing the required data in Financials Chains is that the operator is placed in the correct field. For Create Supplier Invoice, the Supplier field is where users would reference a previous test case. Using the example above "<FROM_TEST_CASE: CRTSUP02>" and "<FROM_TEST_CASE:CRTSUP03>" will allow the Create Supplier Invoice template to pick up the correct Supplier number from the initial Create Supplier test. Similarly within the Create Ad Hoc Payment template, the value "<FROM_TEST_CASE: CRTSUP01>" in the Payee field will pick up the correct Supplier created.
Within the Create Settlement Run template, it is simply a case of referencing the Test Case IDs from your Create Ad Hoc Payment/Create Supplier Invoice templates within the relevant field (Supplier Invoice, Expense Report or Ad Hoc Payment).
When viewing a Financials Test Run that contains chained tests, users can select the Chains View tab (highlighted below) to enter the Chains View. In this view, Smart will display (in order) the various chains that exist in any given test run in an easy to read format.
If a test case in the pack is not included in any chains, it will be under its own individual heading with no further test cases.