When adding a new release order
 

Creates a unique process number for each new release order.  Format is "YYRON" where YY=Year and N=Sequence Number e.g. "05RO500" or "99RO2002131120".
 

CND331

BR456

When date of issuance is set on a release order and user clicks SUBMIT
 

Release order number status will be set to issued.
 

CND345

BR469

When date of issuance is set and user clicks SUBMIT
 

The mandatory fields in ‘Conditions of Release Detail’ screen must be entered. If not, display message “ You must input mandatory fields in conditions for release detail screen”.
 

CND346

BR470

If there is no check digit number on a process
 

Date of arrest will not be sent to ACIS.
 

CND347

BR471

When date of issuance is set and user clicks SUBMIT
 

Date of arrest, and time of arrest must be input.  If not, display message “You must enter Date of Arrest” “You must enter Time of Arrest”.
 

CND348

BR472

When date of issuance is set and user clicks SUBMIT
 

The mandatory fields in ‘Court Detail’screen must be entered.  If not, display message “ You must input mandatory fields in court detail screen”.
 

CND349

BR473

When the user has initiated the release order for a process
 

A release order number will be created and the status is set as incomplete and the relationship to the case is established with the appropriate sequence number. Format of RO#: (YYROXXXXXXX)
 

CND350

BR474

When a release order is issued
 

Any associated initiating processes or OFAs related to the Release Order should be marked served if it is ‘unserved’.
 

CND351

BR475

When a release order is issued
 

Process tracking history will be updated with Service Date, Serving Agency & Officer, Action = Serve and Status = Serve for the lead case and all related cases (if not already in Process Tracking).
 

CND351

BR820

If the offense requires a fingerprint and the process is either a Magistrate Order or a Release Order on an Initiating Process

 

Check Digit Number must be added with the Date of Arrest on FP Card or Check Digit Reason fields are required.  MSG377: Error: Check Digit Number & Date of Arrest OR Check Digit Reason must be entered.
 

CND352

BR476

When the Release Condition  and/or bond amount is changed on a release order or appearance bond
 

When updating the Release Conditions screen on an issued Release Order,

Based on the value of the “RO and AB send field” in the County Profile and the status of the process, determine whether the County needs to receive the updated values.  If the updates should be sent, send *only* the bond type and amount but no other Release Order information to ACIS. This avoids unintentionally overwriting court info or arrest data which the clerk had changed in ACIS with old information in NCAWARE.
 

CND418

BR559

When a release order is issued by a county other than the originating process county (out-of-county)
 

The county name issuing the release order and the county name where the initiating process was issued is displayed on the Summary tab and printed on the release order.  

Example:  Wake County (issuing) for Durham County (originating).
 

CND592

BR821

If a second or subsequent release order is created on the same process for a bond surrender and no order for arrest exists for that case
 

Servicing information from the original Release Order should pre-populate to the following fields in the RO-Summary Detail screen: Serving Officer, Date Served, and County Served.
 

CND593

BR822

When a release order is issued and the bond type is ‘Unsecured’
 

Automatically create an Appearance Bond (AB) with the defendant as the bondsmen and store AB information in NCAWARE database.  

Print both the Release Order and Appearance Bond when print process option is checked.
 

CND594

BR823

When creating a release order on a case that has service information in process tracking and NO related cases are attached to the Release Order
 

Populate the service date, officer and place of service from process tracking in the Summary Detail screen.
 

CND595

BR824

When creating a release order on a case that has service information in process tracking and more than one related case is attached to release order
 

Do NOT populate the service date, officer and place of service from process tracking.
 

CND596

BR825

If Statewide Search button is selected from the Process Summary tab view
 

Display the Statewide Search by Person screen with defendant information (where applicable) pre-populated from the defendant information in the associated process Defendant tab.
 

CND598

BR827

When displaying or printing Related Cases attached to Release Orders or OFAs

Regardless of the case from which the Related Cases are viewed or printed, the sort order will be:

1. Lead Case
2. Related Cases ascending by year of file number, then sequence number

   Ex.

   12CR500063 (Lead Case)

   10CR500100

   11CR500075

   11CR500080

   12CR500064

·  If an OFA with related cases is attached to the Release Order, all of the OFA related cases will also print on the Release Order as related cases and are subject to the above sort order.

·  CRS case types are sorted in same manner as CR types.

·  The above sort order does not apply to the list of potential Release Cases returned when the “Attach Case” button is clicked on the Release Order/Related Cases tab. This sort order is detailed in RO Related Cases_UC123.doc.

BR1093

When editing the values of the Date of Arrest on FP Card, Check Digit #, Arrest #, Serving Officer, Date Served, or County Served and ANY of these values on an Initiating Process Related Case or an OFA on an Indictment Related Case are different from the current values of the Lead Case other than blank.

Issue a WARNING message:  "A value for one or more of the following fields: Date of Arrest on FP Card, Check Digit #, Arrest #, Serving Officer, Date Served, or County Served conflict with related cases <List cases #'s>.    EDIT will only apply values on this screen to related cases with blank values in these fields.  If the user selects EDIT again, apply all the "to" values to all the selected cases where the from value is blank or does not conflict with the Lead Case value"

Scenarios when the warning message should appear:

Warning Message when RO Summary screen changes values from Lead Case and conflict with Lead Case and Related Cases:

Warning Message when Lead Case is Blank and Related cases have a value different than what was entered on RO Summary fields:

Warning Message when Lead Case and RO Summary Detail values are same but different from a Related Case:

NO Warning message if the RO Summary Detail screen changes values originally defaulted from the Lead Case and no related cases are attached.

CND886

BR1149

When an OFA is served (by RO or Process Tracking action SERVE) and the initiating process is in an unserved state

The status of the OFA and the initiating process (including initiating processes on all related cases) will automatically be marked 'Served' and Process Tracking will be updated to reflect service information.  NCAWARE will also generate Interface message(s) to ACIS to update the initiating process(es) with service information (and court information if served by Release Order) and to remove the OFA Date(s).

CND915

BR1180

If a Release Order's lead case is a converted case that already shows a served status and ALL related cases show a served status,

Set the "Serving Officer" field to display only.

CND997

BR1266

 If a Release Order's lead case is a converted case that is already served and one or more related cases are unserved,

The "Serving Officer" will still be editable.  Show an Informational message "Serving Officer will not be set on the Lead Case since it is a converted case that is already marked as served, but will be applied to one or more unserved related cases."

CND998

BR1267

When a RO is issued on an unserved OFA process

Send to ACIS a 'Reinstatement = Y'  for each OFA offense with a MOD of VL or LC for each related case.  The ACIS system will reinstate each OFA offense with a MOD of VL or LC if Reinstatement field is currently <blank> or <N>.  If the ACIS offense Reinstatement field is already 'Y', the system will ignore the Reinstatement event.  The ACIS case will change the status to 'Pending'.  The ACIS offenses will still display the VL or LC in the Method of Disposition (MOD) field until court appearance and new MOD is updated.

CND1032

BR1309

When a Process Tracking update action of SERVED is submitted on an OFA process

Send to ACIS a 'Reinstatement = Y'  for each OFA offense with a MOD of VL or LC for each related case.  The ACIS system will reinstate each OFA offense with a MOD of VL or LC if Reinstatement field is currently <blank> or <N>.  If the ACIS offense Reinstatement field is already 'Y', the system will ignore the Reinstatement event.  The ACIS case will change the status to 'Pending'.  The ACIS offenses will still display the VL or LC in the Method of Disposition (MOD) field until court appearance and new MOD is updated.

CND1033

BR1344

If one of the following occurs: 1) the OFA is deleted  2) if the OFA is recalled, served, or stricken in process tracking  3) if a Release Order is issued on the OFA

ACIS "Called and Failed Date" should be set to blank.

CND1046

BR1323

When sending the Bond Type to ACIS and multiple release conditions selected

1) Send only the most restrictive condition (Most restrictive to least: Electronic House Arrest (EHA) with Secured Bond, Secured Bond, Unsecured Bond, Custody Release, Written Promise to Appear)

2) If the condition is “EHA”, send it to ACIS as “Secured Bond”.

CND1068

BR1350

When maximum date/time to set conditions of release on form ‘Detention – Probation Violation with Pending Felony or Prior Sex Offense (AOC-CR-272)’ is more than 7 days from Arrest Date

On submit display an error at the top of the screen “Release Order Summary Detail” “Error: Maximum date/time to set conditions of release on form ‘Detention – Probation Violation with Pending Felony or Prior Sex Offense (AOC-CR-272)’ is more than 7 days from Arrest Date.  CANCEL and correct on Additional Forms tab or correct Arrest Date on this screen.”

CND1069

BR1351

When sending the Bond Type to ACIS and multiple release conditions selected

1) Send only the most restrictive condition (Most restrictive to least: Electronic House Arrest (EHA) with Secured Bond, Secured Bond, Unsecured Bond, Custody Release, Written Promise to Appear)

2) If the condition is “EHA”, send it to ACIS as “Secured Bond”.

CND1068

BR1350

When maximum date/time to set conditions of release on form ‘Detention – Probation Violation with Pending Felony or Prior Sex Offense (AOC-CR-272)’ is more than 7 days from Arrest Date

On submit display an error at the top of the screen “Release Order Summary Detail” “Error: Maximum date/time to set conditions of release on form ‘Detention – Probation Violation with Pending Felony or Prior Sex Offense (AOC-CR-272)’ is more than 7 days from Arrest Date.  CANCEL and correct on Additional Forms tab or correct Arrest Date on this screen.”

CND1069

BR1351

If a Release Order is issued on a case that contains one or more additional Unserved

OFAs

Display a new screen displaying the message:

“Warning: This action did not serve one or more Orders for Arrest (OFA) on the case."

The screen will also display the Unserved OFAs and steps to Serve them.

?

?

Upon submitting the RO Summary Detail screen, NCAWARE checks if any unserved OFAs remain on the lead case of the process with which the just issued RO is associated

Display a new screen displaying the message:

“Warning: 

This action did not serve one or more Orders for Arrest (OFA) on the case.

Please serve remaining unserved OFAs by either (A) adding additional release orders or by (B)following these steps:

Press Ctrl+P to print this screen. It shows information you will need for the following steps.

From the NCAWARE Main Menu select “Track a Process”

From the Process Tracking menu, select “Update Tracking for a single process”

For the field “Search for process by” on the Process Search screen, change the default “FILE NUMBER” to “PROCESS NUMBER”

Enter the process number of the OFA to be served (see list below) and select “Search”

Select the Process Tracking action “SERVE” and select Update

Complete the screen for serving the process.

Repeat for each unserved OFA identified below.”

This message will be followed by a list of (all) OFAs on the lead case of the process just served. This list will show the following detail:

Issued Date

Process #

Status

Bond Type

Bond Amount

Date FTA

OFA Reason

Custody Directive

Related Cases

CND1073

BR1355

When updating the Release Conditions screen on an issued Release Order

Based on the value of the “RO and AB send field” in the County Profile and the status of the process, determine whether the County needs to receive the updated values.  If the updates should be sent, send the updated bond type and/or amount to ACIS.

?

When updating the Summary screen on an issued Release Order

Send *only* the arrest information but no other Release Order information to ACIS. This avoids unintentionally overwriting release condition or court info which the clerk had changed in ACIS with old information in NCAWARE. The arrest information to send to ACIS includes Date of Arrest on FP Card, Check Digit Number, Check Digit Reason, Arrest Number.

?

When an Check Digit Number is updated on the RO Summary screen

The RS/RV fields in ACIS should be set to blank when a check digit number is sent

BR5103