Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Nearby cases

Updated on January 18, 2021

The feature “Nearby Cases” is used to view locations of other cases, which are present near the given case. The type of cases to be seen and the range/radius can be set, and once you click on search, based on the casetype and range selected, the cases are visible on a map as shown below. When clicked on the location pin, the details of the case are shown.

There are two main steps involved in this functionality.

  1. Saving the given location by the user into database.
  2. Populating nearby cases, based on the location persisted in the previous step.

    The address is persisted into the index table as shown below. A location parameter is passed to the persist proximity location step.

Sample example of nearby cases feature

  1. Persist proximity location: In this step, we will persist the given location into the index table(Index-Location class in the database), using a declare index, “ProximityLocation”. The location parameter, i.e., the address property which has to be stored has to be passed as a parameter to this step. For example, my first step is manage interview, in which my address property is stored in “.interview.LocationDetails.Location” and this is now passed as a parameter to persist this location into the index table.
  2. Nearby Cases: In this step, the same location parameter is sent likewise in step 1. This step fetches the latitude and longitude values of the given location using a google API. When the end user selects the type of case and the range/radius, a datapage, D_pzFetchProximityCases is run and all the selected cases present in the given range are fetched, they are shown on the map.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us