Portal Planning v5.7 - Release Notes Released April 2025
AI Validator Enhancements Planning Compliances Enhancements for Irish Customers
Validator – Exception keyword rule
The AI Validator is now able to allow exceptions to rules depending on an applications proposal.
In the Configuration Portal (Configure Service >> Planning >> Validator >> Rules >> "AI Validator Rules Configuration") the user can now find a new item in each rule skeleton, which is a multi-selector. When a keyword/phrase is chosen within this multi-selector, even if all other rule requirements are met, the rule will not be triggered if the scope of the work in the proposal includes what the chosen keyword/phrase describes.
For example, for a Householder (Application type 1) application, existing elevations may be set to required for all circumstances except when the scope of the work includes a new building.
This is how the rule would appear in this specific example:
It is important to note that this functionality is only available to clients using the new "merge configuration".
To enable the "merge configuration", you must contact the Product Owner.
Validator - Review and send on demand emails
AI Validator has functionality to send automatic emails once the tool has analysed the application and applied the rules.
There is now the option to hold the email in the tool, allowing the emails to be edited and sent by an officer within the Validator.
To enable this functionality, go to the Configuration Portal, select 'configure service' >> Planning >> Validator >> Reporting >> Email Configuration, and enable the checkbox called 'Send email manually in Validator Portal'.
Once this configuration is enabled, all new applications will have a button within the application details, which will lead to a modal where the email can be edited, saved, and sent.
The modal view will be loaded with a default subject and body with the output analysis done by the Validator.
Below the title of the modal, there are two buttons to set the template as valid or invalid with their merge fields filled in. These buttons will automatically modify the subject and the body. Both the subject and the body of the email can be modified.
In the second highlighted section, fill in the relevant email accounts, separated by commas. At the bottom of the modal, there are three buttons:
- Save: to save all progress, so any edits are kept and the email can be reviewed and sent later.
- Send: to send the modified email (at least one email address must be in the first text field called 'Send Email to').
- Cancel: to exit the modal
Planning Compliances – Submit application
We refactored the application submission to create a planning compliance application based on an existing planning application.
The new submit application will display a wizard with the new following steps:
- Type
- Parent application
- Conditions
- Details
- Documents
- Summary
Planning Compliances – Submit application – Type
Display a dropdown list to select the relevant application type, for now will be just “Compliance”, for this step needs to configure the application type (Click here)
Planning Compliances – Submit application – Parent application
It will display an autocomplete input text “Application reference” to let the user introduce the planning reference of the parent application.
The system will check if exists any application with that reference linked to the logged user (checking the agent email of the planning applications or the applicant email if there is no agent) and display the possible references while the user is typing.
If an application reference is selected, the following details of the application will be presented:
Including a link “View full details” which open the planning application details screen in a new browser tab.
For this step, need to be configured a form (Click here).
Planning Compliances – Submit application – Conditions
It will be listed all the conditions linked to the parent application in a table letting to the user select one condition where the compliance will be applied.
Only not complied conditions are shown; no conditions are listed where the PAPRES. CB_COMPLDIND (Complied Indicator on Conditions screen) and/or the PAPRES.COMPLDT (Complied Date on Conditions screen) are populated to ensure only conditions awaiting compliance are displayed.
For this step, need to be configured a table config (Click here).
Planning Compliances – Submit application – Details
It will be displayed a form based on the customer configuration depending on the application type selected.
Default form for Compliances with a text area with a label:
Please describe how the Condition in question has been complied with:
For this step, need to be configured a dynamic form (Click here).
Planning Compliances – Submit application – Documents
It will be displayed an uploader with the ability to select the document type for each document and a note.
Planning Compliances – Submit application – Summary
It will be displayed an uploader with the ability to select the document type for each document and a note.
Planning Compliances – My applications
The previous “My applications” screen was showing the temporal planning applications from the web submissions, as the old web submissions are no longer that screen will be removed, and will display all the applications of the user based on their email displaying the following fields in a table: Web reference, Case reference, Location, Type, Status, Proposal, Registered date and Details (“Condition: XXXXX”)
Planning Compliances – Application details
A new section will be added to the existing application details called “Related applications” (this will appear only for IE customers and needs the following config: Click here).
It will display a table with the related planning applications. Displaying: Reference, Location, Proposal, Registered date.
Planning Compliances – Delete draft applications
Now a new button will be displayed on the “My applications” menu, providing the ability to delete applications that are in draft status.
Support tickets:
#18752054701 (From bug #101646)
Bugs related:
Configurations:
- Form name: Submit Parent App; To get the form, go to Planning dev – Demo config sheet.
- Table name: Submit Conditions; To get the table configuration, go to Planning dev – Demo config sheet.
- Dynamic form: PLANNING_SUBMISSION_FORM_COMPL, name: Compliances; To get the form, go to Planning dev – Demo config sheet.
- SHOW_RELATED_APPLICATIONS: true (just for IE customers).
- For Irish Customers: It should exist and Application Type (cmstdcde where stdtyp = 143) with stdcdedes = “Compliance” and scode = ‘COMPL”