Child pages
  • GEMS Maintenance Notes
Skip to end of metadata
Go to start of metadata

Incorporating eApp Data

Once an application has been created in GEMS, its IU Application Number can be used to link to eApp form data in DSS_RDS.ADM_CUR_APPL_RSPNS_GT. For instance, eApp accepts four phone numbers using ADM_APPL_QSTN_ID field values of:

  • cellPhone
  • homePhone
  • permanentPhone
  • workPhone

and allows a preferred phone to be indicated using value phonePrefered with ADM_APPL_VAL_TXT field of, for instance 'CELL'.

Names from eApp

GEMS Preferred_Name uses eApp 'preferFirstName'.

eApp allows for multiple "other name under which credentials may arrive". GEMS stores only one other name; if multiple names are given, selection ordering is undefined.

Test Score Alerts

New Test Score Alerts (a list of applications for which new scores have been received) are emailed to the Info and CS admissions secretaries (Cheryl and Shelly) daily by 2 Nintex workflows, New_GRE_TOEFL_INFO and New_GRE_TOEFL_CSCI.


Because the work is actually divided by building rather than by department, Shelly gets all CS, plus Bio MS and Security MS. Due to a limitation in CAML Query Schema (no logical NOT, and no NotContains), Bio and Security alerts are filtered only in the New_GRE_TOEFL_CSCI workflow. The workflow schedules are set to run CSCI 20 minutes before INFO, so that Bio and Security alerts are caught, routed to CS, and marked as done before the INFO workflow runs.

Cheryl has requested that the INFO workflow run daily, rather than only on workdays, so because of the scheduling requirement above, the CSCI workflow cannot be limited to workdays only.

Better fix for above

Fixed the scheduling issue described above by linking New_GRE_TOEFL_INFO to the end of New_GRE_TOEFL_CSCI. The quirk in this is that the Nintex schedule lists only New_GRE_TOEFL_CSCI, but the workflow history list shows both, with overlapping times.

Test Score Reports

A test score report generation feature was added to the TestScoreFeed. It builds GRE and TOEFL tables on top of a Word document prototype and then saves the documents in pdf format and copies the pdf's to GEMS.

Individual score reports are generated and placed in student document folders, and a cumulative report document for printing is generated, for both CSCI and INFO. The cumulative documents (.pdf) are placed in the GEMS 'Documents' library to be printed. Once printed, the .pdf should be deleted. As long as the .pdf is not deleted, additional reports will continue to be appended. (This is actually done by keeping local copies of the cumulative .docx files and checking existence of the GEMS .pdf's.)

Temporary files (both .docx and .pdf) are kept in local directory C:\\GEMS\Documents. This folder must be writeable by user ADS\soicgems.

CSCIScoreReports.docx, INFOScoreReports.docx, and TestResultsProto.docx must exist in C:\\GEMS\Documents and must be writeable by user ADS\soicgems.

( Skull&CrossBones plus Radiation Trifoil )

The report generation process runs Word from a scheduled task as user ADS\soicgems. To make this work in Windows Server 2008 R2 the folder 'Desktop' MUST be present in both these locations (it is not there by default), with specific permissions for soicgems:



The System32 path is required, even though we are using 64-bit Word and 64-bit Windows Server.???

Credit to H Ogawa, in

New IU Email Alerts

Alerts are mailed to the Info and CS admissions secretaries (Cheryl and Shelly) daily by 2 Nintex workflows, New IU_Email Alert INFO and New IU_Email Alert CSCI when an IU email address is added to an application.

Handling is similar to that described above for Test Score Alerts.

Passing Dates Into SharePoint From Code

When using SharePoint List Service to feed dates to a SharePoint 'Date and Time' field, dates have to be converted to strings, since they must be inserted into a command string.  SharePoint requires the string to use the format shown in this example: 



If List Service code is ported to Client Object Model (COM), this example will succeed:

AppListItem["Submitted_Date"] = System.DateTime.Now.ToString("yyyy-MM-ddTHH:mm:ssZ");

However, the resulting date in SharePoint will be off by one day (earlier)! I have not found a string format that yields the correct value.

The correct way to pass a date into SharePoint using COM is as type DateTime rather than as a string:

AppListItem["Submitted_Date"] = System.DateTime.Now;

  • No labels