When deleting an initiating process issued in NCAWARE
 

An initiating (original) process can only be deleted prior to service or prior to a Release Order being completed or up until 8 hours after service for Citations, Magistrate Orders (Initiating processes that are automatically marked “Served.”  This is the “8 hour rule”.)
 

CND174

BR249

When deleting a release order process issued in NCAWARE
 

A Release Order cannot be deleted if it has an issued Appearance Bond attached to it.  Display ERROR MSG: ‘Appearance Bond must be removed before Release Order can be deleted.’
 

CND175

BR257

When deleting a release order process issued in NCAWARE
 

Only the user who created it, their proxy, the local data administrator, SSA (State System Administrator), or Clerk is allowed to delete it.  Display an ERROR MSG: ‘Not authorized to delete’.
 

CND175

BR867

When deleting an initiating process from NCAWARE
 

Only the user who created it, their proxy, the local data administrator, SSA (State System Administrator), or Full Clerk is allowed to delete it.  Display an ERROR MSG: ‘Not authorized to delete’.
 

CND176

BR251

If a citation with a CVR 2 & 8 or an AOC-CVR-13 is deleted from NCAWARE after 6PM of the same day the CVR is issued.

  A notification must be sent to ACIS and DMV by listing the deleted process and CVR 2 & 8 or AOC-CVR-13 on the ACIS Error Log. The delete should be processed by ACIS at time delete event is received by NCAWARE; however, the message will be logged to state: “<Court File Number> <Process Type> <Defendant Name> has been DELETED <Delete Reason> by <User Name/Agency>. The associated CVR was also DELETED and proper notification of deleted CVR should be given to DMV.

CND226

BR321

When the user clicks EDIT or DELETE SUBPOENA from the Subpoena tab
 

Only one record may be selected.
 

CND540

BR716

When deleting a warrant (WFA, WCW, FW), Criminal Summons (CS, WCS) or OFA process from NCAWARE prior to service by an agency other than the most recent Printed For Agency with a print date/time of less than 24 hours ago

Display on the ‘Delete Process Reason – After Mode’ screen the WARNING MSG: ‘This process has been printed by <agency name> on <date/time>.  Please notify the agency if deletion is completed.’

CND604

BR1172

When deleting a subpoena process from NCAWARE
 

Only the user who created it or their proxy, the local data administrator, SSA (State System Administrator), or Full Clerk is allowed to delete it.  Display an ERROR MSG: ‘Not authorized to delete’.
 

CND633

BR875

When deleting a Warrant For Arrest, Worthless Check Warrant, Fugitive Warrant, Criminal Summons, Worthless Check Criminal Summons, or an Order For Arrest process from NCAWARE prior to service
 

The system shall remove the deleted process from process tracking
 

CND634

BR865

When deleting an incomplete, complete or issued Release Order process  
 

If the last (only existing) Release Order on the originating process is being deleted, any Related Process with which the Release Order is associated and was not previously served by a LEO using a Process Tracking “Serve” action, should become unserved (i.e., Process Tracking action of “Reset to Unserved”) again in NCAWARE and in ACIS and re-assigned to the previously (last) assigned agency.

For example:

1. A WFA is unserved when the local system sends the Arrest Info Creation request which applies the PT action “Serve with Arrest” and an incomplete RO. If the magistrate now deletes the RO, the WFA will be returned to unserved.

2. A LEO uses Process Tracking action “Serve” to serve a WFA in NCAWARE. Then the local system sends the Arrest Info Creation request which applies the PT action “Serve with Arrest” and an incomplete RO. If the magistrate now deletes the RO, the process will remain served. Due to the LEO’s “Serve” action, an explicit PT action “Reset to Unserved” would be required to reset to unserved.

3. A WFA has two RO processes in NCAWARE. The first is for the initial arrest. The second is for a bond surrender. The magistrate realizes he made a mistake and deletes the second RO. The WFA remains served because of the RO added on the initial arrest..
 

CND635

BR250

When deleting a Release Order that is in an ‘incomplete or complete’ status (not issued)
 

Any authorized judicial official with authority to create a Release Order can delete the Release Order.

(It does NOT have to be the user that initiated the Release Order.)
 

CND636

BR868

When deleting a Release Order process issued in NCAWARE associated with an OFA on a Bill of Indictment

Do not reset the Bill of Indictment to unserved.  Keep the Bill of Indictment as served and send a message to the NCAWARE Business Log.  “<County number><Court file number> Bill of Indictment had a linked OFA that was served and then reset to Unserved.  The OFA process was reset to unserved in NCAWARE but the Bill of Indictment is marked served.  Verify with Clerk of Court if the Bill of Indictment ‘Served Date’ needs to be removed.”
 

CND639

BR877

When deleting an Appearance Bond process from NCAWARE
 

The Appearance Bond can be deleted up until a  subsequent Release Order is issued on the same originating process. Otherwise, display an ERROR MSG:  ‘Cannot delete Appearance Bond after a subsequent Release Order has been issued.’
 

CND640

BR871

When deleting an Appearance Bond process from NCAWARE
 

Only the user who created it, their proxy, the local data administrator, SSA (State System Administrator), or Clerk is allowed to delete it.  Display an ERROR MSG: ‘Not authorized to delete’.
 

CND640

BR878

When deleting an Order For Arrest process from NCAWARE
 

Only the user who issued it, their proxy, the local data administrator, SSA (State System Administrator), or  Clerk is allowed to delete it.  Otherwise, display an ERROR MSG: ‘Not authorized to delete’.
 

CND641

BR872

When deleting an Order For Arrest process from NCAWARE

Send the OFA delete message to the interface to update ACIS, but also send an OFA issued message for every UNSERVED OFA.  This is necessary to insure that ACIS is kept in sync with the current outstanding OFA(s) shown in NCAWARE.

CND641

BR1320

When an Order For Arrest has a status of recalled or stricken
 

The OFA cannot be deleted through NCAWARE by user.  
 

CND642

BR873

When deleting a Release Order process issued in NCAWARE and the reason for the delete is NOT ‘Wrong Name’

Related Cases that created a Merge will not be Unmerged by the delete.  Display WARNING MSG:  ‘Deleting this Release Order does not Unmerge the Merged names, Click DELETE to continue with delete or Click CANCEL to disregard the delete’.
 

CND648

BR883

When deleting an initiating process or when doing an automatic 30-day or manual TMP number delete in NCAWARE
 

The system should remove the associated participants from the database on the process unless they are attached or associated to another process or participant.
 

CND727

BR252

When deleting an initiating process or when doing an automatic 30-day or manual TMP number delete in NCAWARE
 

The system should NOT delete the associated Businesses on the process from the database.
 

CND727

BR255

When deleting an initiating process or when doing an automatic 30-day or manual TMP number delete in NCAWARE
 

The system should NOT delete a LEO from the database.
 

CND727

BR970

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 displaying a field on a process

All fields will display the value from the process archive if an archive is available unless otherwise indicated in the field definition.

CND969

BR1238

If a person record loses the last SID on its associated cases (either because the case was deleted or because the SID was otherwise removed)

Remove the SID and FBI #  from the person as well.

CND1035

BR1311

When attempting to delete a case in NCAWARE with an initiating process type supported by NCAWARE (MO, MOGC, MOWL, MOABC, FO, CS, MWC CS, WFA, FW, MWC WFA)

The delete fails with the error message, "CRS exists. Please initiate case deletion in ACIS." Note: These rules are in place to keep users from accidentally deleting a CR or CRS which they’re not aware of.

CND1036

BR1312

When deleting a case in NCAWARE with an initiating process type supported by NCAWARE (MO, MOGC, MOWL, MOABC, FO, CS, MWC CS, WFA, FW, MWC WFA)

Both CR and CRS portions of the case must be deleted in NCAWARE and ACIS.

CND1037

BR1313

When receiving a delete or expunge event from ACIS

Both CR and CRS portions of the case must be deleted in NCAWARE. (ACIS will have already deleted the ACIS case at all court levels.)

CND1038

BR1314

If both the OFA Reason is one of the FTA reasons and either the OFA is Issued, Reset to Unserved in Process Tracking, or reset to unserved by deleting its last Release Order

ACIS "Called and Failed Date" should be set to the NCAWARE "Date Failed to Appear".

CND1045

BR1322

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 deleting a Release Order

Unmerge any Person record merges caused directly by the inclusion of Related Cases on the Release Order.*

* In the case of a “chained” merge, an unmerge not directly related to the RO or OFA will need to occur before any directly related unmerges can be completed.

Ex.  If A and B were merged into C when an OFA was added and then C was manually merged into person D, then a deletion of the OFA should cause an unmerge of C from D prior to unmerging A and B from C.

n/a

BR5031

When deleting an OFA

Unmerge any Person record merges caused directly by the inclusion of Related Cases on the OFA. *

* In the case of a “chained” merge, an unmerge not directly related to the RO or OFA will need to occur before any directly related unmerges can be completed.

Ex.  If A and B were merged into C when an OFA was added and then C was manually merged into person D, then a deletion of the OFA should cause an unmerge of C from D prior to unmerging A and B from C.

n/a

BR5032

When deleting a Release Order

Do not delete the OCA # and OCA Agency from the case.

pend.

pend.

When deleting an issued Release Order process created by a “Release Order Arrest Info” event (triggered by a local interface Arrest Info Creation Request message after NCAWARE applied the Process Tracking action “Serve with Arrest”)

If the last (only existing) Release Order on a process is being deleted and the process was not previously converted or issued with a “Served” status or served by a LEO using a Process Tracking “Serve” action,  NCAWARE should automatically apply the Process Tracking action “Reset to Unserved” to the process associated with the Release Order, set it to unserved in ACIS and re-assign to the previously (last) assigned agency.

pend.

pend.

When deleting an initiating or subsequent process which originally introduced an agency’s PID to a case (This will occur in response to an AICR message, MOCR message or as part of conversion of the case from ACIS)

NCAWARE will
(1)   remove the agency’s PID from the case

pend.

pend.

If a person record loses the last of an agency’s PID from its associated cases (either because the case was deleted or because the agency’s PID was otherwise removed)

Remove that agency’s PID from the person as well.

pend.

pend.

When an OFA, appended to an unserved Indictment or Other process type, is deleted from NCAWARE

The system will automatically delete the unserved Indictment or Other process from NCAWARE only.  The trigger to ACIS will not send a delete event for the Indictment or Other process.

pend.

pend.

When a user attempts to delete one of multiple Release Orders from the Case Summary RELEASE ORDERS tab, and the selected Release Order is not the most current

NCAWARE will disallow the deletion. On the Case Summary RELEASE ORDERS tab, display an error message: "Error: Only the most recently issued Release Order may be deleted.”

NOTE: Use the Event History Issue Date to determine the most recent Release Order *not* the user-entered "Date Issued" from the RO SUMMARY screen.

BR5083

If a Release Order is deleted and there is another Release Order on the same process

NCAWARE will change the most recently added remaining Release Order’s status from ‘Inactive’ to ‘Issued’.

BR5080

When deleting a Release Order

If present, the CONDITIONS OF RELEASE MODIFICATION HISTORY supplemental form associated with the Release Order is deleted.*

BR5106

When deleting a Release Order

All prior events for the Release Order (issuance, edit events) should remain in the case Event History after deletion.

BR5101