This is related to question "Add ability for admissions to set username" but a separate issue or bug.
When a student matriculates and the enrollment team adds their username from admissions, everything is set to LDAP and OU Genesis Accounts. However, the account will not run unless they go to System Admin, look up the student, enter the profile and click save and return. No changes are made, but the AD account is not made until Save and Return is clicked from that screen.
Ideally, we can get the process to streamline directly at the matriculation point, but until then, why is the system requiring us to go the sys admin screen and click save even though the info is already there and correct?
Status:
Closed
I am confused what you are talking about. The future enhancement is two fold:
– Add a Username type field to prospect that will create the username as the default type/ldap context when a student is added.
– Change the username field in Student/Employee to create the user as the default type/ldap context.
Currently, someone needs to go to the User page in System Administration and change the username of the new students to be the correct format and change it from internal to AD and set the context. Once the enhancement is done, this will be unnecessary.
Senior Software Developer
Global Ministry Center - Church of the Nazarene
I think what is happening is: A prospect is matriculated and then the team goes to the academics and gives them a username.
Since they assigned a username in academics, the LDAP and OU is correct when they go to the system admin so there is no need to save and return because it is all correct. So, they just hit return instead of save (as they should when not changing any info). However, although all the requirements are met to create in AD (no check box, in OU, and LDAP account), they do not get made until they hit “save and return”.
Although they should be able to learn to “save and return”, it seems to allow for extra chance for user error since the settings are already good and do not need to be “save”d. Does that make sense?
Stephen Porter
Nazarene Theological Seminary
No, but if clicking “save and return” gets them through, have them do that.
Senior Software Developer
Global Ministry Center - Church of the Nazarene
They shouldn’t have to click save is the data is already there which is where the bug is. It is confusing to the user and will cause errors and support calls. (It already has and is hard to track down.)
Stephen Porter
Nazarene Theological Seminary
This would take longer to hunt down and fix than the actual enhancement, which will make this one moot when complete.
Senior Software Developer
Global Ministry Center - Church of the Nazarene