Professional & Continuing Ed Quick Admit - Enroll Automation

In Process [In Process]

47% complete, updated on Tue 8/11/26 12:54 PM by Gloria Walden Johnson

Changed Percent Complete from 46% to 47%.
Professional & Continuing Ed Quick Admit - Enroll Automation Project Update Overview – Progressing, with integration dependencies and end-to-end testing still open

The project made meaningful progress in Salesforce - orchestration, transaction validation, error handling, and preparation for business review. The status is Yellow until Person Match is completed, Boomi can access the required Salesforce custom fields, and a request successfully completes the entire end-to-end process.

1. Key Highlights/Steps Complete

• Successfully tested the residency and term-activation API transactions.
• Confirmed that the course-enrollment API returned the appropriate error when the selected course did not have an open section in the test environment.
• Advanced the Salesforce orchestration process for External Registration Requests.
• Separated residency from program enrollment because residency is an independent API transaction that may fail separately.
• Implemented validation of required student data before API processing begins, including first name, last name, email address, date of birth, and phone number.
• Configured requests with missing information to stop processing and enter an error state with an explanatory message.
• Established asynchronous Salesforce processing that records completed integration steps, allowing failed requests to resume at the point of failure.
• Confirmed that API request and response logs are being captured in Salesforce; consistent log creation and association still require validation.
• Todd obtained access to the PeopleSoft TST environment and can independently verify transaction results.
• Identified and corrected a missing Salesforce Create permission during Boomi troubleshooting.
• Defined the proposed error-resolution process:
  • Failed requests will appear in a centralized Salesforce Errors list.
  • PCE users will review and correct the underlying issue.
  • A Reprocess button will restart the request from the failed step.
• Confirmed that Person Match will occur before Person Create.
• Confirmed that successfully matched or created students will generate Salesforce account records using the PeopleSoft EmplID as the external identifier.
• Agreed to change the Salesforce UAT API connection from version 64 to version 62 to align with production and troubleshoot the Boomi custom-field visibility issue.
• Continued incorporating the PCE functional stakeholders into technical Scrum sessions for business validation.
• Reduced formal communications and training activities because the operational change affects only one department and two primary functional users.
• Agreed to invite Chloe to the next Tuesday Scrum session for a preliminary business review

• Person Match integration: The complete match-or-create sequence cannot be validated until the intended Person Match integration is available and completed.
• Boomi custom-field access: Boomi can locate the External Registration Request object but cannot see its custom fields. This may prevent CTA data from loading and block automated end-to-end processing.
• PeopleSoft test data: The team must identify an existing open course section before course-enrollment testing can be completed.
• Country-code transformation: Salesforce transmitted US, while PeopleSoft requires USA, causing the transaction to fail.
• Reprocess functionality: The Reprocess button is not yet complete, preventing corrected requests from efficiently resuming at the failed step.
• Business-facing error messages: Technical PeopleSoft responses must be translated into clear, actionable instructions for PCE users.
• Logging consistency: An expected API callout log did not initially appear during the demonstration. The team must confirm that each transaction consistently creates and associates the correct log.
• Notification approach: Broad automated notifications may overwhelm users. Chloe should determine whether the centralized Errors list provides sufficient operational visibility.
• Project-management coverage: Gloria’s upcoming absence may delay coordination unless meeting ownership, invitations, and escalation responsibilities are confirmed in advance.
• Schedule exposure: Delays involving Person Match, Boomi custom-field access, valid PeopleSoft test data, or Reprocess functionality could affect business validation and end-to-end testing.
• Overall status: The project should remain Yellow until the major integration dependencies are resolved and a request successfully completes the full end-to-end process

• Immediate actions:

• Correct the Salesforce country-code transformation from US to USA and rerun the transaction.
• Identify an open PeopleSoft course section with valid enrollment test data.
• Continue developing the Person Match integration.
• Change the Salesforce UAT API connection from version 64 to version 62.
• Retest Boomi access to the External Registration Request custom fields.
• Schedule additional troubleshooting with Jim if the API-version change does not resolve the Boomi issue.
• Investigate the missing or inconsistent API callout log.
• Develop and test the Reprocess button.
• Convert technical API errors into business-friendly messages.
• Prepare the Salesforce Errors list with the fields Chloe needs to evaluate and resolve failed requests.
• Invite Chloe to the next Tuesday Scrum session to review the workflow, error-resolution process, and notification requirements.
• Update the card wall to reflect completed, active, blocked, and remaining Salesforce tasks.

• Next major milestone:

  Complete one External Registration Request through the full process:

• Person Match or Person Create
• Program enrollment
• Residency
• Term activation
• Course enrollment
• Salesforce account creation

• Target: Complete a successful end-to-end demonstration by Thursday, August 13, 2026, subject to resolution of the Person Match, Boomi-access, and test-data dependencies.