Invoicing for Requested Inspections in the Portals

• What - Inspection types can now be configured with instructions, attachment requirements, associated line items, and payment requirements for inspection requests submitted through the Business Portal and Community Connect. When applicable, an invoice is created and linked to the inspection request, allowing payment to be collected using the existing portal payment workflow.
• Why - This enhancement provides greater flexibility when accepting inspection requests through the portals by allowing important instructions, supporting documentation, and applicable fees to be incorporated into the request process. It also creates a consistent invoicing and payment experience between permit and inspection requests.
• How
  • Navigate to Admin → Inspections → Inspection Types and select an inspection type that is enabled for portal requests.
  • Open the User Portals tab.
  • Use Instructions to provide information applicants should see when requesting the inspection.
  • Enable Attachments to allow applicants to upload files with their request.
  • Enable Attachments Required when at least one attachment must be provided before the request can be submitted.
  • When online payments are available, enable Payment Required at Time of Application and use Associate Line Items to configure applicable fees.
  • Save the inspection type configuration. The same configuration applies to requests submitted through both the Business Portal and Community Connect.
  • When a configured fee is greater than $0, an invoice is created and linked to the inspection request. If payment is required, the applicant is directed through the existing payment process.
  • If a configured fee calculates to $0, the applicant can continue without a payment prompt or blocking invoice.
  • If payment fails or the applicant leaves the payment process, the inspection request and unpaid invoice remain available so payment can be completed later.
  • Note: The payment configuration options are only available when the existing online-payment condition is met.
  • Note: This enhancement is controlled by a feature flag and does not apply fees, invoices, or attachment requirements retroactively to previously submitted or pending requests.
• Use Case - An inspection type can be configured to display preparation instructions, require an applicant to upload supporting documentation, and collect an associated inspection fee. When an applicant selects that inspection type in the Business Portal or Community Connect, they see the configured instructions, provide the required attachment, and, when the fee is greater than $0 and payment is required, complete payment as part of the request process.

Permit List Upgraded with Saved Views System (Feature Enhancement) Service Provider 

• What – The Permit List has been migrated to the new Saved Views system, bringing it in line with the same experience available in other modules. Users can now create, configure, and manage personalized views with full control over filters, criteria, columns, column ordering, sorting, pagination, and visibility settings.
• Why – This update ensures a consistent and modern experience across modules, making it easier for users to work efficiently without having to reconfigure their list settings each session.
• How
  • The Permit List now supports the full Saved Views experience, similar to what is available in other list-based modules.
  • Navigate to the Permit List within the Service Provider portal.
  • Use the Saved Views dropdown to access Favorite, Predefined, Custom, and Shared with Me views.
  • Create a new Saved View by configuring your preferred filters, criteria, columns, column ordering, and sort settings.
  • Set visibility for each view: Only Me, Everyone, or Selected Users.
  • Optionally enable Allow other users to apply changes to this view when sharing a view.
  • Set your preferred default pagination to 20, 50, or 100 records per page.
  • Save and name the view for quick access in future sessions.
  • When a Saved View is selected, its configured filters, columns, sorting, and pagination are applied to the Permit List.
• Use Case – A user who regularly filters permits by a specific status and set of columns can save that configuration as a personal view and return to it instantly in future sessions. A supervisor can create a shared view with standardized filters and column settings, making it available to other users for consistent permit review. A user managing high permit volumes can set a default pagination of 100 records per page within their Saved View, reducing the need to adjust settings manually each session.

Invoicing Support for Addressless Permits (New Enhancement)

• What – Users can now create and manage invoices for permits that do not have a physical address, including standalone, pre-development, and special event permit types. This support is available across both the Business Portal and staff interfaces.
• Why – Some permit types are initiated without a linked address, and the inability to generate invoices for these permits created gaps in the billing workflow. This update ensures all eligible permit types can move through the invoicing process regardless of address status.
• How
  • This feature applies to three addressless permit types: standalone, pre-development, and special event permits.
  • Invoices can be automatically generated or manually created for addressless permits.
  • Staff and applicants can use the Create Invoice from Permit workflow for these permit types.
  • Address linkage can be added or updated on a permit without disrupting existing invoice associations.
  • Anchor fields may be editable or locked depending on the state of the associated invoice.
  • Permits can be re-enabled from the permit side when applicable workflow conditions are met.
  • This feature is available to both Business Portal users and staff.
• Use Case – Staff can generate an invoice for a special event permit submitted without a site address, while an applicant submitting a pre-development permit through the Business Portal can receive and pay an invoice without first associating a property address. Staff can also link an address to an existing addressless permit later in the workflow without losing or disrupting previously created invoice records.