Configuration

• a Microsoft Access database if it ends with ".mdb", its path is physical if it includes "\" otherwise it is a URL; else
• an OLE DB Data Link if it ends with ".udl", its path is physical if it includes "\" otherwise it is a URL; else
• an OLE DB (Object Linking and Embedding Data Base) connection string if it contains "provider="; else
• an ODBC (Open Data Base Connectivity) connection string.

DbConnection setting values may be encrypted using the SISfm Encrypt Database Connection Strings utility.

• SQL - specify a database connection string (e.g. using the AdsDsoObject OLE DB provider) plus setting DbTableLDAP.
• .NET - specify an LDAP server URL using the ldap: protocol, and do not set DbTableLDAP. Note that this method requires the adsPassword session variable.

• for SQL Server by executing:
  EXEC sp_set_session_context @key='UserID', @value='adsName';
• for Oracle by executing:
  CREATE OR REPLACE CONTEXT sisfm USING sisfm_set_key;
  CALL sisfm_set_key('UserID', 'adsName');
  (note that the procedure sisfm_set_key must exist in the database)

NOTE that the SMTP server used by SISfm to send emails is configured separately in the <system.web> section of Web.config, refer to the supplied example for details.

1. The chart type, one of: AreaChart BarChart ColumnChart ComboChart Gauge LineChart PieChart.
2. Zero or more options for that chart type.

1. The first column of string data type.
2. One or more subsequent columns of numeric data type, according to the chart type.

• Space Manager displays the Output Log button in its menu.
• Edit Occupants is available for rooms (when People Manager is not enabled).
• All details pages display the Add, Remove and Edit buttons.
• All details pages display all fields.

NOTE that if access security is enabled, use of the equivalent access security functions is recommended instead of this setting.

NOTE that the use of an additional key field (to model multiple roles for the same person, for example) is not recommended unless table em is only updated from a product which supports such a model correctly (such as PeopleSoft or Alesco).

1. The person type, a em.em_type value.
2. A comma-separated list of required fields in table em.

1. The facility type code, e.g. CP.
2. The facility type name equivalent to "building", e.g. Car Park.
3. The facility type name equivalent to "floor", e.g. Level (if omitted, floor details are not displayed).
4. The facility type name equivalent to "room", e.g. Bay.

• delimited format - by specifying a single delimiter character. This is used to delimit S, B, F, R so that they can be of variable length. The delimiter must be one of the !$+-.@^`~ characters.

  Note that the ; character is also permitted as a delimiter if XSSValidateOff is TRUE.

  Example: 20.15A.01.102

• fixed format - by specifying a character field layout such as SSBBBbFFR.

  Fields must be defined in this order. Each may have any number of characters. The room ID field extends to the end of the loc_code value (whose length may vary), so a single R is sufficient. Any other characters in the LocCodeFormat value signify characters in the location code that are not used. The building sub-ID is intended for buildings identified with a suffix character (e.g. building 15A), all zeros signifies no suffix.

  Example: 20015A01102

where:

S is the site ID (site.site_id).
B is the building ID (first part of bl.build_no).
b is the building sub-ID (optional, second part of bl.build_no).
F is the floor ID (rm.fl_id).
R is the room ID (rm.rm_id).

If omitted, delimited format using a decimal point (.) is expected.

NOTE that the above fields must not contain:

• the loc_code delimiter character;
• characters *<>":?/\| which are not permitted in Windows file names;
• characters #$&+=@ and the space character, which are not permitted in URLs without encoding;
• characters %[]{}^ which are generally considered unsafe in URLs without encoding;
• characters '(; which are reserved by SISfm.

Thus characters permitted in these fields for SISfm are:

• characters ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
• characters 0123456789
• characters !)-.`~_ (less the loc_code delimiter character, except rm.rm_id which may contain one)

Some permitted characters should be avoided for readability or keyboard entry reasons.

• default format - by specifying no value. The default format (e.g. ML 15A.102) is displayed, in which the site ID is converted to its site Code and the floor ID field is not included, so this is best suited when the floor ID prefixes the room ID.

• location code format - by specifying the value LocCode. The location code value itself is displayed, which is best suited for the delimited format.

• custom format - by specifying any value optionally containing one or more occurrences of {S}, {B}, {F} and {R} which are replaced by the site ID, building ID, floor ID and room ID respectively. Repeat S,B,F,R to specify a minimum field width, this will be left padded with zeros. For example {S}{BB}.{R} displays site 3, building 5, room 101 as 305.101.

1. The database identifier, as an DbConnectionAsset entry number, or zero for the Facility database. Must be zero for Asset Manager.
2. The database table name. This may instead be a table alias name followed by the actual table name and an SQL WHERE clause to specify a subset of rows in the table, for example museq[eq WHERE eq_std='MUS'].
3. A title for the asset category stored in this table.
4. An optional '~' separated list, to enable its availability in Asset Manager, of:
   1. A definition of fields in this table for asset items.
   2. An optional definition of fields in this table for asset component items.
   where each field definition is a space-separated list of:
   • field group definitions, as group titles enclosed by '|' and with '_' replacing spaces. Group title 'Photo' specifies a field group to contain a photo thumbnail with its name and description.
   • the * character, to specify a component count field for asset items.
   • field names, or '-' separated lists of names of fields in dropdown field sets, for the preceding group. If a field name is followed by '!' then it will not be included as a List column.

1. The name of a table/alias specified by an AssetTable setting.
2. The sub-table name.
3. A sub-table title.
4. A field definition list, as for the AssetTable setting.

1. A title for the links stored in this table.
2. A folder URL, under which location code sub-folders store the link targets (for details see External links).

1. The database identifier, as an DbConnectionAsset entry number, or zero for the Facility database.
2. The database table name (for details see External links).
3. A title for the links stored in this table.
4. An optional URL base for the link targets stored in this table.

1. The database table name (for details see External links).
2. An optional URL base for the link targets stored in this table.

1. The name of the field in the table, or a field calculation. A field name value may optionally be followed by a colon, then one of the following descriptors:
   • csi - values are converted to asset CSI Classification descriptions, and a selector button is included when editing. The database field must be a string data type.
   • phone - phone number validation is performed when editing. Values may only include digits and spaces, plus a leading + for international numbers, otherwise a leading 0 and nine more digits. The database field must be a string data type.
   • link:URL - values are displayed as links, which display URL in a new window, replacing any * character in URL by the value.
   A field calculation value takes the form (<expression>) AS <alias> where:
   • expression - is an SQL expression which is valid for the table in SQL SELECT and ORDER BY clauses for the database in use. NOTE that SQL errors will be issued if the expression is invalid. NOTE that it may be necessary to review the SQL that uses this expression for suitability (to see this, introduce an error in it).
   • alias - is any valid SQL field alias name which does not conflict with feature field names in this table. Note that the alias name is displayed in the Map Enquiry advanced theme column list, and as the theme legend title if selected.
   Access security should be provided for a field calculation by creating a dummy field named alias in this table, and defining access to this field in the sisfm_flds table.
2. (not currently used)
3. (not currently used)
4. The column (1,2,...) in which to show the feature.
5. The heading under which to show the feature.
6. The description of the feature. If omitted its sisfm_flds.ml_heading is used.
7. (not currently used)

1. May be an amenities name enclosed in * characters. For example the value *amenity* specifies amenities stored in the asset_amenity table. Other amenities names may be specified to reference other types of amenities in other tables whose names and amenity type fields are named correspondingly.

2. A "D" signifies that this is a Default feature that will always be shown in a search result, otherwise it will only be shown if it has been searched upon.
3. An "S" signifies that this is a Search field that will be searched for text matches.

7. A "Q" signifies that this field is available to the Map Enquiry Room dialog Quick Edit function.

• the location search keywords site, building, floor, room.
• alternative facility type codes with descriptions in parentheses, if in use, e.g. cp (car parks).
• the condition search keywords defined by Search values (perhaps duplicated to include operator options).
• text which is likely to be commonly used in condition searches or text searches.

1. The search text keyword.
2. The name of the field (col), which must exist in the rm table.
3. The type of search comparison to make:

   num	Numeric, when followed by an optional operator from  =  >  <  >=  <=  <>  followed by a number.
   str	String, using the following operator and field value
   str_after	String, when followed by a further search term, which is compared for any match (col LIKE '%term%').
   bool_num	Boolean numeric (col >= 1).
   bool_y	Boolean text (col LIKE 'Y%').

4. The comparison operator, one of  EQ  GT  LT  GE  LE  NE  (which are translated to the SQL operators  =  >  <  >=  <=  <> ) or LIKE or IS or IS NOT. Used for type str, and as the default operator for type num.
5. The comparison value, used for type str. The comparison operator and value must form legitimate SQL when combined.

• CSV - comma separated values (default).
• TXT - tab separated values.

• Photos - photos and documents.
• Projects - projects in site and building details.
• BuildingLeases - building lease notes in building details (see RoomBuildingLeases setting).
• RoomUtilisation - room utilisation in room details (see RoomUtilisation* settings).
• Links - links (see FolderLinkTable, *LinkFolder and *LinkTable settings).
• SiteBuildingPlanLinks - building plan links in site details in Map Enquiry.
• WorkRequests - work requests in site, building, floor, room and asset details.

• as the from address for emails sent by this module.

Note that the chart SQL must include both a table alias CHART_TABLE and a WHERE 1=1 placeholder for adding site, building, floor, room restrictions

• Room details page (default RoomWindow)
• Custom page specified by MapLinkUrl (default CustomWindow)
• Selected items page specified by MapItemLinkUrl (default SelectedItemsWindow)
• Item pages specified by their LinkAttribute attribute (default ItemWindow)
• Asset details page (default AssetWindow)
• Icon move page - not currently used (default IconMoveWindow)
• Site details page (default SiteWindow)
• Building details page (default BuildingWindow)
• Floor details page (default FloorWindow)
• Room cleaning schedule page (default RoomCleaningWindow)
• People Manager show plan page (default PersonMapWindow)
• Person details page (default PersonWindow)
• BIM properties page (default BIMWindow)
• Project details page (default ProjectWindow)
• Dashboard page (default DashboardWindow)

1. The layer name.
2. The SQL replacing the View Points table. This must supply the same field names as the original View Points columns, plus any others used in its where clause. Note that the View Points parameters may only specify a single table.

1. The maximum image size supported by the Web Map Server in pixels, default 2880.
2. The image opacity, in range 0 to 1 or 0% to 100%. Optional, default 1.

1. Layer name (as modified using MapLayerAlias settings).
2. Image properties, as a space-separated list of
   1. The maximum image size supported by the Web Map Server in pixels, default 2880.
   2. The image opacity, in range 0 to 1 or 0% to 100%. Optional, default 1.
3. The URL to get a map image. This should be equivalent to that used for the Cadcorp OGC WMS overlay (Cadcorp does not provide an API method that Map Compiler can use to obtain this, hence its duplication here). Its BBOX, WIDTH and HEIGHT querystring parameters must be present, and may have any values suitable for testing. To obtain this URL, display a representative image from the required Web Map Server using a web browser, then if necessary view the source of the page to obtain the URL of the image itself.

1. Layer name (as modified using MapLayerAlias settings).
2. The layer opacity, in range 0 to 1 or 0% to 100%. Optional, default 1.
3. The layer supplier, one of:
   • OSM - OpenStreetMap.
   • Wiki - Wikimedia Maps.
   • GoogleMaps - Google Maps.
   • GoogleSatellite - Google Satellite.
   • GoogleSatelliteHybrid - Google Satellite Hybrid.
   • GoogleTerrain - Google Terrain.
   • GoogleTerrainHybrid - Google Terrain Hybrid.
   • GoogleRoads - Google Roads.
   • EsriNationalGeographic - ESRI NatGeo World Map.
   • EsriWorldOceanBase - ESRI World Ocean Base.
   • EsriWorldImagery - ESRI World Imagery.
   • WMTS - another supplier (when the following further values are required).
4. The EPSG code specifying the coordinate reference system of the data supplied.
5. The layer name in the data supplied.
6. The URL of the capabilities of the data supplied, as an XML document.
7. Supplier attribution text (optional).

NOTE: Ensure that map service providers' terms of use are complied with.

1. Layer name (as modified using MapLayerAlias settings). The layer should be compiled from a Cadcorp View Points overlay.
2. Key column name, default id. The layer may be edited if this column exists, and a single View Points table is used, according to its data type:
   • if integer, the Edit dialog displays its value read-only, and the next highest value is used when saving new items.
   • otherwise, the Edit dialog displays its value for editing, and this is tested for uniqueness when saving.
3. Description column name, default description.
4. scale - point icon scale, default constant icon size.
5. angle - point icon angle (clockwise degrees from horizontal), default 0.
6. icon - point icon file name, default Pin.gif.
7. link - point icon hyperlink URI, default none. This may include placeholders $$column$$, where column is the name of a column in the table, to include its value in the URI.
8. description - point description, shown in point dialog by default, found by Local Search.
9. Point label alignment:
   • OVER - place label over the point icon.
   • otherwise - place label above the point icon.

1. Layer name (as modified using MapLayerAlias settings). The layer must also be present in MapLayerPoint settings.
2. Node table name. Must be the layer's View Points dataset table, and may have additional attribute fields.
3. Link table name. Must have fields id,node_id1,node_id2, and may have additional attribute fields.
4. Cable table name. Must have field id, and may have additional attribute fields.
5. Cable links table name. Must have fields id,link_id.
6. Circuit table name. Must have field id, and may have additional attribute fields.
7. Circuit cables table name. Must have fields id,cable_id,core_a,core_b.
8. Circuit splice table name. Must have fields node_id,cable_id1,core_a1,core_b1,cable_id2,core_a2,core_b2.

Table sisfm_tbls is used to define alternative terms for Node, Link, Cable and Circuit (e.g. Pit, Duct, Pipe).

NOTE that this type of layer is experimental, and that its tables must be populated manually.

An different approach is the use of Node and Link item topology in an 'other links' layer.

1. Type, one of:

   tip	for a tooltip field.
   label	for a Label theme.
   colour	for a Colour theme.

2. Field name:
   • any field in the rm table, to specify room themes on floor plans.
   • any field in the bl table, prefixed by bl., to specify building themes on site plans.
   • any field in a View Points table, prefixed by its table name, to specify point themes on site or floor plans:
     • field values may include the | delimiter to display them on multiple lines. An example is a field of occupants for a room zone. When using SQL Server, such fields can be specified based on the following self-contained example:
       SELECT TOP 1 STUFF((SELECT '|' + RTRIM(bu_id) FROM bu FOR XML PATH ('')), 1, 1, '') AS bu_id_list FROM bu
     • for tip, if no fields are specified, all attribute fields of the table are included, with field name as description.
     • for label, field name icon specifies the point icons themselves, to allow them to be turned off when other labels are present.
     • for colour, the label background is themed for View Points layers.
   • for the label and colour types, the name of an 'other links' layer, followed by ., followed by the name of a field in the layer's SVG elements (such as description).
   • a field calculation, of the form (<expression>) AS <table>.<alias> where:
     • expression - is an SQL expression which is valid for the table in SQL SELECT and ORDER BY clauses for the database in use. NOTE that SQL errors will be issued if the expression is invalid.
     • table - is the name of the table.
     • alias - is any valid SQL field alias name which does not conflict with feature field names in this table.
   The following special field name values are available:

   bl.id	for building number.
   bl.area	for building area (the field defined by BlAreaField).
   id	for room number.
   bu_id	for room business unit.
   capacity	for room capacity (rm.RoomCapacityField if People Manager is not enabled).
   occupants	for room occupants (symbol label theme).
   occupantlist	for room occupants (text label theme).
   vacancies	for room vacancies (the difference between rm.RoomCapacityField and the number of occupants). Not used if People Manager is enabled.
   em.field:colour	for flagged room occupants, e.g. fire wardens (symbol label theme) where:. field is the name of a field in table em containing 'Y' to flag that occupant. colour is one of Red Green Blue for the colour of the flag symbols. If the colour is Red then fire hose reel icons are also displayed for any unoccupied rooms with names containing fire (such as Main Fire Cupboard).
   link_table:field	to colour theme network links using table link_table (see MapLayerNetwork).

3. Field description, required for themes, optional for tooltip.
4. Cost lookup table name. Optional and only used by colour themes. The name of a database table with two fields:
   • Field containing theme values, with the same name as the field being themed.
   • Field containing the $/m² cost for theme values, with the cost lookup field name.
5. Cost lookup field name. Optional, if omitted the name of the cost lookup table is used.

1. Themed field name, as specified by a MapTheme setting.
2. Themed field value, or value range:
   • Value - a single expected item value. Note that rm_type values are expressed as rm.rm_cat|rm.rm_type (e.g. 6|601). Optional if MapLegendColours is set to AFM.
   • Value range - a range enclosing expected item values, specified as minimum and maximum values separated by a tilda (~). Either value can be omitted to specify an open ended condition. Range values can be numeric or non-numeric. Item and range values are compared as numbers if both are numeric, otherwise as strings. Comparisons use greater than on the minimum, and less than or equal to on the maximum range value. The order of legend entries is obtained by sorting these values as strings, left-padding minimum values with zeros if necessary.
3. Colour for this field value, as hexadecimal RRGGBB. The default theme colour for unspecified field values is 666666. Optional if MapLegendColours is set to AFM.
4. Description of this field value. Optional. For fields rm_cat, rm_type, bu_id, dv_id, dp_id the description overrides the description obtained from the facility database. For other fields the description overrides the field value.

• if colours are omitted, the Archibus colours in field hpattern_acad of the applicable table (bl,rm,rmcat,rmtype,bu,dv,dp or any Archibus field validation table) are used if this field exists.
• if AFM2 is specified, hpattern_acad values are interpreted as BGR instead of RGB, to suit this change made by Archibus in Web Central.
• if values are also omitted, the values present in the database are used.

1. Map icon name, relative to the folder specified by the DataFolderMapIcon setting.
2. Description to appear in the point legend.

• LABEL - the label is centred (the default)
• ICON - the icon is centred
• BOTH - the icon is above and the label is below

1. The height of walls (per storey), in metres. Optional, walls are not displayed if the setting is not defined.
2. The SVG styles for walls. Optional, default stroke:#666666;stroke-width:0.05px;fill:#666666;fill-opacity:0.2.

1. The height of walls, in metres. Optional, walls are not displayed if the setting is not defined.
2. The SVG styles for walls. Optional, default stroke:#666666;stroke-width:0.05px;fill:#666666;fill-opacity:0.2.

NOTE that if set to TRUE there will be a delay loading plans if the Way Finder server is not running.

1. The X position of the top left of the print title field, in map print units relative to the bottom left of the print.
2. The Y position of the top left of the print title field, in map print units relative to the bottom left of the print.
3. The size of the print title field, as a scale factor.
4. A short description of the print title field, to appear in the Print menu.

1. A title for the search.
2. An advanced search string, to which entered search text will be appended. This may include placeholders $$site$$, $$building$$ and $$floor$$, which will be replaced by site, building and floor search clauses matching the currently displayed plan. Use an empty value to allow a complete advanced search string to be entered (when the comma may be omitted).

NOTE that latitude and longitude are approximate values only. They are calculated using linear interpolation from the homeLatLon attribute of the map element of map XML files.

• dp_name - the person's department name (dp.name).
• email_name - the person's email address (em.email) omitting @domain.

• as the from address for emails sent by this module.
• as the approver if no approvers were found for a booking.
• for requesting room approval access.

1. The link button caption.
2. The link condition field: an optional table rm field name:
   • name undefined or field absent: the link will be displayed for all rooms.
   • field value Y: the link will be displayed for this room.
   • field value NT: the link will be displayed for this room, and the room timetable will not be displayed (regardless of other BookTimetableLink settings).
   • other field value: the link will not be displayed for this room.
3. The link URL, which may include the following placeholders:
   • $$YYYY$$ - the current year.
   • $$LOC_CODE$$ - the room location code.
   • $$LOCATION$$ - the room code, as bl_id.fl_id.rm_id.
   • $$LOCATION2$$ - the room code, as site_id-bl_id.fl_id.rm_id.
   • $$SITE_ID$$ - the site code.
   • $$BL_ID$$ - the building code.
   • $$FL_ID$$ - the floor code.
   • $$RM_ID$$ - the room code.
   • $$DATE_TODAY$$ - the current date, as yyyy-MM-dd.
   • $$DATE_LAST_MONDAY$$ - Monday last week, as yyyy-MM-dd.
   • $$DATE_LAST_FRIDAY$$ - Friday last week, as yyyy-MM-dd.

• as the from address for emails sent by this module.
• as the approver if no approvers were found for a booking.
• for requesting asset approval access.

• as the from address for emails sent by this module.

• to distinguish between Administrator and Business Unit move initiators.

• 1 - the user specifies Project and Cost Centre, and the approver is obtained using SELECT dp_fin_bum_email FROM dp WHERE dp_fin_id_new LIKE '%CostCentre%'
• 2 - the Cost Centre is the Division ID dv.dv_id and the approver is obtained using SELECT head_email FROM dv WHERE dv_id='CostCentre'

• 1 - text specifying PC/fax/printer details.
• 2 - a table of equipment with tag, description, from and to location fields.

• 1 - text specifying removalist details.
• 2 - fields for removalist required, number of boxes, delivery date, description.

• as the from address for emails sent by this module.

Note that the chart SQL must include both a table alias CHART_TABLE and a WHERE 1=1 placeholder for adding site, building, floor, room restrictions

• The first value is the table name (one of work_request work_process work_schedule work_date work_order site bl fl rm eq).
• Subsequent values are the names of the columns to include (these need not include PK or description columns).

• as the from address for emails sent by this module.

1. The heading colour, as hexadecimal RRGGBB.
2. The heading text.
3. Selection criteria as up to two semicolon-separated values:
   1. The room classes to include, as for RoomClassOccupant.
   2. An optional further restriction as an SQL WHERE clause using room table fields (e.g. rm.capacity>0 AND rm.capacity<4).

• as the from address for emails sent by this module.

• dp_name - the person's department name (dp.name).
• email_name - the person's email address (em.email) omitting @domain.

NOTE that access token requests include the following parameters which must be supported:

• grant_type="client_credentials"
• scope="access_token"

1. Overlay name - the name of the overlay in DwgTemplateSwd.
2. The physical path of the folder containing floor plans as DWG files, or Windows shortcuts to them, in the usual SISfm subfolder structure.

• INTERNAL - one polygon representing internal gross area
• EXTERNAL - one polygon representing external gross area
• BOTH - two polygons of smaller and larger area representing internal and external gross areas
• NONE - gross area polygons are not processed (the default)

1. Overlay colour override, as hexadecimal RRGGBB. In addition, a Blank brush override is applied.
2. Overlay name, and also the name of an overlay Filter if this exists.
3. DWG file path, relative to the DWG file being compiled, containing DwgNameRegularExpression replacement parameters.

Example to add ...\A\01B201-A-FP0301.dwg as overlay Base Plan at position 1 when compiling ...\SO\01B201-SOPL0301.dwg:

DwgNameRegularExpression: ([^-]*)-SOPL(.*)
DwgAddOverlay1: 000000:Base Plan:..\A\$1-A-FP$2

1. The file format, one of PNG or SVG.
2. The PNG scale, as pixels per metre. Ignored for SVG.
3. The plan orientation, one of:
   • UNROTATED - e.g. geo-referenced.
   • ROTATED - rotated to the view rotation defined in the SWD file.
4. The overlay to be labelled, as an index to the list below of overlays to be included (e.g. 1 for the first). Optional.
5. The label text, as a Cadcorp expression.
6. The label height, as a Cadcorp expression.
7. The label colour, as hexadecimal RRGGBB.
8. The name of the first overlay to be included.
9. The name of the second overlay to be included. Optional.
10. etc.

• Blank - the item will have zero fill opacity, so the fill is invisible but a position within the the item will select it.
• Hollow - the item will have no fill, so a position within the the item will not select it (unlike in Cadcorp SIS).

1. The layer name. This may optionally be two '~' separated values:
   1. The FacilityType code for which layers are to be added. Use an empty code for the default facility type.
   2. The layer name.
2. The View Points parameters. These are the same As the mapEnquiry/getViewPoints.aspx querystring parameters (for an example see Troubleshooting), but:
   • replacing & by +
   • omitting x1 And y2
   • supporting the following placeholders:
     • $$map_name$$ which will be replaced by the floor plan loc_code.
     • $$site_id$$ which will be replaced by the floor plan site_id.
     • $$bl_id$$ which will be replaced by the floor plan bl_id.
     • $$fl_id$$ which will be replaced by the floor plan fl_id.

1. The facility type code to be compiled. For the default facility type, use Building.
2. The name of site plan overlays containing building links.
3. The name prefix of the overlays containing building floor plans to be added to the site plan. These are added after the building links overlay with names prefix..0 containing all the building floorplans linked from the site plan, prefix..1 for those one level higher, etc.
4. The name of floor plan overlays containing room links.
5. The scale of static room labels, e.g. 1000.

Building floor plan layers are only compiled for floor plans with an SWD file, and which are in the same coordinate system as the site plan (e.g. geo-referenced).

If value 3 is in the OverlayLinks setting, rooms on floor plans can be selected and themed, otherwise they are shown with static room number labels.