/
Integration Testing

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

Integration Testing

 

user mule_svc is used in the intergration

Source

Purpose

Scenarios

Source

Purpose

Scenarios

SITS

sync ALumnis - From SITS to Salesforce

  • New Alumni - Create as per mapping rules.
    New record created on the following objects:
    > Account
    > Contact
    > AQB__AlternateID__c
    > AQB__AQAddress__c
    > AQB__Education__c
    > AQB__AreaOfStudy__c

  • Existing Alumni
    > update Account and Contact if SITS date is later than salesforce modified date
    > Upsert on other objects using external id
    > For AQB__AQAddress__c object upsert need to fetch the RecordTypeId for Email and Phone type from RecordType object.

  • Errors
    NON-ENGLISH-ADDRESS - if Address contains non English asci characters.
    NO-EDUCATION - if SITS doesn’t send any Education data
    POBOX-ADDRESS - if address starts with PO or P O or P.O strings (case insensitive)
    ERROR - All others. This could contain if any updates, creations failed or any other data quality issues.

iModules

Receive online donations

  • Batch with more than 5 different transactions

  • Donor is matched

    • iModule id in alternate id.

    • donor firstname and lastName and email

    • alternate channel using email

    • found check for bioupdates (updates to biographical data) by comparing FirstName, LastName, Email and Postcode fields between iModules and Salesforce.

    • create a new batch in AQB__Batch__c

    • create transactions on batch item

  • if Donor doesn’t exist - create new Lead

    • if BIO update are relevant - log it for manual verification.

  • below exceptions are logged for iModules integration.

    • BIO-UPDATE - It indicates one of the fields (FirstName, LastName, Email and Postcode) in iModules have changed

    •  

Peoplesoft

validate the COA in Peoplesoft

  • cc = transaction.USYD_Class_Code__c

  • rc = transaction.USYD_Responsibility_Centre__c

  • pc = transaction.USYD_Project_Code__c

  • ac = transaction.USYD_Analysis_Code__c

 

?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:syd="http://xmlns.usyd.edu.au/Enterprise/FSCM/schema/SYD_COMBO_CF_EDIT_REQ.V1">
  <soapenv:Header/>
  <soapenv:Body>
    <syd:Request>
      <syd:ChartfieldValidationRequest>
        <syd:BusinessUnit>UNSYD</syd:BusinessUnit>
        <syd:LedgerGroup>ACTUALS</syd:LedgerGroup>
        <syd:AccountingDate>2022-10-14</syd:AccountingDate>
        <syd:ChartfieldValidationDetail lineNumber="1">
          <syd:Distribution lineNumber="1">
            <syd:Accounting name="DistributionCharge">
              <syd:AccountingSegment id="">
                <syd:Classification/>
                <syd:ResponsibilityCentre>61006</syd:ResponsibilityCentre>
                <syd:AnalysisCode/>
                <syd:Project>00000</syd:Project>
              </syd:AccountingSegment>
            </syd:Accounting>
          </syd:Distribution>
        </syd:ChartfieldValidationDetail>
      </syd:ChartfieldValidationRequest>
    </syd:Request>
  </soapenv:Body>
</soapenv:Envelope>

  • validate a Batch with valid COA

  • validate a Batch with invalid COA data

Swift

Bio update and unsubscibes

  1. Unsubscribe a contact
    find contact in campaign and populate the stop date

  2. Bio Update is working as expected:

  3. Error log

    1. contact not found

    2. Reactivated

    3. Error

 

 

 

Related content

TAP Solution Slayers (TAPSS) - Team Space (to be archived)
TAP Solution Slayers (TAPSS) - Team Space (to be archived)
Read with this
TAP-908 SITS/Jarvis Integration - Business Logic
TAP-908 SITS/Jarvis Integration - Business Logic
Read with this