Info |
---|
This guide has been reviewed against our global client base and classed as relevant to all regions |
This article outlines how a change request for an area needs to be submitted to the Reapit Service Desk
An area is assigned to every property added to your system and used in applicant requirements to establish which areas each applicant is looking to buy/rent in
If intending to remove, replace or add areas, it is important to ensure that such changes will not impact the client website or portals - feeds for non-UK based portals in particular (i.e. Dubai, Ireland, etc) use area information in their search results, therefore removing an area could also remove a sizeable portion, if not all, of the agent’s stock from the internet - if in any doubt, ask for assistance before proceeding requests to remove areas
...
...
For an area to be changed and/or a new one to be created, Reapit will require the following information: Structure of new area layout Detailed map showing the coverage of each area Default groups for office requesting area change Removing/replacing areas: when areas are to be removed, a list detailing relationship between old and new areas Details of the information required is covered in the following sections
|
1. Structure of new area layout The structure of a new area layout should list the groups and the areas included within that group Sub groups can also be used Reapit need to know where the new areas will fit into the existing area structure set up
In this example below, Staffordshire is the group and all the areas beside it make up the Staffordshire group Staffordshire: Tamworth, Wilnecote, Polesworth, Dordon, Fazeley, Glascote
|
2. Detailed maps A detailed map showing the span of each area is required |
...
should not be left between areas
Map boundaries can be drawn using Google Maps - click here for more information
In this example, the map shows the areas of Tamworth, Glascote, Wilnecote, Polesworth, Fazeley and Dordon - all areas need to be labelled as they should appear on your system
| |
...
Image Added Info |
---|
If an existing area is to be amended, this may have an effect on match results as properties might no longer be associated with a particular area See step 4 for more information |
|
3. Default groups Each office can be configured to have a default group of areas which will be visible initially - the list can then be expanded to view all areas |
4. Removing/replacing areas When areas need to be removed and new ones added, a list should be provided to outline the old and new areas For example: the areas of Wilnecote, Shirley, Knowle and are to be removed and new areas of Dordon, Fazeley & Solihull need to be added as new areas - this list should be provided: Old areas Tamworth, Wilnecote, Polesworth, Glascote, Shirley, Knowle, West Bromwich New areas Tamworth, Polesworth, Dordon, Fazeley, Glascote, Solihull, West Bromwich
Information to explain the relationship between the old and new/existing areas should also be provided to explain what to do with properties currently assigned to the existing areas (which then has a knock-on effect with applicants searching in those areas) For example, this list could be provided: Wilnecote is now Tamworth Shirley is now Solihull Knowle is now Solihull
|
Info |
---|
When you have this information ready, submit an area change request using this form (in Configuration Option, select Area, then use the Description field to enter the detail of the change) |
Related articles
Filter by label (Content by label) |
---|
showLabels | false |
---|
max | 5 |
---|
spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@a45 |
---|
sort | modified |
---|
showSpace | false |
---|
|
...
| reverse | true |
---|
type | page |
---|
cql | label = "match" and type = "page" and space = "RW" |
---|
labels | property |
---|
|
Excerpt |
---|
|
How a change request for an area needs to be submitted to the Reapit Service Desk |