Batch Job / Scheduled Flow Name | High Level Description | Apex Class/Flow being Referenced by the Job | Timing/Frequency | Related JIRA |
|---|---|---|---|---|
UsydSpecialCategoryCalculationSchedule | This batch handles the update of Special Category field in Account and Contact records to reflect all the special category names of the transactions under that account. This would also create/update alerts from the Account and Contact depending on the special category names collected from the transactions of the account. | UsydSpecialCategoryCalculationSchedule | Everyday except Sunday at 10 pm | |
USYD Summarise Contact Campaign to Contact Scheduled | Updates contact, campaign and campaign members to summarize the campaigns clicked, participated, received and registered. | USYD_SummariseCampaignToContactScheduled (batch class) → USYD_Contact_Campaign_Summary_Fields_Subflow (subflow) | Everyday at 7 AM | |
Contact Case Schedule (API Name: USYD_ContactCaseSchedule) | This schedule-triggered flow serves as the main flow for scheduled creation of cases. At present, it's configured specifically for the creation of 'New Decease Request Cases' and utilizes a referenced subflow called 'Contact Deceased Case 105.' | Contact Deceased Case 105 | Everyday at 6 AM | |
USYD Update Case related Records Start Date for Deceased Case | Flow was built to query on all related records for the Contacts to be deceased to avoid any AQ validation errors when doing the deceasing utility where Death of Date might be greater than the start date on related objects namely:
| USYD Update Case related Records Start Date for Deceased Case | Daily at 8PM | |
Usyd_UpdateContactLegalCreditBatch | Daily at 8PM |
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
General
Content
Integrations