RULES
Person
Change Person Status | Changes a person’s status when a ‘Date Of Death’ is entered. | |
Tennessee Secure Person | Provides specialized security about who can see specific people in Quest based upon hard coded rules. | |
Indiana Secure Person | Provides specialized security about who can see specific people in Quest based upon hard coded rules. | |
Secure Person Attribute | This rule is designed to limit access to regular, special, and/or at risk person attributes. By default, everyone authorized to view person attributes can view these. With this rule, you can define which group(s) should NOT be authorized. | |
Change School Status | Changes the person’s current school status when all cases for the person have been closed. | |
Copy Agency Contact Information | Copies the employer agency address/contact numbers to a person. WHY WOULD I USE THIS? If you routinely add agency employees, for example DCS caseworkers, this rule would automatically add their work address and work phone number. | |
Send Message for Address | Sends a message to specific case assignments if an address is changed for a person. | |
Protect Address | This is meant to protect specific address type from people who would otherwise be authorized to it. WHY WOULD I USE THIS? This is a great way to keep groups of people from changing specific addresses. If you have a Notice Address for example, this is the address provided by the parties as to where they can be served. Then DCS or IV-D can change the home address to a new address for serving summons, but the Clerk will continue to send notice of court orders to the Notice Address until provided a new address by the parties. You can protect the Notice Address address type so DCS and IV-D can’t change it. | |
Protect Phone | This is meant to protect specific phone number type from people who would otherwise be authorized to it. WHY WOULD I USE THIS? This is a great way to limit the number of people who can add or change a specific contact number. For example, a Notice Email |
that is provided by attorneys and pro se litigants who have agreed to receive copies of court orders by email. | ||
Secure Medical Treatment | This is meant to protect medical treatments from being seen by people who would otherwise be authorized to them. | |
Allen End Home Address | This rule is designed for Allen County to automatically end all open home addresses when a protected address is added. |
Cases
Update State Decision | This is meant to act as a trigger to update the state’s decision and decision date when a document is file stamped. | |
Default Home Court | Defaults the home court when a case is added. It will check to see if the casename has previously been assigned to a single court. If so, it will assign the case to that court, regardless of what the user may have entered. |
Secure Case | Secures specific cases. 1) Person must be directly assigned to the case or the supervisor of a person directly assigned. | |
Secure Case | Nobody from a specified agency can see a case from another user from that agency. WHY WOULD I USE THIS? If you have a probation officer with a case in the system, this would stop everyone from that same agency from seeing that probation officer’s case. | |
Secure by Open Case | Secures a record by checking for open case. Most groups only have access to the record if the person has an OPEN case of a type the user is authorized to. If a person does not have an open case, certain areas of their record can be hidden, such as substance reports, contact notes, etc. | |
Tennessee Secure Case | Provides specialized security based upon hard coded rules. In summary, the rules are: 1) A person can only see a case if the home court matches the person’s employer agency. WHY WOULD I USE THIS? If you have multiple agencies using the same Quest jurisdiction. | |
Validate Case | Performs logical validations on a case. WHY WOULD I USE THIS? Right now, this allows you to say in which case types Filed Statutes Must Exist. I can see opportunities for future use. |
Indiana Update Cover Sheet | Automatically formats and updates the oldest cover sheet entry for a case. The entry is added if it doesn’t already exist. WHY WOULD I USE THIS? The cover sheet is a great way to see specific information on companion cases. |
Case Assignments
Add User to case on requirement | Assigns users to a case whenever a requirement of a specified type or type/code are added. WHY WOULD I USE THIS? This is a great way to add a user to the case when a specific requirement, such as community service is added, if you have a specific person who monitors the community service activity. | |
Add user to case on status | Assigns users to a case whenever a case status of a specified type is added. WHY WOULD I USE THIS? If you want to add a specific person to a case assignment every time a new case is open, this allows you to do that, or if a case status of “collections” is added, you could add your collections person to the names assigned to the case for example. | |
End Case Assignments | Ends all open case assignments of the specified type when a new assignment of the same role is added. WHY WOULD I USE THIS? If you want to prevent duplicate roles. | |
No Duplicate Roles | Prevents 2 or more people from being assigned to the same case at the same time with a specified role. WHY WOULD I USE THIS? If you want to prevent duplicate roles. | |
Add User to case on incident | Adds the current Incident Officer as a case assignment. WHY WOULD I USE THIS? When adding the officer to the incident detail screen, that person can also be automatically assigned to the case in whatever role you wish, petitioner, witness, arresting officer, etc. | |
Stay to Case Assign | This is meant to act as a trigger to automatically add/update the corresponding case assignment to the database whenever a stay reason starts and/or ends. | |
Send Message | Sends a Quest message to all active case assignments (who are Quest users) tied to the record in question letting them know about the action. |
WHY WOULD I USE THIS? It is a way to ensure all Quest users who are assigned to the case are aware of different things being added in the case, such as case assignments, case names, deadlines, facility stays, and incidents. | ||
Send Message 2 | Sends a Quest message to the desired parties about the passed object, such as a new case assignments, facility stay or stay locations, filed statutes or cause numbers, incident statutes, event types, or event attributes. |
Case Status
Update Case Status | This is meant to act as a trigger to update the case status when a document is file stamped (by default) or other time, if specified. WHY WOULD I USE THIS? Sometimes we use an FF Update to add a case status, such as a DCS Petition Alleging Child in Need of Services, we want it to add a case status of “Petition Filed.” However, this adds the case status when the document is FINISHED. If a petition is finished at 5:00 on a Friday night, it may not be file stamped until Monday morning, so a case status of Petition Filed on Friday would not be as correct as a case status of Petition Filed on Monday morning. This rule will allow you to specify which templates should add a case status upon File Stamp, completion, or approval. |
Deadlines
Send Email for Deadlines | Sends a message to all active case assignments from the same agency as the agency assigned to the deadline letting them know about the deadline. WHY WOULD I USE THIS? It is a way to notify the agency responsible for the deadline that a deadline has been added, updated, or deleted on their case. | |
GAW047 | Indiana PD Visit Deadline | For Marion County Indiana, this rule creates a deadline for the PD to visit someone in secure detention when the PD is appointed to a case. |
Indiana Transport Deadline | For Marion County Indiana, creates a deadline for the Court to issue a return order whenever a transportation order is generated. |
Warrants
Warrant Notify | This rule is will send eQuest messages to specified Identities when a Warrant is added/updated. The purpose is to notify certain parties like the Sheriff who must know when Warrants are issue, served, recalled, etc. Messages are intended to be sent when a new Warrant record is added or when the warrant status is changed. WHY WOULD I USE THIS? This is a great way to keep people informed of warrant changes. |
Incidents
GAW023 | Allen Incident Docket Entry | This rule ensures there is always a ‘WIR’ manual docket entry written for any incident which is added or updated that is tied to a Case. |
GAW029 | Howard Requirement to Incident | This is meant to act as a trigger to automatically add the corresponding incident to the database whenever a probation requirement starts and ends. |
GAW030 | Howard Stay To Incident | This is meant to act as a trigger to automatically add the corresponding incident to the database whenever a stay starts and ends. |
GAW038 | Tippecanoe Requirement to Incident | This is meant to act as a trigger to automatically add the corresponding incident to the database whenever a requirement starts and ends. |
GAW039 | Tippecanoe Stay To Incident | This is meant to act as a trigger to automatically add the corresponding incident to the database whenever a stay starts and ends. |
Filed Statutes
GAW026 | Allen Update Filed Date | This is meant to act as a trigger to update the filed date of the latest filed statutes with the date of the current case status record. It will only do it when case status is changed to petition filed or modification filed. |
Events
Secure User Event | This is meant to limit access to changing/deleting a non-court event to the person who created it. | |
Send Email for Events | This will send an email notifying all case assignments tied to the event of the event, along with a calendar invite attachment. For somebody to receive an email, we must have their email address within Quest. It is also possible to specify email addresses that should get notice for specific event types or events from a specific court. | |
Send Message for Events | This will send a Quest message notifying all case assignments tied to the event of the event. WHY WOULD I USE THIS? This is a great way to notify probation officers if someone is scheduled to appear for a drug test for example, and an event disposition is added as “failed to appear.” A quest message will be sent to all names assigned to the case. | |
Event to Contact | Creates a contact when an event is completed. Copies the event note to the contact note. WHY WOULD I USE THIS? Probation appointments for example, if you pull up your calendar and make notes on each event as they happen it is an easy way to quickly add a contact note. | |
Event Appearance Set Document | Overrides the document to create for the event appearance based on the configuration settings for this rule. | |
Event to Substance Report | Creates a substance report when an event is completed ‘successfully’. You also have the option as to whether you want to do this for court events. WHY WOULD I USE THIS? This is useful in drug courts when you’ve scheduled the person to come in for testing. You can automatically add a substance report just be disposing of the event. | |
Validate First Case Attribute | Validates that, if an event is flagged with a ‘first case of the day’ attribute, it is the only event for that court with the attribute and, none of the case assignments are already associated with another ‘first case’ in another court that day. | |
Copy Case Notes | This is meant to automatically copy notes from one case to another. It will only do it for notes added/updated within an event. |
Secure Event Overload | This is a security rule designed to limit a user or group to specific court(s) if they are authorized to overload hearings. WHY WOULD I USE THIS? This is a great way to limit departments, such as IV-D or DCS from scheduling more than a specific number of cases for a court. When they have reached the specific number, they can’t add any more hearings. | |
Update Event for Requirements | Updates an existing event on the same day with a completion code and note of why completed for all people tied to a requirement related object. |
Requirements
Send Email on Requirement | Sends an email to the desired parties about the passed Requirements / RequirementCases objects. WHY WOULD I USE THIS? Allows you to notify someone by email when a requirement is added, such as a referral to a treatment facility or a commitment to DOC or DCS. | |
Send Message for Requirements | Sends a Quest message to all active case assignments (who are Quest users) for the names tied to the underlying requirement letting them know about this particular item. It also allows you to specify additional people to receive notification. WHY WOULD I USE THIS? This is very useful in notifying someone of a payment on a requirement, such as a bond payment where the clerk needs to process it. | |
Add Attribute on Requirement | Assigns a person attribute and/or requirement attribute whenever a requirement of a specified type or type/code is added. WHY WOULD I USE THIS? For statistical purposes every time you add a specific requirement you could also automatically add a requirement attribute. Such as when you add community corrections/drug court, a requirement attribute of problem solving court could be added. So you could pull statistics how many people were involved in problem solving court, if you had several requirements of this type or you could add a person attribute of drug court participant or something. | |
Ensure Requirement Exists | This is meant to limit insertion of data into a case until a specific requirement type/code has been added for that case. WHY WOULD I USE THIS? |
This is helpful if you have a specific requirement that must be added, such as a specific program you are running and you want to make sure the requirement has been added. | ||
Stop Requirement Overlap | Prevents 2 requirements from overlapping each other (except on start/end date). WHY WOULD I USE THIS? Maybe you want to prevent two home detention fees from running at the same time. | |
Add Scheduled End to Requirement | This is meant to automatically place a scheduled end date on all defined ‘auto’ add requirements that are still open when the primary requirement is ended. The scheduled end date will match the status date of the primary requirement. The ‘auto’ add requirements are defined in the settings for the primary requirement. WHY WOULD I USE THIS? If on your home detention for example, you have it configured to add a fee requirement when the home detention requirement is added, then when the home detention requirement ends, this rule will cause a scheduled end date to be added to the fee requirement, thereby stopping the assessing of more fees. | |
Track SI Inventory | This rule keeps the sanctions/incentives inventory field up to date (in the sanctions/incentives generic validation table). WHY WOULD I USE THIS? If you have a requirement where you are using sanctions and incentives, such as drug court, and you have 10 movie cards to give out as incentives, when you give 1 away, this will keep track of the fact that you only have 9 movie cards left. | |
Add Req Attribute By User | Adds a requirement attribute whenever one of the following conditions is met:
|
Financials
Generate Transaction Nbr | This is the default generator for financial transaction numbers. WHY WOULD I USE THIS? If there are multiple departments taking payments and you want the transaction numbers on receipts to be different. For |
example: Clerk’s numbers start with a C and Probation starts with a P. | ||
Update Requirement on Paid | Updates the associated Requirement when a transaction results in the requirement being fully paid or waived. WHY WOULD I USE THIS? This is a wonderful way to ensure the requirement status gets updated when a fee is paid or waived without the user having to remember to do it. | |
Transaction Edits | This allows the user to configure rules for the financial transactions, such as allow future dates, allow back dates, allow negative amounts , payment method required, payor required, etc. WHY WOULD I USE THIS? It makes certain fields on the take a payment window mandatory. Such as you must have a payment method and a payee selected or you will get an error message. If you don’t allow back dates the user can’t accidently date the payment 1/1/18 instead of today. | |
GAW106 | Credit Card Fee | This rule is designed to recalculate the transaction fees specifically for credit card transactions. |
Notify Collection on Payment | This rule will send an email to a collections agency when payment transactions are entered, notifying them of payments received. | |
Indiana Assess 25 of Open | Automatically assesses a given percentage (defaults to 25%) of all outstanding balances for a person when the specified requirement type/code is added. | |
Substance Report to Transaction | Creates a transaction to an existing open requirement every time a substance report is added. WHY WOULD I USE THIS? When a specific type of substance report is added, it will automatically add the drug test fee. | |
Update Payment Plan | This rule keeps the payment plan requirement in sync with payments made. It matches on the person making the payment matching the default payee of the payment plan requirement on a case being paid. | |
GAW040 | Indiana Add Estate Court Costs | This is meant to act as a trigger to automatically add court costs to ESTATE cases. |
GAW022 | Allen Credit Card Fee | This rule is designed to recalculate the transaction fees specifically for credit card transactions. It is very hard coded and will only work for specific requirement transaction types that already include certain accounts. |
Documents
Protect Document | This is meant to protect documents from being updated or deleted once notice has been sent (printed). WHY WOULD I USE THIS? Once notice has been sent to the parties, you wouldn’t want a Reporter to be able to hit Edit Text and change a document. | |
Protect Document2 | This is meant to protect a document from being updated once it has been completed. WHY WOULD I USE THIS? Certain documents will send information to someone upon completion or may update certain areas in Quest. You may want to block these types of documents from being changed after finished. | |
Secure Document | This is meant to limit access to a document to either the person who created it or the person assigned to it. | |
Secure Document 2 | This rule is designed to limit access to docket codes that a user may otherwise be authorized to view. With this rule, you can define which group(s) should NOT be authorized. WHY WOULD I USE THIS? You may have invoices submitted by appointed attorneys or GALs that you don’t want the other names assigned to the case to see, so if you scan the invoice as a docket entry, then add that docket code to this rule, certain security groups can’t see it. | |
Send Email for Documents | Sends an email or fax if possible to all active case assignments for the names tied to a document letting them know about the document. It also updates the fact that notice was sent to these people. It is possible to skip sending emails for documents that need approval or need file stamp until that event happens. If you do this, make sure to add the rule to those events on the document so people get notice when that happens. WHY WOULD I USE THIS? It is a way to ensure everyone who is assigned to the case but is not a Quest user is aware of the documents being entered in the case. If you are using the certificate of service and print pending notices I would not turn this rule on. | |
Send Email for Documents 2 | Sends an email to the desired parties letting them know about the document. It also updates the fact that notice was sent to these people. |
WHY WOULD I USE THIS? This is a great way to notify people who are not assigned to the case of a document, such as the sheriff if the document is a warrant. | ||
Send Message for Documents | Sends a Quest message to all active case assignments (who are Quest users) for the names tied to a document letting them know about the document. It also updates the fact that notice was sent to these people. While it could be called for any request, it makes the most sense to call it with either ‘a’ (upon completion) and/or ‘A’ (when the document is approved/rejected). It is possible to skip sending messages for documents that need approval or need file stamp until that event happens. WHY WOULD I USE THIS? It is a wonderful way to ensure all Quest users who are assigned to the case are aware of the document being entered in the case but that they don’t get the documents until they are approved, or file stamped. I would recommend using the “skip until approval=y” and “skip until file stamp=y” option so that notice is not sent to anyone until that happens. | |
Send Message for Documents 2 | Sends a Quest message to the desired parties about the passed Documents object. If a DocumentNames object is passed, the message refers to the underlying Documents object which must be a manual docket entry. It also updates the fact that notice was sent to these people. WHY WOULD I USE THIS? If you wanted to send a copy of a file stamped document or an approved order to a Quest user who is not assigned to the case, such as the Prosecutor or the Clerk. | |
Send Message On File Stamp | Sends a Quest message to the desired parties indicating a document has been file stamped. Can be sent to all case assignments or to a specific quest user. WHY WOULD I USE THIS? You could potentially use this to notify the Clerk of all the documents that have been file stamped that day. Once documents are file stamped they are removed from the list to be file stamped. If you used this rule to send all file stamped documents to a generic clerk user, they would quickly print all the documents that were file stamped that day. But other than that, I would use GAW016. |
Indiana Send School Notice | It sends a generic email to the current school for each person with an open case attached to the document that has a guilty felony charge. It also sends a regular Quest message to every user directly authorized to the person’s current school assignment. WHY WOULD I USE THIS? Because in Indiana you are required to notify the schools of adjudications. IC 35-50-8 & IC 35-50-8-1 | |
Auto Approve Document | It will automatically approve the document. | |
Add Contact for Documents | This will add a contact note for a document. WHY WOULD I USE THIS? If you created a Violation Petition for example, you may want to add a contact note that says “Violation Petition Filed.” | |
Auto Assign Document | Automatically assign a document to the last user of the specified role attached to a case associated with the document. |
Supervision
Assessments
Protect Assessment | This is meant to protect an assessment or assessment detail from being viewed by a group otherwise authorized. |
Contacts
Secure Contact | This rule is designed to limit access to contacts of specified types. If a contact is being secured, in addition to the regular authority to access it, the user must be in the same agency as the person who created the contact. | |
Add Contact for Requirements | This will add a contact note for a requirement related object. | |
Document Note to Contact | Creates a contact when a document note is completed by a particular person. Copies the document note to the contact note. | |
Contact to Substance Report | Creates a substance report when a contact is added. WHY WOULD I USE THIS? If you add a contact that you gave a field alcohol test for example, when that contact type is added, it will automatically add a substance report for that date and time. | |
Case Plan to Contact | This is meant to create (or update) a contact note when a case plan item changes. | |
Protect Contact | This is meant to protect specific contact notes from being seen by people who would otherwise be authorized to it. |
Detention
Require Case on Stay Reason | Validates that a case is tied to the Stay Reason record. | |
Stay to Require | This is meant to act as a trigger to automatically add/update the corresponding requirement to the database whenever a stay reason starts and/or ends. WHY WOULD I USE THIS? If you are tracking your facility stays also as requirements this is a great way to automate it. | |
Send Email for Detention | Sends an email to the desired parties about detention counts exceeding a desired threshold. | |
Send Email for New Detention | Sends an email to the desired parties about a new person being brought into detention. |
Add Assignment as Visitor | Adds an assigned person as an approved visitor whenever a case assignment is added and there’s an open stay or whenever a stay is added and there’s an open assignment. Whenever either the stay or assignment ends, the person is removed from the visitor list (unless the stay is still open and the person is assigned to another case). | |
Allen Protect Log Book | This is meant to protect the shift leaders log book from being seen by people who would otherwise be authorized to it. WHY WOULD I USE THIS? This is helpful if someone needs a log book that they don’t want others who have security to view log books to see. Such as if shift leaders need to log information about staff, but don’t want staff to be able to see it. | |
GAW025 | Allen Stay To Incident | This is meant to act as a trigger to automatically add the corresponding incident to the database whenever a stay starts and ends. |
Time Keeping
GAW019 | Time Keeping | Access the old G&W time keeping system to update the in/out information for a person. This only works for Lake County when the locator screen (IdentityMisc) is added/updated. |
GAW051 | Indiana Send Locator Message SJ | Sends a message to a user when a person changes a locator screen (IdentityMisc) to Sick/Vacation/Other. |
GAW130 | Add to Overtime | Automatically adds an additional overtime amount to whatever the user had entered. |
GAW134 | Send Message for Usage | Sends a message to all parties requested when a particular time code is used. |
G&W Programming Rules – FOR INFORMATION ONLY
GAW001 | Cancel Events | Cancels future events if the current status of the case is now closed. Events are only cancelled if this is the only case tied to the event. Otherwise, references to this case are simply removed from the event. Of course, the user must be authorized to perform those tasks or the rule won’t work. |
GAW002 | Close Case | Performs close case processing if the current status of the case is now closed. This entails putting end dates on case names, case assignments and deadlines. Of course, the user must be authorized to perform those tasks or the rule won’t work. If the status is inactive instead of closed, only case names and assignments will receive end dates. |
GAW003 | Format Cause | Determines whether or not to use cause number or petition numbers. |
GAW006 | Get Latitude Longitude | Performs the logic necessary to access some mapping interface to get the latitude/longitude for an address. |
GAW007 | Log Event | Logs the current event to the EventLog database table. This rule was written with the intent of providing a method to log who adds, updates or deletes database records. It is not meant to provide any kind of rollback database capabilities, but simply to log who has done what. Primarily, it’s purpose is to |
log who deletes Identities and Cases; however, it is written generically enough to work for any object. | ||
GAW008 | Log Signons | Logs sign on/sign off requests and performs special processing associated with logging on/off. |
GAW009 | Notify GAW | Used to send emails to G&W when various events happen. |
GAW010 | Notify Quest Administrator | Used to send emails to the Quest Administrator identified in the quest properties file when various events happen. |
GAW067 | Log View of Documents | Adds a DocumentNotes entry whenever the person who is assigned to a document views it. |
GAW068 | Track Document Assignments | Adds a DocumentNotes entry whenever a document assignment changes. |
GAW073 | Log Changes | This rule adds a GAWLog entry tracking when and where it is used. It reports the user and IP address involved as well the usage, key, and to string of the object. |
GAW077 | Validate Address | Validates an address against the United States Postal Service database. |
GAW091 | Indiana Secure Photos | Secures a person’s photo by ensuring the rules as follows:
|
GAW096 | Tennessee Generate Petition Number | Generates the petition number for a filed statute if a number was not provided. |
GAW097 | Add Filed Statute | Automatically adds a filed statute when an incident statute is added. |
GAW104 | Incident to Dispo Date | This rule forces disposition date on a filed charge to be greater than or equal to the earliest incident date on the case. |
GAW105 | Tennessee Generate Cause | Generates the cause number for a filed case if a number isn’t currently assigned. |
GAW110 | Tennessee Format Cause | Places the dashes in the correct position of Tennessee cause numbers and then sets the formatCause field of the object. |
GAW111 | Tennessee Fix Cause | Expands the cause number input by the user into a valid cause number. |
GAW115 | Indiana State Code URL | Builds an external URL that links to a state of Indiana website for the passed Statute and then sets the stateCodeLink field of the object. |
GAW145 | Indiana Notify EFM | Notify the Tyler EFM when a case known by the EFM is sealed and/or expunged. |
GAW149 | Validations | Validates various database objects. At the moment, it works for OtherIDs. |
GAW152 | Log new Messages | This is meant to automatically log messages in XML format to a log file in /temp. The file name will be in the format JURISDICTION-Messages-year-mm-dd.xml. |
GAW154 | Florida Format Cause | Places the dashes in the correct position of florida cause numbers and then sets the formatCause field of the object. |
GAW027 | Florida Fix Cause | Expands the cause number input by the user into a valid cause number. |
GAW028 | Florida Generate Cause | Generates the cause number for a filed case if a number isn’t currently assigned. |
GAW032 | Maryland Format Cause | Formats petition numbers. Adds the initials of the assigned MASTER. |
GAW033 | Maryland Generate Except Doc | This rule will generate an EXCEPTION ORDER document if the current document being updated is being changed from ‘pending approval’ to ‘exception filed’. |
GAW034 | Maryland Generate Family ID | Generates the family ID if it isn’t already entered. |
GAW035 | Maryland Generate Petition Number | Generates the petition number for a filed statute if a number was not provided. |
GAW036 | Maryland Validate Jail ID | Validates that the Jail ID is entered after the **WRIT on address line 1. |
GAW042 | Indiana Fix Cause | Expands the cause number input by the user into a valid cause number. |
GAW043 | Indiana Format Cause | Places the dashes in the correct position of Indiana cause numbers and then sets the formatCause field of the object. |
Indiana Generate Cause | Generates the cause number for a case if a number isn’t currently assigned. | |
GAW045 | Indiana Generate Petition Number | Generates the petition number for a filed statute if a number was not provided. |
GAW066 | Indiana Marion Co PD | This rule contains all the custom edits and processes for the Marion County Public Defender system. |
GAW088 | Florida Get Census Info | Performs the logic necessary to access the Miami-Dade GIS system to get the census tract (geocode) for an address. |
GAW154 | Florida Format Cause | Places the dashes in the correct position of florida cause numbers and then sets the formatCause field of the object. |
GAW131 | Florida Secure Case Bays | Secures a case for BAYS. |
GAW049 | Indiana Secure Drug Court | This is a security rule designed to limit access to Drug Court related objects (secured objects). Access to Drug Court is |
defined by the authority granted to the Requirement type assigned to the drug court program. | ||
GAW062 | Indiana Force Event ID for Doc | It prevents the adding or updating of the document object if the user is from the OFC groupID and there’s not an eventID tied to the document. |
GAW052 | Indiana Send Trial Msg SJ | Sends a message to COROMA and ANTENN when a trial is scheduled for a JD/JS case. |
GAW046 | Indiana ICJI | This is meant to act as a trigger to automatically add the corresponding EventLog record to the database whenever an action that should update the Log of Juveniles Held happens. |
GAW075 | Indiana St Joe Events | This rule is designed to prevent a prosecutor in St Joseph County from adding/updating a court event for any court except 4. |
GAW041 | Indiana Auto Seal Case | Automatically seals an adoption case. |
GAW048 | Indiana Secure Case | Grants or revokes access to cases based upon specific conditions for Saint Joseph County, Indiana. |
Interfaces
GAW005 | Get IMS Scanned Documents | Interfaces with the IMS imaging system to retrieve documents and insert them into the Documents array being created. |
Repository | This is meant to act as a trigger to automatically add the corresponding EventLog record to the database whenever an action that should update the repository happens. In general, this should be used for any item referenced on the identity or case detail screens. | |
GAW013 | Secure Add By Me | This rule is designed to limit updates and deletes to GAWDBObject objects to the person who added the object. A NotAuthorizedException is thrown if an attempt is made to update or delete a GAWDBObject object by anyone other than the person who added the object. |
GAW018 | SigPlus | This rule is used to process the exit points in the electronic signature capture and display process. |
GAW054 | Interfaces Log Drug Requests | Logs all drug test requests to the outgoing interface file. |
GAW055 | Interfaces Get In Out SJ | Reads St Joe’s time keeping application to determine whether that system thinks the person is in or out. If the time keeping disagrees with the record in Quest, we’ll override Quest to show what time keeping says. |
GAW056 | Interfaces Get Yasi Documents | Retrieve all YASI created documents from the YASI server and place them into the GAWParms searchDocuments TresSet. |
GAW080 | Interfaces MD Warrants | Send a warrant to the state of Maryland. This is a live link, so if it fails, the warrant can’t be added. |
GAW122 | Document to Event Log | This is meant to add an EventLog entry whenever a document of a specified type is completed. It’s the interface to JTAC for the PI/PDR. |
GAW132 | Interfaces Update BI for Requirements | Updates BI Electronic Monitoring system when the requirement status changes to active or the requirement is ended. |