Communications
Keep notices, follow-up and communication history in context. Email and SMS use connected providers; campaign tools may have their own authoring and sending responsibilities.
Fits into your institution's world
Workday and Banner
admissions integrations.
Connect Crossroads admissions software with your student information system. Workday Student and Banner integrations are available. Plan the records, mappings and handoffs your institution needs, with clear responsibilities for setup and ongoing operation.
01 / Student information systems
Workday Student
integration.
Crossroads integrates with Workday Student. Start with the admissions handoff your institution needs, then work through the details with the people responsible for both systems.
Ask about WorkdayA shared understanding of the handoff.
Your admissions process determines which information needs to move. Your Workday environment determines the access, vocabulary and configuration needed to support that exchange.
Bring one admissions scenario to the discussion: the event that starts the handoff, the information needed in Workday Student and the result staff expect to see. Use it to check the supported scope before planning the connection.
- Records and direction
Identify the admissions information involved and which system supplies or receives each part.
- Timing and changes
Agree when information should move and how later corrections should be handled.
- Access and ownership
Bring your Workday administrator into the discussion of environment access, setup and ongoing responsibility.
02 / Student information systems
Banner admissions
integration.
Crossroads integrates with Banner. Plan the connection around your institution's admissions records, local codes and the people who maintain them.
Ask about BannerMake the local details part of the plan.
Term, program and other institutional values need an agreed meaning on both sides of a handoff. Include the Banner owners who can explain those values and the business process they support.
Bring a sample of your institution's data definitions and an admissions scenario to review. Identify the values that need mapping, the expected result in Banner and how staff will verify it against the agreed scope.
- Institutional vocabulary
Review the codes and values involved in the selected admissions exchange.
- Matching and reconciliation
Agree how records are identified and how the team will check the results.
- Environment and responsibility
Identify the Banner environment, required access and the owner of any institution-specific work.
The information behind the connection
Agree the records.
Understand the exceptions.
A useful integration conversation follows the work from one system to the other. It should leave your team with a clear account of the information involved, how to check it and who responds when something needs attention.
Agree the records
Define the business event, data involved and system responsible for each value.
Map the information
Work through identifiers, institutional codes and required values.
Validate the handoff
Agree representative cases and how your team will reconcile the results.
Assign exceptions
Identify who investigates a rejected record and how an agreed correction is handled.
People on both sides
Know who owns
the next step.
Admissions, institutional IT and Advant bring different knowledge to the connection. Make those responsibilities explicit during implementation and keep them understandable after launch.
Plan migration alongside integration- Admissions team
- Explain the process, required information and the point at which it should pass to the SIS. Review the result in business terms.
- Institutional IT / SIS
- Bring environment and access requirements, local data definitions and the people who maintain the receiving or supplying system.
- Advant
- Work through the Crossroads side of the agreed scope, implementation responsibilities and the support arrangement.
These are planning roles. The proposal should name the actual owners, deliverables and ongoing responsibilities for your institution.
Review security and data questionsThe rest of the picture
Your admissions environment
includes more than the SIS.
Crossroads connects staff and applicant work with the services your institution uses. Include communications, identity, documents and payments when discussing the full process.
Identity and source data
Discuss staff access, applicant identity and any source of inquiry or application information that needs an agreed handoff.
Documents and payments
Identify how supporting material and any payment services fit the selected application process, including who handles exceptions.
Agree the services, supported exchanges, account requirements and any separate provider charges as part of your implementation scope.
Bring your SIS questions
Let's look at the handoff
your institution needs.
Bring the systems you use, the information that needs to move and the people who own the process.