✅ The short answer:
Just click here or go to Admin --> Integrations--> CPOMS (links coming soon).
We'll walk you through the steps to set up the integration. Keep reading for a step by step and troubleshooting guide.
1️⃣ Make sure you have matching MIS IDs or UPN numbers in STEER and CPOMS
To work properly, you need to have matching IDs in STEER and CPOMS. CPOMS recommend using UPNs (unique pupil numbers) but you can also use a matching MIS ID.
How to check MIS ID in STEER
Go to admin --> Data Management --> Student Data --> Edit
How to check MIS ID/UPN in CPOMS
Go to any students profile and you can see their MIS ID on the overview. If they have a UPN, this will be shown as a separate field.
If they match already:
Great! There is nothing you need to do. Just set-up the CPOMS integration using the self service tool (when it becomes available in July).
If they don't match:
Your can use our simple Update MIS ID tool.
(You need to be a STEER Admin to use this).
This article walks you through the process.
2️⃣ Activate the STEER Integration on CPOMS
Go to the CPOMS Integrations page and add STEER!
3️⃣ Enter the set-up information
Here, you need to provide 3 bits of information from CPOMS.
- API Token
- School CPOMS Portal Url
- CPOMS Category Id
You should be provided with this information when you activate the STEER integration on CPOMS (previous step).
3️⃣ Test the integration
As shown on the set-up tool, we will send a test incident to CPOMS for a random student. Note that you can switch the student if they are unsuitable for whatever reason.
We will send a test incident with the text: “STEER Testing - Please Ignore”
If there is any issue on our side, we will flag it at this stage. This normally relates to mis-matching STEER and CPOMS IDs. Reach out to our support and we will help.
Assuming that the incident was successfully sent, you now need to verify that it can be seen by all the expected staff on CPOMS.
The most common problem schools face is with their CPOMS permissions. If you find that some staff cannot see the test incident, then use our troubleshooting guide to investigate. Failing that, please reach out to CPOMS support.
Make sure to ask a variety of different staff to confirm they can see it. It is not enough to just check with the DSL for example.
🚨 Important
Please take special care to confirm that all relevant staff members can see the test incident. It is much better to do this now, to avoid issues when you rollout the integration. Failing to properly verify the integration can result in significant staff frustration and wasted time. Staff have been told that their IT teams are expected to have tested the integration, so it is imperative that this happens.
3️⃣ Activate the integration
Assuming that the testing as all gone well, you can now activate the integration! This will make the share buttons visible to all staff. Of course, they can only share students they have permission to see on STEER.
Comments
0 comments
Please sign in to leave a comment.