For the purposes of this article, Groupcall Xporter refers to Groupcall Xporter, Groupcall XE, and Hosted Xporter.

Groupcall Xporter can be configured with tokens to enable additional functionality. The version of Groupcall Xporter used by RM Unify runs a job configured with the RMIncludeFuture token on a daily schedule. This token, installed and set to 'true' by default, enables account pre-provisioning.

Pre-admission students will not be extracted unless they have been entered correctly.

1. Students must be entered into Admission.

2. The students must also be in the Accepted state (Admitted state students will be
   extracted as normal and are not treated as pre-admission).

3. Groupcall Xporter will extract students from the previous year's pre-admissions who are in the Accepted state.
4. Users will not be extracted if they have been entered manually into SIMS but are not in pre-admission.
5. On the first day of term, any pre-admission user left as Accepted in SIMS will be deemed not to have arrived in school and:
• if RM Network Provisioning is installed - The user will have their RM Unify account deleted and their network account disabled
• if RM Managed Services User Provisioning is installed - The user will have their network account and RM Unify account deleted 

Groupcall Xporter will extract student users who have the following required fields entered. Omitting any of the following will result in the user not being extracted:

• Application Status as Accepted.
• UPN (permanent only - you must not enter a temporary UPN).
• Forename.
• Surname.
• Year Group.
• Registration Group.
• Gender.
• DateofBirth.

Students who have an Application Status as Admitted and all the other required fields listed above completed will be treated as normal students, not pre-admissions.

Additionally, all staff who have their employment date set in the future will be extracted as pre-admissions. For example, if today's date is 28 June 2020 and the user's start date is 25 August 2020.

Advice from Groupcall is that any user with a record entered into the MIS with a start date in the future will be a candidate for extraction. If no users are extracted, the advice is to log a support ticket for Groupcall to investigate these on a case-by-case basis and to propose solutions and relevant changes for the MIS records in question.

If pre-admission staff or students have already been extracted, they will be deleted if the token is deleted.

Consider the following scenario:

• The RMIncludeFuture token is set to true and an extract is performed. The pre-admission user accounts are created.
• Subsequently, the RMIncludeFuture token is set to false (or deleted) and an extract is performed. The pre-admission users will have delete updates sent by Groupcall Xporter and the users' network accounts will be disabled (RM Unify Network Provisioning) or deleted (RM Managed Services User Provisioning).

Where your RM Unify student user accounts are provisioned using MIS Sync in Create mode and the username format consists of the year of entry (YOE), you may find that the current academic year is used instead of the expected next academic year, e.g. July 2023 actually falls within the 2022 academic year, so any of the 2023 academic year intake added to the MIS in July 2023 and pre-provisioned into RM Unify will have '2022' in their usernames as opposed to the desired '2023'.

Development within RM Unify MIS Sync is required to address this issue, but in the meantime, it is possible to use the MIS User Rename functionality in the RM Unify Management Console to quickly and easily update your users' account names to the desired format. Please see TEC6902586 in the Other Useful Articles section below for more information.