Best practices for working with jw50_Event

Database views beginning with jw50 are meant to replicate the structure of the JustWare system to maintain backward compatibility.

If the term "JustWare" is unfamiliar, you may not need the details on this page. Only customers migrated from a JustWare instance have jw50 views.

Overview

In JustWare, the Event view covers many event types which become separate entities in eProsecutor Online during migration. With the entities separated, the EventID field in the jw50_Event view is no longer unique because it is an aggregate from multiple eProsecutor Online entities. So, when using the jw50_Event view, searching for an event by the EventID can return multiple items instead of the single desired item.

For optimal results, implement one of the following:

Use eProsecutor Online views

The best solution is to replace jw50 views with eProsecutor Online views. This ensures the system returns data from the desired entity and improves performance. For the following event types included in the jw50_Event view, you can use the eProsecutor Online view as a replacement.

The table shows how jw50_Event view fields map to the associated eProsecutor Online view.

Scheduled event

For scheduled events, use the epo_ScheduledEvent view.

jw50_Event view epo_ScheduledEvent view

EventID

id

CaseID

case_id

EventTypeCode

TypeCode

EventTypeDesc

Type

EventTypeMasterCode

TypeCategory

EventCategoryCode

EventCategoryCode

EventCategoryDesc

EventCategory

EventStatusCode

ResultTypeCode

EventStatusDesc

ResultType

EventDt

startDateTime

EventEndDt

endDateTime

Tracking

For tracking, use the epo_Tracking view.

jw50_Event view epo_Tracking view

EventID

id

CaseID

case_id

EventTypeCode

TrackingTypeCode

EventTypeDesc

TrackingType

EventTypeMasterCode

TrackingTypeCategory

EventTypeCodeType

TrackingTypeCodeType

EventCategoryDesc

EventCategory

EventDt

startDateTime

EventEndDt

endDateTime

EventStatusCode

StatusCode

EventStatusDesc

Status

Case documents

For Case Documents, use the epo_Document view.

jw50_Event epo_Document

EventID

id

CaseID

case_id

Date

dateFiled

Title

nameExact

FolderID

folder_id

Sealed

DocumentIsSealed

Case status

For Case statuses, use the epo_CaseStatus view.

jw50_Event view epo_CaseStatus view

EventID

id

CaseID

case_id

EventTypeCode

ValueCode

EventTypeDesc

Value

EventDt

beginDate

EventEndDt

endDate

EventNotes

notes

Sentence

For Sentences, use the epo_Sentence view.

jw50_Event view to the epo_Sentence view

EventID

id

CaseID

case_id

EventTypeCodeType

SentenceTypeCode

EventTypeDesc

SentenceType

EventTypeCodeType

SentenceTypeCodeType

EventTypeMasterCode

SentenceTypeCategory

EventLocationCode

SentenceLocationCode

EventLocationDesc

SentenceLocation

EventDt

sentenceBeginDate

EventEndDt

sentenceEndDate

EventStatusCode

status

CountID

associatedCharge_id

EventDurationDesc

sentenceDurationDesc

Amount1

amount

Amount2

amountReducedTo

Sentence condition

For Sentence Conditions, use the epo_SentenceCondition view.

jw50_Event view epo_SentenceCondition view

EventID

id

EventTypeCode

SentenceConditionTypeCode

EventTypeDesc

SentenceConditionType

EventDt

sentenceConditionBeginDate

EventNotes

notes

EventAmountToMin

length

Use precise jw50 views

The second solution is to use jw50 views with a precise scope. Not every event type included in the jw50_Event view has a more precise jw50 view. The following are a few examples of precise jw50 views:

  • Non collectible financials use the jw50_NonCollectableFinancials view.

  • Case Documents use the jw50_CaseDocument view.

  • Sentences use the jw50_Sentence view.

Include filters on jw50_Event

The third solution is to add more filters when using the jw50_Event view.

These filters should include:

  1. A filter on the event type. This eliminates the issue by limiting the returned results to an event type. You can use the EventEntity field in the jw50_Event view for this filter.

    The following table shows the value of the EventEntity field for each event type:

    Event type EventEntity value

    Scheduled event

    ScheduledEvent

    Task

    CheckListItem

    Tracking

    Tracking

    Non collectible financial

    NonCollectibleFinancial

    Case document

    CaseDocument

    Person document

    PersonDocument

    Case status

    CaseStatus

    Sentence

    Sentence

    Sentence condition

    SentenceCondition

  2. Use a filter on the Case or Person entities. This cannot fully resolve the issue by itself, but it improves the performance of the jw50_Event view. Use this filter type with an event type filter.