Mapúa Malayan Digital College · Enrollment Operations
Ticket log triage, the week's two blocking defects, fixes shipped, and the GSA register — reported separately.
Period
Term 1, 2026
Prepared
30 July 2026
Scope
70 tickets · 92 GSA records
Internal working document — not for external distribution.
Ticket log · 70 records
Operations · 45 · 64%
Technology · 23 · 33%
Operations — manual fix, no engineering dependency
Technology — EnrollMate–Salesforce sync layer
All 23 technology tickets trace to one sync layer, and the 12 untagged learner emails are the oldest — running back to 29 June.
Plus 2 administrative: APP-59718 student number correction, APP-64235 blank duplicate.
Biggest issues this week
No learner email
12 ticketsCause
Expired Salesforce credentials. A new SF security policy requires passkeys; enforcement moved to October, but passwords still had to be rotated.
Effect
Rotation invalidated the integration credentials. CAMU and Google Workspace provisioning stopped writing back, so enrolled learners never received an account and were never tagged.
Resolved
130CAMU and Google Workspace accounts resent.
Watch: passkey enforcement lands October — integration credentials need a migration plan.
New apps not syncing to Salesforce
Cause
Applicants selecting the ASU collaboration option stall: Salesforce script-injection protection HTML-encodes the apostrophe, so the value no longer matches the restricted picklist.
Effect
Insert rejected, application stalls. Compounded by picklist option changes in EnrollMate that never propagate to Salesforce.
SF insert failed: Why do you want to study in MMDC?: bad value for restricted picklist field: MMDC's collaboration with Arizona State University
Resolved
No data lost. Applications resynced the same day the issue was reported.
Watch: any future picklist value with an apostrophe, ampersand or quote fails the same way.
Fixes
95%
of last week's CAMU-related issues resolved. Integrations working, aside from intermittent 503 errors.
130
CAMU and Google Workspace accounts resent. Learner email now syncing to Salesforce.
Zero
data lost on the picklist failure. Blocked applications resynced same day; no applicant resubmitted.
Learner email syncing in Salesforce
Credentials restored, 130 accounts resent
Engineering
Fixed
Document links syncing in Salesforce
Clears the 7 document-sync tickets
Engineering
Fixed
Application insert on ASU picklist value
Resynced same day, no data loss
Engineering
Fixed
CAMU integration
Intermittent 503 errors remain
Engineering
Working
Picklist parity check EnrollMate → Salesforce
Decode entities before insert; add release check
Engineering
Open
Passkey migration for SF integration credentials
Enforcement lands October
Engineering
Not started
GSA register · 92 records, reported separately from the ticket log
Invalid student number on upload
Manual reupload of application data
Operations
66
No GSA / not visible in EnrollMate
Re-request GSA, then reupload
Operations
19
Paid but stuck in GSA, not tagged enrolled
Move to completed, tag as enrolled
Operations
5
No GSA in EM and SF amount not updated
Re-request, reupload to SF, CAMU and EM
System
2
What is driving the operational cases
Invalid student numbers
The MCL system failed to read applicant data on upload, blocking assessment generation downstream.
Underpayment
Payment reads short because early-bird discount tagging or the Asenso 20% was not applied. Learners paid correctly.
Unfinalization and reassessment
Reopened GSAs do not re-publish to EnrollMate, leaving no visible assessment and no route to payment.
Sequence the fix. 88 unique applications — four appear in both §1 and §2, so reupload application data before re-requesting a GSA that would fail again. One resolved: APP-60059, interschool settlement, GSA completed and tagged enrolled.