====== Checklist: Custom Work ======

===== Key =====
  * = needs to be done, status unknown
  * :-) = is finished

===== Items =====
==== Need Fixing ====

  * None

==== Need Testing ====

  * :-) Documents not able to be downloaded / viewed / whatevered on random machines. A lot of machines can view them all, but some machines can not view all documents.
    * FIXME **Update:** This might be fixed. More testing needs to insue.
    * **Update:** We attempted to chase this crucial bug down while Eric was here, but were unsuccessful in the end. It may have something to do with how our network is setup. UMBCs network may be blocking or stopping communications of some kinda. Because we could not pinpoint it for certain though, and I have asked our professionals, I do not know where to go next.
    * **UPDATE:** Jeremy seemed to think this was because of server side compression (for speed) of content that came default with apache. He turned off the compression in an options file.
  * :-) CollegeNET application imports via shared ParaDocs Samba drive. See Collegenet Import wiki for details on what this process does. Directory currently called 'cnetimport'.
    * FIXME **Update:** Test some more specifically for EDI_DE
  * :-) Scanner communication with server
    * :-) Posting service auto start workflowing once posted is not working (background: workflows are assigned special auto-start queries; these auto-start queries may not be being checked properply)
      * FIXME **Update:** CMSC specific. KEEP TESTING
    * :-) Correct Group selection on posting client. "\" characters appeared after the group names. Eric thought it may be attributable to changing databases from Oracle -> Postgres. 

==== Done ====

  * :-) T_Import custom-created table; Who loads data and where will it be in the future for imports? The T_Import table is currently resident on the paradocs server and acts as a local import source of applicant personal data (when looking up a applicants on the scanning machines). The data comes from the UMBC SIS Shadow DB - //added by Nick & Eric// There is a process on the sun paradocs box that pulls SIS data into the T_Import table.
    * :-) Sweeper that updates the profile field labeled 'status' on applications is not being updated; See [[http://umbc.edu/gradbusiness/techdocuments/systems/paradocs/umbc_custom_setup#status_field|Status Field]] for background. The sweeper updates the status nightly from UMBCs SIS information, which may lay on the T_IMPORT table and updates the FAT table; it is run nightly by cron
    * **UPDATE** Jeremy is working on this, handing it off to Bryan
    * **UPDATE** Bryan thinks that he is close to solving this problem, he needs a login for the oracle shadow SIS in order to ODBC in
  * :-) Custom workflow fields. In the backend database table PARADOCS_WORKFLOW_MASTER or WORKFLOW_MASTER, there were 3 custom fields that were added. The fields are named: **LASTNAME**, **TERM**, and **OBJ**. The old (live) system has them, the new (test) system does not. The additional fields may not be needed, because the new system appears to show those fields in its workflow frame. **Verification that these 3 fields are not needed may be all that is required.**
  * :-) Correct bolding of new workflow documents
    * :-) Bold when workflow first starts
    * :-) Bold when workflow goes to a new step
  * :-) The GS_Decision document needs to be automatically created each time an application is posted. - //added by Eric//
  * :-) Thumbnails, there is none; - //added by Eric//
  * :-) (from a user perspective) Profile Field dropdowns do not show. There is one drop down of finite choice for the status field. It does not show. Database brought over incorrectly? brought up by Marie Ghazanfari - //added by Eric//
    * :-) (from a user perspective) All profile fields are editable by users. We would only like certain ones to be editable, and they worked correctly in the past implementation. Can this be done by me by checking and changing settings in the 'Manage Profile Fields' admin tool?
    * :-) **Update:** System has to be re-administered at time of migration; profile fields have to be manually brought over from old format to new in the Admin Utility.
  * :-) memo locking is not working; all users seem to be able to be able to unlock - /added by Eric, Nick, Emanuel/
  * :-) No content search in "add shared query" - /added by Eric/
  * :-) Bug when creating a new workflow with multiselect all and trying to pass a created workflow through the steps we made. - //added by Eric, Nick, Emanuel//
    * **Update:** Running a workflow with a multiple-all task behaves as if it is a multiple-any task; See the vacation request que for an example
    * **Update:** Bryan updated the code to the newest version and it now works