Administration

Customization Resources

Customization is possible at many levels in PlanTest. This document covers general information and references to other documents both inside and outside the PlanTest 4.0 help pages.

Abbreviations used in this document

Customization Resources

Further work to remove SI only items, and provide links within help pages or online sources.

Customization of PlanTest runs the gamut from CSS files for specific report pages, to assemblies for analysis or architecture extensions. Let’s break it down:

1. Analysis – assemblies. Automated tests specific to client site, created by Seaconis developers.
2. Extensions – assemblies. Client specific extensions to PT architecture. First created to allow custom services to be called early in initialization, rather than during analysis or UI interaction. As of 3.2 all jurisdictional code is in extension assemblies.
3. Workflows – XML files. Seaconis schema for data dependent workflows used to drive analysis. There are usually several, and are a key part of the user experience.
4. Data – all sorts. Data used by PT can be of several types.
   • Survey data – various files or streams from services. Part of transactional data, or PO but deserves special mention as a distinctive competence of PT.
   • Transaction data– various files or streams from services. The data being examined.
   • ICSM LandXML – ICSM and SG format for cadastral survey data.
   • SG LandXML (SGLX) – Broad scope data for SG transactions.
   • PO data – per original or Point of Truth data from the cadastral registry or fabric.
   • Scanned Plans – georeferenced TIFF files. Paper plans scanned to raster and georeferenced to overlay with digital data on map.
   • Ad Hoc - data loaded into new objects and feature layers. Like Singapore occupations.
5. ESRI map files
   • Geodatabase – MDB files. Client data models mapped to ESRI database, using cadastral editor and extended attributes.
   • Layers – ArcMap layer files. Files are used as source of symbology, labeling and numerous other map display properties -including scripting. Layer files are not applied directly, but queried for various properties to apply to PTd maps.
   • Customization Resources. ArcMap templates for client specific map types (for printing). Most use of PTd maps is dynamic, but layout toolbar is used to create a printable map.
6. Web page/report files -extensive use of web technology in PTd allows site customization of large parts of the applications presentation and interaction with results.
   • HTML for PTd results browsers. Each results report or other web browser-based UI module has an associated HTML file. This is usually a brief page setting up the JavaScript and CSS references. Transformation of results XML produces the actual HTML used.
   • JavaScript files. PT uses JavaScript (js) for results presentation behavior. This allows great freedom in customization. Standard PTd js files are proprietary, but can be replaced by developers. Interactions (API) like map navigation and integration with results windows are not documented, but could be made available. Better approach is to work with Seaconis developers.
   • XSLT files. XSLT (eXtensible Style sheet Language Transformations) is a language for transforming XML documents into other XML documents, or other formats such as HTML for web pages. PT uses to modify results XML streams or files into presentation specific filtered and organized HTML for pages and tables.
   • CSS files, Cascading Style Sheets is a language used to describe the presentation of a document written in HTML or XML. PT uses CSS to allow custom look and feel.
   • Controls – web controls that can be employed in custom presentation. Generally referenced in base HTML.
   • Image files, various formats. Used in styling in presentation.
7. Reference Documents - special folder where reference documents can be copied. This folder is dynamically read by PlanTest to populate one of the application menu headers.
8. User preferences – proprietary XML files. Managed by PTd, persisted in AppData\Local\Seaconis, users can create any number of working environment profiles.
   • Layout – Actipro Docking Windows layout file.
   • Toolbar positions – named .ptx files. Seaconis XML schema.
   • UI colour themes – named .ptx files. Seaconis XML schema.
   • UI behaviour (map navigation, ect) – named .ptx files. Seaconis XML schema.
   • Service sources
9. Rule Sets – XML files. Seaconis XML schema to record business rules used by analysis or UI.
10. External Results – XML files. Seaconis XML schema to record test results from external systems, to include in PT examination.
11. Third-party extensions – assemblies
12. Core – PT code modifications for clients. In most cases jurisdictional code is now external assemblies included only in site specific installations.
    • Data model – code. Jurisdictional data models are produced by Seaconis developers during adaptation projects.
      • SI Objects – code. The base data model.
      • Site data model is a layer on top, usually of a modified second tier SI Object.
    • ETL code – classes specific to reading and writing jurisdictional data formats and data models.
    • PTd UI – code.
      • Controls – classes MVVM architecture.
      • Menus – XAML and MVVM view models.
      • Toolbars and toolbar items – MVVM and XAML templates
      • Tools – Map tools follow ArcMap hooks.