| Incident Reports |
| Name |
Title |
Default Value |
Description |
| SP_NewRepNum |
Incident: Prefill Report Number |
"N" for "No" |
Prefill the Report Number with the next available Incident Number, when Adding a New Incident Report:
- "Y" for "Yes"
- "N" for "No"
|
| SP_IRepDate |
Incident: Prefill Date Reported |
"L" for "Last Date" |
Prefill the Date Reported when Adding a New Incident Report with:
- "C" for "Current Date"
- "L" for "Last Date Entered"
- "N" for "No Value" (Leave Date Empty)
|
| SP_GuideIRep |
Incident: Guide User during Add/Edit |
"A" for "Adding" |
Guide the Users through entering Incident Details:
- "A" for "only when Adding new Incidents"
- "E" for "only when Editing Incidents"
- "B" for "Both, when Adding and Editing Incidents"
- "N" for "Never" (Don't Guide User at all)
|
| SP_IRepLoc |
Incident: Add Locations |
"Y" for "Yes (Required)" |
Enter Incident Locations:
- "Y" for "Yes" (Locations are Always Required)
- "N" for "No" (Skip Locations)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepFC |
Incident: Add File Classes |
"Y" for "Yes (Required)" |
Enter Incident File Classes/Offenses:
- "Y" for "Yes" (Offenses are Always Required)
- "N" for "No" (Skip Offenses)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepPers |
Incident: Add Persons/Names |
"O" for "Optional (Ask)" |
Enter Incident Persons/Names:
- "Y" for "Yes" (Persons are Always Required)
- "N" for "No" (Skip Persons)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepVeh |
Incident: Add Vehicles |
"O" for "Optional (Ask)" |
Enter Incident Vehicles:
- "Y" for "Yes" (Vehicles are Always Required)
- "N" for "No" (Skip Vehicles)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepDMSF |
Incident: Add Documents or Forms |
"O" for "Optional (Ask)" |
Enter Incident Documents or Forms:
- "Y" for "Yes" (Documents are Always Required)
- "N" for "No" (Skip Documents)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepProp |
Incident: Add Property Items |
"O" for "Optional (Ask)" |
Enter Incident Property Items:
- "Y" for "Yes" (Property is Always Required)
- "N" for "No" (Skip Property)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepEvid |
Incident: Add Evidence Items |
"N" for "No (Skip It)" |
Enter Incident Evidence Items:
- "Y" for "Yes" (Evidence is Always Required)
- "N" for "No" (Skip Evidence)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepTick |
Incident: Add Tickets |
"O" for "Optional (Ask)" |
Enter Incident Tickets:
- "Y" for "Yes" (Tickets are Always Required)
- "N" for "No" (Skip Tickets)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepHS |
Incident: Add HotSheets |
"N" for "No (Skip It)" |
Enter Incident HotSheets:
- "Y" for "Yes" (HotSheets are Always Required)
- "N" for "No" (Skip HotSheets)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepPics |
Incident: Add Pictures |
"N" for "No (Skip It)" |
Enter Incident Pictures:
- "Y" for "Yes" (Pictures are Always Required)
- "N" for "No" (Skip Pictures)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepNarr |
Incident: Add Narratives |
"O" for "Optional (Ask)" |
Enter Incident Narratives and Supplements:
- "Y" for "Yes" (Narratives are Always Required)
- "N" for "No" (Skip Narratives)
- "O" for "Optional" (Ask User what to do)
|
| SP_IRepNIBR |
Incident: Add MICR (NIBRS) |
"O" for "Optional (Ask)" |
Enter MICR (NIBRS) Data for MICR-reportable Incident Reports:
- "Y" for "Yes" (MICR Data is Always Required)
- "N" for "No" (Skip MICR Data)
- "O" for "Optional" (Ask User what to do)
|
| SP_SortInvolv |
Incident: Sort Order for Persons |
"CVSATDWOPX" |
Determine the order in which Persons are listed and printed, based on the Person's Involvement(s) and Names. The default order is:
- "C" for "Complainants"
- "V" for "Victims"
- "S" for "Suspects"
- "A" for "Arrested"
- "T" for "Ticketed"
- "D" for "Drivers"
- "W" for "Witnesses"
- "O" for "Owners"
- "P" for "Passengers"
- "X" for "Others"
- Finally all other Persons with user-defined Involvements.
|
| Tickets |
| Name |
Title |
Default Value |
Description |
| SP_NewTickNum |
Ticket: Prefill Ticket Number |
"N" for "No" |
Prefill the Ticket Number with the next available (Ticket Type-specific) Ticket Number, when Adding a New Ticket:
- "Y" for "Yes"
- "N" for "No"
|
| SP_TickDate |
Ticket: Prefill Date |
"L" for "Last Date" |
Prefill the Ticket Date when Adding a New Ticket with:
- "C" for "Current Date"
- "L" for "Last Date Entered"
- "N" for "No Value" (Leave Date Empty)
|
| SP_GuideTick |
Ticket: Guide User through New Add |
"P" for "Paper Order" |
Guide the Users through entering Ticket Details:
- "D" for "in Display Layout order"
- "P" for "in Paper Ticket Layout order"
- "N" for "Never" (Don't Guide User at all)
|
| SP_TickChrg |
Ticket: Add Charges |
"Y" for "Yes (Required)" |
Enter Ticket Charges:
- "Y" for "Yes" (Charges are Always Required)
- "N" for "No" (Skip Charges)
- "O" for "Optional" (Ask User what to do)
|
| SP_TickLoc |
Ticket: Add Location |
"Y" for "Yes (Required)" |
Enter Ticket Location:
- "Y" for "Yes" (a Location is Always Required)
- "N" for "No" (Skip Location)
- "O" for "Optional" (Ask User what to do)
|
| SP_TickPers |
Ticket: Add Person/Name |
"O" for "Optional (Ask)" |
Enter Ticket Person:
- "Y" for "Yes" (a Person is Always Required)
- "N" for "No" (Skip Person)
- "O" for "Optional" (Ask User what to do)
|
| SP_TickVeh |
Ticket: Add Vehicle |
"O" for "Optional (Ask)" |
Enter Ticket Vehicle:
- "Y" for "Yes" (a Vehicle is Always Required)
- "N" for "No" (Skip Vehicle)
- "O" for "Optional" (Ask User what to do)
|
| Hot Sheets |
| Name |
Title |
Default Value |
Description |
| SP_FillHSLDT |
HotSheet: Prefill Log Entry Date/Time |
"Y" for "Yes" |
Prefill New HotSheet Log Entries with Current Date/Time values:
- "Y" for "Yes" (Prefill with Current Date and Time)
- "N" for "No" (Leave fields empty)
|
| SP_HSLogOrder |
HotSheet: Log Entry Print (Sort) Order |
"A" for "Ask User" |
Sort Order for HotSheet Log Entries when Printing:
- "A" for "Ask User before Printing"
- "D" for "Sort by Date and Time"
- "N" for "Sort by leg Entry Number"
|
| Narratives |
| Name |
Title |
Default Value |
Description |
| SP_NarrSpace |
Narrative: Line Spacing Factor |
"100" for "Single Line" |
Line Spacing Factor in percent, based on the selected font. Values can be any number from "0" to "9999",
but numbers below "50" and above "200" are usually not sensible. Examples:
- "80" for "80% (Compressed Line Spacing)
- "100" for "100% (Normal / Single Line Spacing)
- "150" for "150% (Wide / One and a Half Line Spacing)
- "200" for "200% (Double / Two Lines Spacing)
|
| SP_Tab2Spaces |
Narrative: Number of Spaces for Tabs |
"10" for "10 Spaces" |
Number of Spaces used to replace Tabs (for Indentations of Paragraphs) in Narratives. Values can be any number from "0" to "999",
but numbers above "30" are usually not sensible. |
| SP_AutoSave |
Narrative: Auto-Save |
"40" for "40 Characters" |
Number of characters (or keystrokes) to be entered in Narratives, before the Auto-Save feature saves a new backup of the text.
Values can be any number from "0" to "999", with "0" disabling the automatic backup feature completely. |
| SP_OrigTmplt |
Narrative: Template for Originals |
"N" for "None" |
Prefill empty Original Narratives with a Template text:
- "N" for "No Template" (Leave empty)
- "C" for "File Class-based" (depends on 1st File Class)
- "F" for "File-based" (the text is read from the file "OrigNarr.txt" in the "Transfer" directory)
- "U" for "User-specific" (the text is read from the file "Orig_UID.txt" in the "Transfer" directory, where "UID" stands for each User's Clerk ID)
|
| SP_SuppTmplt |
Narrative: Template for Supplements |
"N" for "None" |
Prefill empty Supplemental Narratives with a Template text:
- "N" for "No Template" (Leave empty)
- "C" for "File Class-based" (depends on 1st File Class)
- "F" for "File-based" (the text is read from the file "SuppNarr.txt" in the "Transfer" directory)
- "U" for "User-specific" (the text is read from the file "Supp_UID.txt" in the "Transfer" directory, where "UID" stands for each User's Clerk ID)
|
| Persons / Names |
| Name |
Title |
Default Value |
Description |
| SP_PersPhone |
Person: Add Phone Numbers |
"O" for "Optional (Ask)" |
When Adding a new Person/Name, add Phone Numbers and EMail Addresses:
- "Y" for "Yes" (Phone Numbers are Always Required)
- "N" for "No" (Skip Phone Numbers)
- "O" for "Optional" (Ask User what to do)
|
| SP_PersPhDesc |
Person: Add Physical Descriptions |
"O" for "Optional (Ask)" |
When Adding a new Person/Name, add Physical Descriptions:
- "Y" for "Yes" (Physical Descriptions are Always Required)
- "N" for "No" (Skip Physical Descriptions)
- "O" for "Optional" (Ask User what to do)
|
| SP_PersPics |
Person: Add Pictures |
"N" for "No (Skip It)" |
When Adding a new Person/Name, add Photos or Pictures:
- "Y" for "Yes" (Person Pictures are Always Required)
- "N" for "No" (Skip Person Pictures)
- "O" for "Optional" (Ask User what to do)
|
| SP_AddrHist |
Person: Allow Address History records |
"Y" for "Yes" |
When Selecting an existing Person, Ask if an Address History record should be created:
- "Y" for "Yes"
- "N" for "No" (Don't Ask)
|
| SP_PersAlias |
Person: Allow Alias records |
"Y" for "Yes" |
When Selecting an existing Person, Ask if an Alias record should be created:
- "Y" for "Yes"
- "N" for "No" (Don't Ask)
|
| SP_AssignPKey |
Person: ID can be Assigned/Changed |
"N" for "No" |
Allow Users to Assign/Change Person (Student) ID Numbers:
- "Y" for "Yes" (User-assigned Person/Student IDs)
- "N" for "No" (System-assigned Person IDs)
|
| SP_PKCaption |
Person: ID Caption |
"Person ID" |
Caption for Person ID Numbers. Examples are: "Person ID" or "Student ID". |
| SP_ResetPersF |
Person: Always Reset Search Field Values |
"N" for "No (Keep Values)" |
Reset (Clear) all Search Name Field Values, every time Find is selected:
- "Y" for "Yes" (Selecting Find will Reset Values)
- "N" for "No" (Values are available between Searches)
|
Note: The Search/Find/Filter Values can be Reser (Cleared) at any time by pressing
the "Reset" button! |
| SP_ListNames |
Person: List all Names when Searching |
"N" for "Not Exact" |
When searching for Persons/Names, show a List of all Persons/Names to select from:
- "A" for "Always" (Even if a (single) match was found)
- "N" for "Not Exact" (If no (single) exact match was found)
- "M" for "Multiple" (Only when multiple (partial) or no matches were found)
|
| Phone Numbers |
| Name |
Title |
Default Value |
Description |
| SP_AreaCode |
Phone: Default (Department) Area Code |
"888" for "Demo Department" |
Area Code of the Department/Municipal, which can be used as the default Area Code for new Phone Numbers. |
| SP_PACPreFill |
Phone: Prefill Area Code |
"Y" for "Yes" |
Prefill the Area Code with the Default Area Code, when adding new Phone Numbers:
- "Y" for "Yes"
- "N" for "No"
|
| SP_PACLength |
Phone: Area Code Field Length |
"3" (in North America) |
Length of the Area Code input value. In North America, Area Codes consist of 3 digits. Maximum length is 6 digits. |
| SP_PACPicture |
Phone: Area Code Field Picture |
"@R (999)" |
Input Picture for Area Codes. This should match the Area Code Field Length.
Note: Please contact EJS OnSite Support for valid Syntax options! |
| SP_PPNLength |
Phone: Phone Number Field Length |
"7" (in North America) |
Length of the Phone Number input value. In North America, Phone Numbers consist of 7 digits. Maximum length is 10 digits. |
| SP_PPNPicture |
Phone: Phone Number Field Picture |
"@R 999-9999" |
Input Picture for Phone Numbers. This should match the Phone Number Field Length.
Note: Please contact EJS OnSite Support for valid Syntax options! |
| Arrests |
| Name |
Title |
Default Value |
Description |
| SP_ArrestDate |
Arrest: Prefill Date |
"I" for "Incident Date" |
Prefill the Arrest Date when Adding a New Arrest with:
- "I" for "Incident Date"
- "C" for "Current Date"
- "N" for "No Value" (Leave Date Empty)
|
| SP_ArrestText |
Arrest: Prefill Notes from Template |
"N" for "No" |
Prefill the Arrest Disposition Notes from the file "Arrest.txt" in the "Transfer" directory:
- "Y" for "Yes"
- "N" for "No" (Leave Notes Empty)
|
| SP_UniqueArr |
Arrest: Enforce Unique Arrest Codes |
"Y" for "Yes" |
Enforce Unique Arrest Charge Codes for Offenders in Incident Reports:
- "Y" for "Yes" (Only allow unique Charges)
- "N" for "No" (Allow multiple, identical Charges for the same Offender in the same Incident Report)
|
| Property Items / Property Receipts |
| Name |
Title |
Default Value |
Description |
| SP_PropRecipt |
Property: Print Property Receipts |
"Y" for "Yes (Print)" |
Automatically Print Property Receipts when they are created:
- "Y" for "Yes" (Automatically Print Property Receipt)
- "N" for "No" (Show Preview of Property Receipt)
|
| SP_PRecCopies |
Property: Number of Prop. Receipt Copies |
"1" for "Single Copy" |
Specifies the Number of Property Receipt Copies that are printed, when creating a new Property Receipt.
Values can be any number from "1" to "9". |
| SP_PropLabels |
Property: Print Evidence Labels |
"Y" for "Yes (Print)" |
Automatically Print Labels for Evidence Items when creating Property Receipts:
- "Y" for "Yes" (Automatically Print Labels)
- "N" for "No" (Don't Print Labels)
|
| SP_PrntPREmpF |
Print: Empty Property Fields on Receipt |
"N" for "No (Only Content)" |
Print all (even empty) Property Fields on Property Receipts:
- "Y" for "Yes" (Print all (even empty) Fields)
- "N" for "No" (Only Print Fields with Content)
|
| SP_PrntPRETBC |
Print: Barcode for Tag Number on Receipt |
"Y" for "Yes (Print Barcode)" |
Print Evidence Tag Numbers also as Barcodes on Property Receipts (if Barcodes are installed):
- "Y" for "Yes" (Print Evidence Tag also as Barcodes)
- "N" for "No" (Print Evidence Tag only as Number )
|
| SP_PrntPRPics |
Print: Pictures on Property Receipt |
"Y" for "Yes (Print Picture)" |
Print the Property Item's Picture on Property Receipts (if one exists):
- "Y" for "Yes" (Print Pictures on Property Receipt)
- "N" for "No" (Don't Print Property Pictures)
|
| SP_AddPropRep |
Property: Allow Adding of Incidents |
"N" for "No (Must Exist)" |
Allow the Adding of New Incident Reports through the Central Property module, if an Incident with the entered Incident Number doesn't exist:
- "Y" for "Yes" (Allow Creation of new Incident Reports)
- "N" for "No" (Incident Reports must already Exist)
|
| Evidence Management / Property Room |
| Name |
Title |
Default Value |
Description |
| SP_ETNDefault |
Evidence: Tracking Number Default Value |
"N" for "Nothing" |
Prefill the Evidence Tracking Number when Adding a New Evidence Item with:
- "N" for "Nothing" (Leave field empty)
- "P" for "Property Item Number"
- "E" for "Evidence Item Number"
- "T" for "Tag Number"
|
| SP_ETNLength |
Evidence: Tracking Number Field Length |
"10" (maximum) |
Length of the Evidence Tracking Number input value. Maximum length is 10 characters. |
| SP_ETNPicture |
Evidence: Tracking Number Field Picture |
"@K 9999999999" |
Input Picture for Evidence Tracking Number. This should match the Evidence Tracking Number Field Length.
Note: Please contact EJS OnSite Support for valid Syntax options! |
| SP_AddEvidRep |
Evidence: Allow Adding of Incidents |
"N" for "No (Must Exist)" |
Allow the Adding of New Incident Reports through the Central Evidence/Property Room module, if an Incident with the entered Incident Number doesn't exist:
- "Y" for "Yes" (Allow Creation of new Incident Reports)
- "N" for "No" (Incident Reports must already Exist)
|
| SP_HTTPServer |
Evidence: Web Server Name/IP Address |
"127.0.0.1" or "localhost" |
Internet (or Intranet) Domain Name or IP Address for built-in (Evidence) Web Server for Remote Evidence Management. |
| SP_HTTPPort |
Evidence: Web Server Port Number |
"80" for "HTTP Port" |
Port Number for built-in (Evidence) Web Server for Remote Evidence Management. The default is the well-known port for HTTP (Web Access). |
| Internal Document Management System |
| Name |
Title |
Default Value |
Description |
| SP_PreViewDoc |
Documents: Use Internal Preview Option |
"Y" for "Yes (Selected)" |
Default value for displaying Documents with the "Internal" Preview feature, when adding a new Document record:
- "Y" for "Yes" (Internal Preview option will be selected)
- "N" for "No" (Internal Preview option won't be selected)
|
| Printing |
| Name |
Title |
Default Value |
Description |
| SP_RepHead1 |
Print: Incident Report Header 1 |
"EJustice Solutions, LLC -- (248) 782-6404" |
Text to be printed in the 1st (upper) Header Line on top of (Incident) Reports, Property Receipts, Bicycle Registrations, etc.
Usually the Department's Name, often followed by the Phone Number. |
| SP_RepHead2 |
Print: Incident Report Header 2 |
"3600 Green Court - Suite 780, Ann Arbor, MI 48105" |
Text to be printed in the 2nd (lower) Header Line on top of (Incident) Reports, Property Receipts, Bicycle Registrations, etc.
Usually the Department's postal/mailing Address. |
| SP_PrintHead |
Print: Incident Report Header Text |
"Y" for "Yes (Print Text)" |
Print (Incident) Report Header Text Lines on top of Reports, Property Receipts, Bicycle Registrations, etc.:
- "Y" for "Yes" (Print both Report Header Text Lines)
- "N" for "No" (Don't Print the Report Header Text Lines)
|
| SP_HeadrLeft |
Print: Incident Report Header Start Left |
"0" for "0.0 mm" |
Offset from Left for (Incident) Report Header Text Lines, measured in tenths of a millimeter. |
| SP_HeadrWidth |
Print: Incident Report Header Width |
"1500" for "150.0 mm" |
Width of (Incident) Report Header Text Lines, measured in tenths of a millimeter.
The maximum width is limited by the width of the page and the start of the Header Box on the top right, which is 48.0 mm wide. |
| SP_ReportLogo |
Print: Incident Report Logo File Name |
"EJS_LOGO.JPG" |
Name of the Picture File with the Department's (Incident) Report Header Logo. This file MUST be located in the application's "Programs" directory and must be in a valid graphics format (JPG/PNG/GIF/BMP). |
| SP_PrintLogo |
Print: Incident Report Logo on Header |
"N" for "No Logo" |
Print Department's Incident Report Logo on (Incident) Report Headers:
- "Y" for "Yes" (Print the Logo in Report Headers)
- "N" for "No" (Don't Print the Logo in Report Headers)
|
| SP_LogoLeft |
Print: Incident Report Logo Start Left |
"0" for "0.0 mm" |
Offset from Left for (Incident) Report Header Logo, measured in tenths of a millimeter. |
| SP_LogoWidth |
Print: Incident Report Logo Width |
"200" for "20.0 mm" |
Width of (Incident) Report Header Logo, measured in tenths of a millimeter.
The maximum width is limited by the width of the page and the start of the Header Box on the top right, which is 48.0 mm wide. |
| SP_LogoBottom |
Print: Incident Report Logo Bottom |
"2" for "0.2 mm" |
Offset from Bottom of Header for (Incident) Report Header Logo, measured in tenths of a millimeter. |
| SP_LogoHeight |
Print: Incident Report Logo Height |
"150" for "15.0 mm" |
Height of (Incident) Report Header Logo, measured in tenths of a millimeter.
The maximum height is (currently) limited by the height of the Report Header, which is only 15.0 mm! |
| SP_ScaleLogo |
Print: Incident Report Logo Scaling |
"P" for "Proportional" |
Scale Logo to fit into the available space, which is determined by the selected Report Logo Width and Height:
- "P" for "Scale Proportional" (Keep Proportions)
- "S" for "Stretch/Shrink to fit" (Possibly Distorted)
- "N" for "No Scaling" (Print Original Size)
|
| SP_PrntSigned |
Print: "Signed:" or "Officer:" on Footer |
"S" for "Signed" |
Footer options for Incident Report and Officer Daily Print-Outs:
- "S" for "Signed:" (with room for the Officer's Signature)
- "O" for "Officer:" (followed by the Officer's Name)
|
| SP_PrntSepLns |
Print: Separator Lines in Incidents |
"N" for "No Lines" |
Print thin Separator Lines between individual Detail Entries, such as individual Names, Vehicles, Property Items, etc. in Incident Reports:
- "Y" for "Yes" (Print thin Item Separator Lines)
- "N" for "No" (Don't Print Item Separator Lines)
|
| SP_PrntLocUse |
Print: Local Use Fields in Incidents |
"Y" for "Yes (Print)" |
Print the Local Use fields in the Header of "Internal" (not redacted) Incident Reports:
- "Y" for "Yes" (Print Local Use fields)
- "N" for "No" (Skip Local Use fields)
|
| SP_PrntLocatn |
Print: Location Fields in Incidents |
"C1SN" |
Determine which of the Location fields (that aren't empty) will be printed in Incident Reports:
- "C" for "Print Common Name"
- "1" for "Print Address 1"
- "2" for "Print Address 2"
- "S" for "Print Section"
- "N" for "Print Neighborhood"
|
| SP_PrintAll |
Print: Pre-Select All Incident Items |
"Y" for "Yes (Select All)" |
Pre-Select All available Incident Report Details in the Print Report Selection Dialog:
- "Y" for "Yes" (Pre-Select all Incident Report Details)
- "N" for "No" (Pre-Select Nothing)
This setting doesn't affect Incident Report Previews, which always pre-selects all details. |
| SP_PrintPics |
Print: Incident Pictures |
"N" for "No (Skip It)" |
Default value for "Print Incident Pictures" in Incident Report Print Selection Dialog (as well as Previews):
- "Y" for "Yes" (Select/Print all Pictures)
- "N" for "No" (Don't Select/Skip Pictures)
|
| SP_PrintDVF |
Print: Domestic Violence Form |
"N" for "No (Skip It)" |
Default value for "Print Domestic Violence Form" in Incident Report Print Selection Dialog (as well as Previews):
- "Y" for "Yes" (Select/Print DV Form)
- "N" for "No" (Don't Select/Skip DV Form)
|
| SP_PrntRedact |
Print: Default Print Redaction Mode |
"I" for "Internal (Full)" |
Default Redaction Mode Selection for Incident Report Print Selection Dialog (and Previews):
- "I" for "Internal" (Full Report, with no redactions)
- "F" for "FOIA" (FOIA Report, with mainly Names of Juveniles as well as DOBs, Social Security, Ops Numbers and Addresses redacted)
- "P" for "Public" (Public Report, with all Names and Personal Identifiable Information redacted)
|
| SP_PrntPSSNo |
Print: Social Security No. in Incidents |
"Y" for "Yes (Print)" |
Print Person's Social Security Numbers in Incident Reports:
- "Y" for "Yes" (Print Social Security Numbers)
- "N" for "No" (Skip Social Security Numbers)
|
| SP_PrntPDLNo |
Print: Driver's License No. in Incidents |
"Y" for "Yes (Print)" |
Print Person's Driver's License (Ops or ID) Numbers in Incident Reports:
- "Y" for "Yes" (Print Driver's License Numbers)
- "N" for "No" (Skip Driver's License Numbers)
|
| SP_PrntPPhone |
Print: All Phone Numbers in Incidents |
"Y" for "Yes (Print All)" |
Default value for "Print all Phone Numbers" in Incident Report Print Selection dialog (and Previews):
- "Y" for "Yes" (Print All Phone Numbers)
- "N" for "No" (Print Only Main Phone Number)
This selection might be disabled by conflicting Redaction Mode default settings. |
| SP_PrntPAlias |
Print: Alias Information in Incidents |
"Y" for "Yes (Print All)" |
Default value for "Print Alias Information" in Incident Report Print Selection dialog (and Previews):
- "Y" for "Yes" (Print all Aliases, Nicknames, etc.)
- "N" for "No" (Skip Aliases, Nicknames, etc.)
This selection might be disabled by conflicting Redaction Mode default settings. |
| SP_PrntPNotes |
Print: Person Notes in Incidents |
"Y" for "Yes (Print)" |
Default value for "Print Person Notes" in Incident Report Print Selection dialog (and Previews):
- "Y" for "Yes" (Print Person Notes)
- "N" for "No" (Skip Person Notes)
This selection might be disabled by conflicting Redaction Mode default settings. |
| SP_ExportExtn |
Print: Extension for Export Files |
"PDF" for "PDFCreator" |
Extension for files created by the Export/Save (Printer) option, which should normally use the "PDFCreator" Printer Driver. |
| Gun Registration |
| Name |
Title |
Default Value |
Description |
| SP_GunAppDept |
Gun Reg: Department Name for Application |
"Demo Department" |
Department Name, as it should be printed on Gun Application/Registration Forms. This is only printed if the "SP_GunAppORI" parameter (see below) is set to "No"! |
| SP_GunVoidDay |
Gun Reg: Expires after Number of Days |
"10" for "10 Days" |
Number of Days the Gun Applications are valid. Used to calculate the "Expiration Date" on the Forms. |
| SP_GunRegDate |
Gun Reg: Allow Editing of Issue Date |
"N" for "No (Date Printed)" |
Allow the Editing of the Gun Registration Date Issued value:
- "Y" for "Yes" (The Date can be manually entered)
- "N" for "No" (The Date Issued is the Date Printed)
|
| SP_GunAppCnty |
Gun Reg: Print County Number (not Name) |
"N" for "No (Print Name)" |
Print the County Number (rather than the County Name) in the "County" field on Gun Application Forms:
- "Y" for "Yes" (Print the two-digit County Number)
- "N" for "No" (Print the full County Name)
|
| SP_GunAppORI |
Gun Reg: Print ORI Number (instead Name) |
"N" for "No (Print Name)" |
Print the Department's ORI Number (rather than the Gun Application Department's Name) in the "Department/ORI" field on
Gun Application Forms:
- "Y" for "Yes" (Print only the 9-character ORI Number)
- "N" for "No" (Print the Department Name, as defined above)
|
| Bicycle Registration |
| Name |
Title |
Default Value |
Description |
| SP_BRNPicture |
Bike Reg: License Number Field Picture |
"@K 99999999" |
Input Picture for Bicycle Registration License Numbers. The License Number can be up to 8 digits long.
Note: Please contact EJS OnSite Support for valid Syntax options! |
| SP_BikeRegExp |
Bike Reg: License Expiration Type |
"N" for "Never" |
Bicycle License Expiration options, which will be used to fill in the Expiration Date:
- "N" for "Never" (Licenses are valid forever. No Expiration Date)
- "F" for "Fixed Date" (All Licenses expire at a fixed Date, see below)
- "Y" for "End of Year" (All Licenses expire at December 31 of the License Year)
- "D" for "Date + 1 Year" (Licenses expire after one Year, on the Date Issued)
- "A" for "Any Date" (License Expiration Dates will be entered manually)
Only when the last option "A" for "Any Date" is selected, will the Expiration Date field be accessible.
In all other cases, the date value will be automatically updated and the field will be disabled. |
| SP_BikeRegNED |
Bike Reg: Fixed License Expiration Date |
(No Default Value) |
Next Bicycle License Expiration Date. This value is (only) used for "F"ixed Expiration Dates, and must be updated, if it changes on a regular basis. |
| SP_BikeRegFee |
Bike Reg: Default License Fee |
"0" for "$ 0.00 (No Fee)" |
Default value for License Fees. Any Value (in Cents) between "0" ($ 0.00) and "99999" ($ 999.99) is allowed. |
| SP_BRegCopies |
Bike Reg: Number of Bike License Copies |
"1" for "Single Copy" |
Specifies the Number of Bicycle License Copies that are printed, when adding or updating a License.
Values can be any number from "1" to "9". |
| Dispatch (Calls for Service) |
| Name |
Title |
Default Value |
Description |
| SP_DispIRep |
Dispatch: Add Incident from Dispatch Log |
"O" for "Optional (Ask User)" |
Allow, Require, or Prohibit the Adding of Incident Reports from Dispatch Log Entries:
- "A" for "Automatically" (Require and Create an Incident Report for each Dispatch Log Entry)
- "O" for "Optional (Ask User)" (Allow Adding of Incident Reports from a Dispatch Log Entry)
- "N" for "Never" (Disable Adding of Incident Reports from a Dispatch Log Entry)
|
| SP_DispIRepSh |
Dispatch: Show/Edit Incident Reports |
"O" for "Optional (Ask User)" |
Allow or Prohibit the Viewing and Editing of Incident Reports from Dispatch Logs Entries:
- "A" for "Automatically" (Update Incident Reports and allow Viewing/Editing of Dispatch Incident Reports)
- "O" for "Optional (Ask User)" (Allow Viewing, Updating, and Editing of Dispatch Incident Reports)
- "N" for "Never" (Disable Viewing, Updating, and Editing of Dispatch Incident Reports)
|
| SP_DispIRepFC |
Dispatch: Add File Class(es) to Incident |
"O" for "Optional (Ask User)" |
Allow, Require, or Prohibit the Adding of File Classes to Incident Reports from Dispatch Log Entries:
- "A" for "Automatically" (Require the addition of (at least) one File Class to Dispatch Incident Reports)
- "O" for "Optional (Ask User)" (Allow Adding of File Classes to Dispatch Incident Reports)
- "N" for "Never" (Don't Add File Classes to Dispatch Incident Reports)
|
| SP_DispIRepLo |
Dispatch: Add Location(s) to Incident |
"O" for "Optional (Ask User)" |
Allow, Require, or Prohibit the Adding of Locations to Incident Reports from Dispatch Log Entries:
- "A" for "Automatically" (Require the addition of (at least) one Location to Dispatch Incident Reports)
- "O" for "Optional (Ask User)" (Allow Adding of Locations to Dispatch Incident Reports)
- "N" for "Never" (Don't Add Locations to Dispatch Incident Reports)
|
| SP_DispDaily |
Dispatch: Add/Update Officer Daily |
"O" for "Optional (Ask User)" |
Allow the Updating of Dispatch Officer information from Officer Dailies:
- "A" for "Automatically" (Update Dispatch Officer from Officer Daily)
- "O" for "Optional (Ask User)" (Currently the same as "N"/"Never")
- "N" for "Never" (Disable any Officer Daily access)
This feature is currently only used to update the Dispatch Log Officer information from existing Officer Daily Logs,
but won't Create or Update any Officer Daily Logs! At a future time, a two-way interface to Officer Daily Logs might be added. |
| SP_DispIRepSt |
Dispatch: Incident Report Status |
"DISPATCH" for "Dispatch" |
Incident Status for Incident Reports Created from Dispatch Logs as well as Data Imports.
This must be a valid Code from the list of available Incident Report Status Lookup Parameters! |
| SP_DispIRepDS |
Dispatch: Canceled Incident Status |
"UNFOUNDED" for "Unfounded" |
Incident Status for Incident Reports Canceled by Dispatch Logs as well as Data Imports.
This must be a valid Code from the list of installed Incident Report Status Lookup Parameters! |
| SP_DispPrntRT |
Dispatch: Print Call Response Times |
"N" for "No (Skip It)" |
Print Average Call Response Times/Call Lengths on Dispatch Log Summary Reports:
- "Y" for "Yes" (Calculate and Print Average Times)
- "N" for "No" (Don't include Average Times)
|
| SP_DispBrKeys |
Dispatch: Allow Short Cuts on Browses |
"Y" for "Yes (Allow)" |
Allow Buttons and Function Keys to work for all Browse Tables or be limited to Dispatch Log Entries:
- "Y" for "Yes" (Short Cuts apply to active Browse Table)
- "N" for "No" (Short Cuts always apply to Dispatch Log Entries)
If the Short Cuts are limited to Dispatch Log Entries, then Adding, Editing and Deleting of
Shifts, Dispatchers, and Officers can only be done after opening
the corresponding detail dialogs, as the short cut keys and main dialog buttons will always only apply to the
Dispatch Log Entries. |
| SP_DispCritcl |
Dispatch: Critical Overdue Time |
"5" for "5 Minutes" |
Specifies the Number of Minutes that have to pass without a Response from a dispatched Officer, before (s)he is considered
Critically Overdue. Values can be any number from "0" to "999" and should
be less than the Dangerous Overdue Time (see below). A value of "0" will disable the Display of the
Critically Overdue Status. |
| SP_DispDanger |
Dispatch: Dangerous Overdue Time |
"10" for "10 Minutes" |
Specifies the Number of Minutes that have to pass without a Response from a dispatched Officer, before (s)he is considered
Dangerously Overdue. Values can be any number from "1" to "999" and should
be more than the Critical Overdue Time (see above). A value of "0" will disable the Display of the
Dangerously Overdue Status. |
| SP_DispUpdate |
Dispatch: Update/Refresh Interval |
"10" for "10 Seconds" |
Specifies the Interval in Seconds after which the Dispatch Logs are automatically updated when the user is idle and not in edit mode.
Values can be any number from "0" to "999". A value of "0" will disable the automatic Updates. |
| Officer Daily |
| Name |
Title |
Default Value |
Description |
| SP_DailyDate |
Daily: Prefill Date |
"L" for "Last Date" |
Prefill the Officer Daily Date when Adding a New Office Daily with:
- "C" for "Current Date"
- "L" for "Last Date Entered"
- "N" for "No Value" (Leave Date Empty)
|
| SP_DailyNoFDs |
Daily: Do Not allow Future Dates |
"Y" for "Yes (Check Dates)" |
Prevent (or Allow) adding of Officer Dailies for future Dates:
- "Y" for "Yes" (Check and prohibit future Dates in Officer Dailies)
- "N" for "No" (Allow adding of Officer Dailies for future Dates)
|
| SP_DailyEquip |
Daily: Use Daily Equipment Templates |
"Y" for "Yes (Enable)" |
Enable (or Disable) the use of Daily Equipment Templates:
- "Y" for "Yes" (Enable Equipment Templates)
- "N" for "No" (Disable Equipment Templates)
|
| SP_DailySum |
Daily: Use only Summary Logs |
"N" for "No (Use Logs)" |
Use Summary Officer Dailies (rather than Full Officer Dailies with Log Entries):
- "Y" for "Yes" (Use Summary Officer Dailies)
- "N" for "No" (Use Officer Daily Log Entries)
|
| External Document Management System |
| Name |
Title |
Default Value |
Description |
| SP_DMS_Active |
DMS: External DMS is Active |
"N" for "No (Disabled)" |
An External Document Management System (DMS) is Installed and Active:
- "Y" for "Yes" (External DMS is Enabled)
- "N" for "No" (External DMS is Disabled)
This parameter can be overridden by the corresponding Workstation/User Parameter (UP_DMS_Active).
Both must be set to "Yes" to enable access to the External DMS on any Workstation. |
| SP_DMS_EXE |
DMS: Program Name and Path |
"DMS.exe" |
The Program Name (including the full Path) to the external Document Management System (DMS).
This parameter can be overridden by the corresponding Workstation/User Parameter (UP_DMS_EXE). |
| SP_DMS_DSN |
DMS: Data Source Name (DSN) |
"DMS" |
The ODBC Data Source Name (DSN) used to connect to the DMS SQL Database Server.
This parameter can be overridden by the corresponding Workstation/User Parameter (UP_DMS_DSN). |
| SP_DMS_UID |
DMS: User ID (for DSN) |
"PDMS" |
User Name (ID) for accessing the installed DMS Database Server.
This parameter can be overridden by the corresponding Workstation/User Parameter (UP_DMS_UID). |
| SP_DMS_PWD |
DMS: Password (for DSN) |
"PDMS" |
Password for accessing the installed DMS Database Server.
This parameter can be overridden by the corresponding Workstation/User Parameter (UP_DMS_PWD). |
| SP_DMS_DocTbl |
DMS: Document Table Name |
"PDMS.Document" |
Fully qualified Table Name for the DMS "Documents" Table. |
| SP_DMS_FDPKey |
DMS: Document Primary Key Column |
"DOC_PK" |
Column Name of the Field containing the "Primary Key" for the DMS "Documents" Table. |
| SP_DMS_FDDate |
DMS: Document Creation Date Column |
"DOC_CREATE_DATE" |
Column Name of the Field containing the "Creation Date" of a Document in the DMS "Documents" Table. |
| SP_DMS_FDDesc |
DMS: Document Description Column |
"DOC_DESCRIPTION" |
Column Name of the Field containing the "Description" of a Document in the DMS "Documents" Table. |
| SP_DMS_FDPage |
DMS: Document Page Count Column |
"DOC_PAGE_COUNT" |
Column Name of the Field containing the "Page Count" of a Document in the DMS "Documents" Table. |
| SP_DMS_AtrTbl |
DMS: Document-Attributes Table Name |
"PDMS.Document_Attribute" |
Fully qualified Table Name for the DMS "Document Attributes" Table. |
| SP_DMS_FAPKey |
DMS: Document-Attributes Key Column |
"DOC_ATTR_DOC_PK" |
Column Name of the Field containing the "Primary Key" for the DMS "Document Attributes" Table. |
| SP_DMS_FARepN |
DMS: Document-Attributes Report Column |
"DOC_ATTR_SP_NO" |
Column Name of the Field containing the "Incident Report Number" of a Document in the DMS "Document Attributes" Table. |
| Personnel and Training |
| Name |
Title |
Default Value |
Description |
| SP_OTCompTime |
Personnel: Overtime to Comp Time Factor |
"100" for "100% (1:1)" |
Overtime to Comp Time Factor in percent. Values can be any number from "0" to "9999". Examples:
- "75" for "75% (1 Hour of Overtime becomes 45 Minutes of Comp Time)
- "100" for "100% (1 Hour of Overtime becomes 1 Hour of Comp Time)
- "150" for "150% (1 Hour of Overtime becomes 1 Hour and 30 Minutes of Comp Time)
|
| SP_DailySumOR |
Personnel: Include Daily Overtime Hours |
"N" for "No (Ignore Overtime)" |
Include Summary-Daily Overtime Hours in Personnel Overtime Reports:
- "Y" for "Yes" (Include Summary Daily Overtime Hours)
- "N" for "No" (Ignore Summary Daily Overtime Hours)
|
| File Classes |
| Name |
Title |
Default Value |
Description |
| SP_FCCaption |
File Class: Field Caption |
"File Class" |
Text used for File Class or Offense Code Captions. |
| SP_FCLength |
File Class: Field Length |
"5" for "MICR" |
Length of the File Class or Offense Code input value. For MICR, Offense Codes usually consist of 5 digits.
Maximum length is up to 8 characters, though. |
| SP_FCPicture |
File Class: Field Picture |
"@R 9999-9" |
Input Picture for File Classes or Offense Codes. The default value is designed for MICR File Class codes.
This should match the Offense Code Field Length.
Note: Please contact EJS OnSite Support for valid Syntax options! |
| SP_FCAllCaps |
File Class: All Upper Case Descriptions |
"N" for "No (Print as Entered)" |
Show and Print File Class Descriptions always in "ALL UPPER CASE" (rather than as they were entered):
- "Y" for "Yes" (ALL UPPER CASE DESCRIPTIONS)
- "N" for "No" (Mixed Case Descriptions)
|
| SP_HitRun |
File Class: Hit and Run Accident |
"54001" |
File Class or Offense Code (or Code Group) for Hit and Run Accidents. This can be a partial Code (or a Code Group),
like "5400" or a specific File Class code, like "54001". This value is used for various (System) Reports. |
| SP_TAReport |
File Class: Traffic Accident |
"93001" |
File Class or Offense Code for Traffic Accidents (usually not a MICR/NIBRS-reportable Code). This value is used for various (System) Reports. |
| Arrest Codes |
| Name |
Title |
Default Value |
Description |
| SP_ACCaption |
Arrest Code: Field Caption |
"Arrest Code" |
Text used for Arrest (Charge) Code Captions. |
| SP_ACLength |
Arrest Code: Field Length |
"4" for "MICR" |
Length of the Arrest (Charge) Code input value. For MICR, Arrest Codes usually consist of 4 digits.
Maximum length is up to 8 characters, though. |
| SP_ACPicture |
Arrest Code: Field Picture |
"@K 9999" |
Input Picture for Arrest (Charge) Code. The default value is designed for MICR Arrest Codes.
This should match the Arrest (Charge) Code Field Length.
Note: Please contact EJS OnSite Support for valid Syntax options! |
| SP_ACAllCaps |
Arrest Code: All Upper Case Descriptions |
"N" for "No (Print as Entered)" |
Show and Print Arrest Code Descriptions always in "ALL UPPER CASE" (rather than as they were entered):
- "Y" for "Yes" (ALL UPPER CASE DESCRIPTIONS)
- "N" for "No" (Mixed Case Descriptions)
|
| Zip Codes |
| Name |
Title |
Default Value |
Description |
| SP_UniqueZip |
Zip Codes: Enforce Unique Zip Codes |
"Y" for "Yes (Unique)" |
Enforce Unique Zip Codes with only a single City Name for every Zip Code:
- "Y" for "Yes" (Enforce Unique Zip Codes)
- "N" for "No" (Allow multiple City Names for each Zip Code)
|
| Security Access |
| Name |
Title |
Default Value |
Description |
| SP_EditClosed |
Security: Allow Edit of Closed Incidents |
"N" for "No (Only Supervisors)" |
Allow All Users or only Supervisors to Edit "Closed" Incidents, based on the Incident Status and Access Rights:
- "Y" for "Yes" (The Incident Status of "Closed" is ignored)
- "N" for "No" (Only Supervisors can Edit "Closed" Incidents)
If "No" is selected, access to "Closed" Incident Reports can be granted
to individual Users (that don't have Supervisor Status) through the User/Password maintenance. |
| SP_RenumIRep |
Security: Access Level to Renumber |
"4" for "Supervisor" |
Required Access Level to Renumber Incident Reports:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit the Incident Report)
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support" (Do Not Use!)
|
| SP_EditIRStat |
Security: Access Level to Edit Status |
"2" for "Clerk" |
Required Access Level to Edit the Incident Report Status:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit the Incident Report)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_EditSecure |
Security: Access Level to Edit Security |
"3" for "Super Clerk" |
Required Access Level to Edit the Security Status (of Incident Reports, Supplements, etc.):
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit the Incident Report)
- "3" for "Super Clerk" (Default Value)
- "4" for "Supervisor"
- "5" for "EJS Support" (Effectively Disables all Security Status Features!)
|
| SP_EditNIBRS |
Security: Access Level to Edit MICR |
"2" for "Clerk" |
Required Access Level to Enter and Correct MICR (or NIBRS) information of Incident Reports:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit the Incident Report)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_AddLoc |
Security: Access Level to Add Locations |
"2" for "Clerk" |
Required Access Level to Add new Locations. This can be used to enforce the use of a fixed set of Locations
(for example on a Campus) to keep Locations as accurate as possible:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_EditLoc |
Security: Access Level to Edit Locations |
"2" for "Clerk" |
Required Access Level to Edit (or Delete) existing Locations. This can be used to prevent unauthorized changes to existing
Locations, to keep Locations and their associations as accurate as possible:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_AddArrests |
Security: Access Level to Add Arrests |
"3" for "Super Clerk" |
Required Access Level to Add Arrests to other users' Incident Reports:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit)
- "3" for "Super Clerk" (Default Value)
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_AddPropSup |
Security: Access Level to Add Property |
"3" for "Super Clerk" |
Required Access Level to Add Property Items to other users' Incident Reports:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Everyone who can Edit)
- "3" for "Super Clerk" (Default Value)
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_IRepEditR |
Security: Access Level to Edit Restrict. |
"4" for "Supervisor" |
Required Access Level to Edit "Restricted" Incident Reports, Supplements, etc.
This is (usually) the lowest security setting besides "Unrestricted/Public":
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Effectively Disables "Restricted" Edit Limitations!)
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support" (Do Not Use!)
|
| SP_IRepViewR |
Security: Access Level to View Restrict. |
"2" for "Clerk" |
Required Access Level to View (details of) "Restricted" Incident Reports, Supplements, etc.
This is (usually) the lowest security setting besides "Unrestricted/Public":
- "1" for "Lookup Only" (Effectively Disables "Restricted" Viewing Limitations!)
- "2" for "Clerk" (Default Value)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support"
|
| SP_IRepPrintR |
Security: Access Level to Print Restrict |
"3" for "Super Clerk" |
Required Access Level to Print, Preview, or EMail "Restricted" Incident Reports, Supplements, etc.
This is (usually) the lowest security setting besides "Unrestricted/Public":
- "1" for "Lookup Only" (Effectively Disables "Restricted" Printing Limitations!)
- "2" for "Clerk"
- "3" for "Super Clerk" (Default Value)
- "4" for "Supervisor"
- "5" for "EJS Support"
|
| SP_IRepEditE |
Security: Access Level to Edit Expunged |
"4" for "Supervisor" |
Required Access Level to Edit "Expunged" Incident Reports, Supplements, etc.
This is (usually) a slightly higher security setting than "Restricted":
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Effectively Disables "Expunged" Edit Limitations!)
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support" (Do Not Use!)
|
| SP_IRepViewE |
Security: Access Level to View Expunged |
"2" for "Clerk" |
Required Access Level to View (details of) "Expunged" Incident Reports, Supplements, etc.
This is (usually) a slightly higher security setting than "Restricted":
- "1" for "Lookup Only" (Effectively Disables "Expunged" Viewing Limitations!)
- "2" for "Clerk" (Default Value)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support"
|
| SP_IRepPrintE |
Security: Access Level to Print Expunged |
"3" for "Super Clerk" |
Required Access Level to Print, Preview, or EMail "Expunged" Incident Reports, Supplements, etc.
This is (usually) a slightly higher security setting than "Restricted":
- "1" for "Lookup Only" (Effectively Disables "Expunged" Printing Limitations!)
- "2" for "Clerk"
- "3" for "Super Clerk" (Default Value)
- "4" for "Supervisor"
- "5" for "EJS Support"
|
| SP_IRepEditS |
Security: Access Level to Edit Sealed |
"4" for "Supervisor" |
Required Access Level to Edit "Sealed (by Court)" Incident Reports, Supplements, etc.
This is (usually) a slightly higher security setting than "Expunged":
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Effectively Disables "Sealed (by Court)" Edit Limitations!)
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support" (Do Not Use!)
|
| SP_IRepViewS |
Security: Access Level to View Sealed |
"3" for "Super Clerk" |
Required Access Level to View (details of) "Sealed (by Court)" Incident Reports, Supplements, etc.
This is (usually) a slightly higher security setting than "Expunged":
- "1" for "Lookup Only" (Effectively Disables "Sealed (by Court)" Viewing Limitations!)
- "2" for "Clerk"
- "3" for "Super Clerk" (Default Value)
- "4" for "Supervisor"
- "5" for "EJS Support"
|
| SP_IRepPrintS |
Security: Access Level to Print Sealed |
"4" for "Supervisor" |
Required Access Level to Print, Preview, or EMail "Sealed (by Court)" Incident Reports, Supplements, etc.
This is (usually) a slightly higher security setting than "Expunged":
- "1" for "Lookup Only" (Effectively Disables "Sealed (by Court)" Printing Limitations!)
- "2" for "Clerk"
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support"
|
| SP_IRepEditC |
Security: Access Level to Edit Confiden. |
"4" for "Supervisor" |
Required Access Level to Edit "Confidential" Incident Reports, Supplements, etc.
This is (usually) the highest security setting available:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk" (Effectively Disables "Confidential" Edit Limitations!)
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support" (Do Not Use!)
|
| SP_IRepViewC |
Security: Access Level to View Confiden. |
"4" for "Supervisor" |
Required Access Level to View (details of) "Confidential" Incident Reports, Supplements, etc.
This is (usually) the highest security setting available:
- "1" for "Lookup Only" (Effectively Disables "Confidential" Viewing Limitations!)
- "2" for "Clerk"
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support"
|
| SP_IRepPrintC |
Security: Access Level to Print Confid. |
"4" for "Supervisor" |
Required Access Level to Print, Preview, or EMail "Confidential" Incident Reports, Supplements, etc.
This is (usually) the highest security setting available:
- "1" for "Lookup Only" (Effectively Disables "Confidential" Printing Limitations!)
- "2" for "Clerk"
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support"
|
| SP_DelMessage |
Security: Access Level to Delete Message |
"4" for "Supervisor" |
Required Access Level to Delete any Sent and Received Messages (and Responses):
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk"
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support" (Do Not Use!)
|
| SP_UseEMail |
Security: Access Level to EMail Address |
"2" for "Clerk" |
Required Access Level to Send EMails to a different EMail Address than EJS OnSite Support:
- "1" for "Lookup Only" (Even Lookup Only Users can send EMails!)
- "2" for "Clerk" (Default Value)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support" (Limits all EMails to Support!)
|
| SP_EditDispLD |
Security: Access Level to Edit Call Time |
"4" for "Supervisor" |
Required Access Level to Edit the Call Date/Time in Dispatch Log Entries:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk"
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support"
|
| SP_EditDispCT |
Security: Access Level to Edit CallTaker |
"4" for "Supervisor" |
Required Access Level to Edit the Call Taker (or Dispatcher/User ID) in Dispatch Log Entries:
- "1" for "Lookup Only" (Not Applicable)
- "2" for "Clerk"
- "3" for "Super Clerk"
- "4" for "Supervisor" (Default Value)
- "5" for "EJS Support"
|
| SP_EditDaily |
Security: Access Level to Add/Edit Daily |
"2" for "Clerk" |
Required Access Level to Add or Edit Officer Daily Logs. Even users with Access Level "1" for "Lookup Only"
could be allowed to Add and Edit Officer Dailies without being able to edit anything else in the application, if that is desired:
- "1" for "Lookup Only" (Even Lookup Only Users might Add/Edit Officer Dailies!)
- "2" for "Clerk" (Default Value)
- "3" for "Super Clerk"
- "4" for "Supervisor"
- "5" for "EJS Support" (Do Not Use!)
|
| SP_DailyRestr |
Security: Restrict Access to Daily Logs |
"Y" for "Yes (Restrict Access)" |
Restrict Access to Daily Logs based on User Access Rights. This is used to prevent Users with a lower Access Level
than the original Author, from Viewing or Printing any of the detail Log Entries:
- "Y" for "Yes" (Hide Log Entries from Users with lower Access Rights)
- "N" for "No" (Show all Log Entries to all Users)
|
| Interfaces (Data Import / Export) |
| Name |
Title |
Default Value |
Description |
| SP_DRI_Active |
Import: (Dispatch) Incidents Active |
"N" for "No (Disabled)" |
The automatic (CAD/Dispatch) Incident Report Data Import process is Active.
This is usually used as an Interface between an external CAD/Dispatch application and the EJS OnSite RMS:
- "Y" for "Yes" (Enable Incident Report Imports)
- "N" for "No" (Disable Incident Report Imports)
|
| SP_IMP_Sleep |
Import: Time Interval between Checks |
"10" for "10 Seconds" |
Time Interval in Seconds between checks for new Import Data Files in the "Import" directory. |
| SP_DRI_Module |
Import: Incident Processing Module |
(No Default Value) |
Program Module for processing the Incident Report Data Imports from an external (CAD/Dispatch) application.
Note: Please contact EJS OnSite Support for valid options! |
| SP_DRI_FileEx |
Import: File Extension for Incident Data |
"TXT" for "Text Files" |
File Extension for the Incident Report Data Import Files, located in the "Import" directory. |
| SP_DRI_AddDoc |
Import: Add Import File to Documents |
"N" for "No (Don't Copy)" |
Copy all Import Data Files to the "Documents" directory after processing:
- "Y" for "Yes" (Copy Imported Files)
- "N" for "No" (Don't Copy any Files)
|
| SP_DRI_AddNar |
Import: Add Descriptions as Narratives |
"N" for "No (Skip It)" |
Add (long) Incident Descriptions as Narratives during Data Imports:
- "Y" for "Yes" (Add Narratives)
- "N" for "No" (Skip Narratives)
|
| SP_DRI_AddLoc |
Import: Add Locations |
"N" for "No (Skip It)" |
Add Locations of Incidents during Data Imports:
- "Y" for "Yes" (Add Locations)
- "N" for "No" (Skip Locations)
|
| SP_DRI_AddPer |
Import: Add Persons/Callers |
"N" for "No (Skip It)" |
Add Names / Persons (Callers) during Data Imports:
- "Y" for "Yes" (Add Persons/Callers)
- "N" for "No" (Skip Persons/Callers)
|
| SP_DRI_AddPhn |
Import: Add Phone Numbers |
"N" for "No (Skip It)" |
Add Phone Numbers to Persons (Callers) during Data Imports. This is only possible if Persons/Callers are also Added (see above):
- "Y" for "Yes" (Add Phone Numbers)
- "N" for "No" (Skip Phone Numbers)
|
| SP_DRI_DelCan |
Import: Delete Canceled Incidents |
"N" for "No (Update Status)" |
Delete Canceled Incident Reports during Data Imports. The preferred (and more secure) option is to only
update the Incident Report Status to a "Canceled Status" (usually "Unfounded", see above),
rather than allowing the automatic deletion of Incident Reports:
- "Y" for "Yes" (Delete Incident Reports)
- "N" for "No" (Only Update Incident Status)
|
Note:
For other Interface (Data Import / Export) Parameters, use the dedicated
Automatic Process Parameter Maintenance and FTP/Internet Parameter Maintenance
options!
|
| LEADS (Data Sharing) |
| Name |
Title |
Default Value |
Description |
| SP_UseLDSLook |
LEADS: Restore Last-Used Lookup Mode |
"N" for "No (Don't Restore)" |
Restore Last-Used LEADS Lookup Mode for Searching by Names, DLNo, or Address:
- "Y" for "Yes" (Restore Last Lookup Mode)
- "N" for "No" (Default to Name Search)
|
| SP_LEADSLook |
LEADS: Last-Used Lookup Mode |
"N" for "Names / DoB" |
Last-Used LEADS Lookup Mode Code. This is automatically updated by the LEADS module:
- "N" for "Names" (with or without DoB)
- "D" for "Driver's License or ID" (can be scanned/swiped)
- "A" for "Address" (Incident Location)
|
| SP_LEADSLogBp |
LEADS: Backup LEADS Logs |
"Y" for "Yes (Backup Logs)" |
Create (up to 999) Backup Log Files, by copying any existing LEADS Log file to a Backup file,
before creating a new LEADS Log file:
- "Y" for "Yes" (Backup LEADS Logs)
- "N" for "No" (Overwrite LEADS Log)
|
Note:
For all other LEADS (Data Sharing) Parameters, use the dedicated
Automatic Process Parameter Maintenance and FTP/Internet Parameter Maintenance
options!
|
| Automatic Processes |
| Name |
Title |
Default Value |
Description |
| SP_EMN_Sleep |
EMail Notifications: Time Interval |
"6" for "6 Minutes" |
Time Interval in Minutes between Checks for new EMails. |
Note:
For all other Automatic Process Parameters, use the dedicated
Automatic Process Parameter Maintenance option!
|
| EMails |
| Name |
Title |
Default Value |
Description |
| SP_SaveEMails |
EMail: Save Copy of Sent EMails |
"N" for "No (Don't Save)" |
Save a copy of all EMails that are Sent by the EJS OnSite application in the EMail databases:
- "Y" for "Yes" (Save all Sent EMails)
- "N" for "No" (Don't Save any EMails)
|
Note:
For all other EMail Parameters, use the dedicated EMail Parameter Maintenance and
EMail Address Maintenance options!
|
| Setup (Other) |
| Name |
Title |
Default Value |
Description |
| SP_Background |
Setup: Background Graphic to Display |
"EJS_LOGO.JPG" |
Name of the Picture File that is used as the EJS OnSite Main Dialog Background Graphic. This file MUST be located in the application's "Programs" directory and must be in a valid graphics format (JPG/PNG/GIF/BMP). |
| SP_Juvenile |
Setup: (Maximum) Juvenile Age |
"16" for "16 Years Old" |
Maximum Age for Juveniles in Years. The Default for Michigan is 16 Years, and the Juvenile status changes to Adult on the date of the 17th Birthday. |
| SP_Military |
Setup: Military (or AM/PM) Time Format |
"Y" for "Yes (Military Time)" |
Use the (24 Hour) Military Time Format or the (12 Hour) AM/PM Time Format:
- "Y" for "Yes (Military Time)" ("00:00" to "23:59")
- "N" for "No (AM/PM Time)" ("12:00 AM" to "11:59 PM")
Some Times are always displayed in Military Format, though, and all Times are internally stored in Military Format,
so switching back and forth between the two options can be done at any time. |
| SP_Epoch |
Setup: Year (Epoch) |
"1914" for "1914 - 2013" |
The Epoch Year is used to calculate the default Century for Dates entered with a one- or two-digit Year. With an Epoch of "1914",
Years entered as "0" through "13" are converted by adding "2000", while
Years entered as "14" through "99" are converted by adding "1900". |
| SP_AllMsgDays |
Setup: Lifetime of Messages to All User |
"7" for "7 Days" |
Notification Lifetime (in Days) for Messages that were sent to "All Users". After the indicated number of days has passed,
such Messages will no longer be presented to new Users, even if they haven't seen them yet. |
| SP_BackupLog |
Setup: Create/Update Backup Log |
"N" for "No (Skip Log)" |
Log any Backup-related operations in the "Backup.log" file in the "Logs" directory:
- "Y" for "Yes" (Update Backup Log)
- "N" for "No" (Don't use Backup Log)
|
| SP_InstallLog |
Setup: Create/Update Install Log |
"Y" for "Yes (Update Log)" |
Log any Install-related operations in the "Install.log" file in the "Logs" directory:
- "Y" for "Yes" (Update Install Log)
- "N" for "No" (Don't use Install Log)
|
| SP_IgnoreFDTS |
Setup: Ignore File Date/Time-Stamp |
"N" for "No (Do Compare)" |
Ignore the Date/Time-Stamps of Copied Files rather than comparing them to the Original File:
- "Y" for "Yes" (Ignore Date/Time-Stamps)
- "N" for "No" (Compare Date/Time-Stamps)
It might be necessary to ignore the File Date/Time-Stamps when copying between diverse Operating Systems,
which might have different Date/Time resolutions, which will result in inconsistent Date/Time-Stamps.
This is used for Notebook synchronizations as well as Version Updates. |