Support for Non-Address Permit Creation with Location Modes

• What - Introduced a new Location Mode framework that allows permits to be created without requiring an address or occupancy when appropriate. Permit types can now use one of four location modes—Standard, Standalone, Pre-Development, or Special Event—with dynamic validation, location-specific fields, and user interface behavior while maintaining existing functionality for standard address-based permits.
• Why - This enhancement supports permit workflows for mobile businesses, pre-development projects, and temporary events where a permanent address or occupancy may not exist, while preserving compatibility with existing permit processes and preventing unsupported functionality from being used.
• How
  • Configure the permit type to use the appropriate Location Mode.
  • During permit creation, complete the required location information based on the selected mode:
    • Standard: Address/Occupancy
    • Standalone: Unit Name
    • Pre-Development: Parcel ID and GPS coordinates
    • Special Event: Event Name
  • Complete the remaining permit application as normal.
  • Standard permits continue to follow existing address-based workflows without changes.
• Use Case - A mobile food vendor can submit a permit using a unit name instead of an address, a contractor can create a permit before a site receives an official address using parcel information and GPS coordinates, and an event organizer can submit permits using an event name for temporary locations.

Dynamic Permit Interface Based on Location Mode

• What - Updated permit creation, permit details, and permit list pages to dynamically display location information, navigation options, and required fields based on the permit's configured location mode. Permit records now present location summaries appropriate to each permit type instead of assuming every permit is tied to an occupancy.
• Why - Presenting only relevant information simplifies permit creation, reduces confusion, and provides a consistent experience across both address-based and non-address-based permit workflows.
• How
  • Create or open a permit.
  • Review the dynamic Location section, which displays the appropriate information for the selected location mode.
  • Use the permit as normal with available tabs and navigation automatically adapting to supported functionality.
  • Standard permits continue to display occupancy, inspection, and invoice information where applicable.
• Use Case - Staff reviewing permits can immediately identify whether a permit references an address, a mobile unit, a parcel, or an event without navigating through unrelated occupancy information.

Pre-Development Occupancy Linking

• What - Added the ability to link Pre-Development permits to an occupancy after an address becomes available while preserving the original parcel and GPS information. Once linked, occupancy information becomes available without changing the permit's location mode.
• Why - This allows permits to begin before an address exists while supporting a seamless transition once the property is officially established, preserving historical location information throughout the permit lifecycle.
• How
  • Open a Pre-Development permit.
  • Select Link to Occupancy when an address becomes available.
  • Complete the occupancy selection process.
  • Review the updated permit, which displays both parcel information and the linked address.
  • Occupancy information becomes available after linking while inspections and invoices remain unavailable.
• Use Case - A construction project can begin permitting using parcel information and later associate the permit with its completed address without recreating the permit or losing original project location details.

Bug Fixes

Enforcement of Unsupported Features for Non-Standard Permits

• What - Added user interface and backend validation to prevent inspections, invoices, and unsupported linking actions from being created or accessed for non-standard permit types. Clear validation messages are displayed when restricted actions are attempted.
• Why - This prevents unsupported workflows, protects data integrity, and ensures users only interact with features available for the selected permit type.
• How
  • Open a non-standard permit.
  • Inspection and invoice navigation is automatically hidden.
  • Attempting restricted actions through unsupported methods is blocked by backend validation with an appropriate error message.
  • Standard permits continue to support inspections and invoices.
• Use Case - Users working with mobile business or special event permits are prevented from creating inspections or invoices that are not supported, ensuring consistent system behavior across all access methods.