- All Known Subinterfaces:
- AssetRemote, CommonWOSRRemote, IncidentRemote, LocationRemote, ProblemRemote, ServiceAddressRemote, SRRemote, TicketRemote, TKServiceAddressRemote, UnassignedWorkViewRemote, WOActivityRemote, WOChangeRemote, WOReleaseRemote, WORemote, WOServiceAddressRemote
- All Known Implementing Classes:
- Asset, CommonWOSR, Incident, Location, Problem, ServiceAddress, SR, Ticket, TKServiceAddress, UnassignedWorkView, WO, WOActivity, WOChange, WORelease, WOServiceAddress
public interface AutoLocatable
The Interface AutoLocatable.
In many cases when the map tab is open and the current record has no address information associated there are many ways to find a related record that can be used to locate the record on the map. This concept is called Auto-locate and its rules are defined below.
The auto-locate rules applies to any map control, not being specific only to existing applications map tabs.
These rules has no relation to any service address configuration, but if any record is automatically inheriting the address from a location record then the auto-locate behaves as if that address was the record address.
Asset:
Asset SA x/y -> location SA x/y -> location parent SA x/y
This rule means that if the asset has no service address associated then look to the asset location record to see if there is a service address record that can be used to locate the asset in the map. If no address is found then look at the parent location record, if there is an address system configured.
Location:
Location SA x/y -> location parent SA x/y
Workorder (WO):
WO SA x/y -> WO Asset SA x/y -> WO location SA x/y -> WO location parent SA x/y
The work order rules must run against the MULTIASSETLOCCI table, and follow the rules for each record found. The system must display a work order marker for each record if the records have different x/y values.
Service Request (SR):
SR SA x/y -> SR Asset SA x/y -> SR location SA x/y -> SR location parent SA x/y
The service request rules must run against the MULTIASSETLOCCI table, and follow the rules for each record found. The system must display a service request marker for each record if the records have different x/y values.