or a law displays as double slashes “\\” Word Processor characters such as commas and apostrophes are not transferring to SJS; rendering as special characters SJS not accepting 30+ bit characters sets found in MS Word Use Text Pad or Note Pad, type the missing narrative, copy, and then paste into the narrative User prompted by Windows Internet Explorer whenever navigating away from the page, that the page is not saved. User didn’t save changes and receives the following error: Cancel to save changes. Click ok to NOT save changes SJS Record Numbers are being skipped 8.0 skips SJS Record Numbers more than desired Bug defect in 707 that would cause an incident number to get skipped. Sequences of AI’s and SDEP’s increment by 4’s. Contracted DBA support fixed one but not the other…existing QC ticket screen is displaying “Unable to Access SJS 8.0 – HTTP Status 404. Requested resource is not available Restart SJS services by clicking on Control administrative tools, and services. Stop services in the following order - Apache Tomcat Service and then OracleserviceSJS. Restart OracleserviceXE. Restart Apache Tomcat service. If this does not restart SJS, have user call back and open ticket for Technical Support. Date defaults to 1899 when only entering “Time” Time was entered manually w/out adding a date. Use Calendar Control for entering time and date. User is unable to edit a Patrolman’s Incident Narrative and can only view it. Patrolman was not to SGT’s Boss Tree. Add the Patrolman to the Sgt’s boss tree, in the Reporting Officer’s section. This will the Sgt to edit the Patrolman’s narrative. (Also, see Installation Issues) Local Law displays as double slashes “\\” Restart the Apache Tomcat Service.
Trying to seal a local law and received message “Load seal failed, ORA 01438.” At this time, SJS is unable to seal a “Local Law”. The user will need to remove the local law and add it to sealing narrative or replace the local law with the state version and then seal. Unable to seal a case for Inactive User. User does not have a 7.0 user record The Agency’s administrator will need to make an account in 7.0. Link 7.0 account to 6.5 Officer record Edit the officer record and add the sealer as a superior officer. Seal case. NOTE: Deactivate the old user account at a future date to ensure all accounted for. Seal Record was unable to DELETE Person(s) from Incident Record – secmx_master_name_delete to delete incident record. User doesn’t have the right to delete a person master in their User Management profile. The SJS administrator needs to do the following: Sign in as fixer7 Click on Maintenance, User Manager. Select the user that will be the ability to delete. Click on the quick jump button labeled ‘Master Names’ Check Delete check box and save. Incident Based Reporting (IBR) Setup Administrative (fixer 7) The SJS administrator signs in using fixer 7. The administrator then clicks on Maintenance, Local Customizations, Agency, Edit Agency – ensure agency is set up for IBR: “IBR” select “Yes”. Enter IBR Start Date: The user will need to contact the IBR support group to obtain this date, by calling the 1-800-262-3257 or sending an email to the group dcjs.dl.ibrsupport@dcjs.ny.gov