Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Gift Implementation Unit Testing
- anderson.pagtabunan
Processes/Sub-flows
USYD GIN - Stage based Update - Before Save (subflow)
Background of issue:
Multiple element of the same process are evident on flow and needs refactoring.
Unit testing:
Record Conditions | Result |
|---|---|
Gift Implementation > Stage is 1. GI-Handover | Record > Last Stage Modified Date is Current Date |
Gift Implementation > Stage is 3. GA-Entry | Record > Last Stage Modified Date is Current Date |
Gift Implementation > Stage is 4. GA-Approval | Record > Last Stage Modified Date is Current Date |
Record > Last Stage Modified Date is Current Date | |
Record > Last Stage Modified Date is Current Date | |
Record > Last Stage Modified Date is Current Date | |
Record > Last Stage Modified Date is Current Date | |
Record > Last Stage Modified Date is Current Date Email notification is sent out to advancement-services.gifts@sydney.edu.au regarding the Gift Implementation |
Create or open an existing Gift Implementation record.
Update the Stage field according to the table above and check that it results to what is expected.
On testing the Email notification, this may not be possible without any access on the email distro. Kindly coordinate with the respective people involved in the email distro(advancement-services.gifts@sydney.edu.au).
USYD Usyd_Update Gift Implementation Status (subflow)
No logical changes on flow and only converted to subflow.
Documentation and testing can be found on TAP-253 - MS - Column header in their List View called Action - calculated field.