Welcome to the Alloy Ideas Portal 👋 Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
When issuing a permit from an asset layer that isnt the gazetteer requires a network link to a gazetteer entry with the USRN.
Which works.
However, we have sections that are linked to multiple streets. and if they are network linked to those streets which all look valid.
All looks well, but on creating a permit, it populates the first entry, so if this is the wrong one, you have to manually enter the other one.
AND it is a legal requirement to permit on the right street, or you can get a Fixed Penalty Notice.
It would be nice to have a picker that shows the 2 valid entries, rather than 1,000’s of other streets unrelated to the section.
Hi thanks for the idea, this was originally raised in the community here so just linking for completeness: https://community.alloyapp.io/t/populating-usrn-on-permit-aplications/518
The picker includes all NSG streets in your system, then we default the selection for you to make data entry quicker. However, in the case where the asset/section is linked to more than one NSG Street, the ‘first’ parent NSG network is selected. This may or may not be the right one.
I don’t think we’d want to completely restrict the possible USRNs in the list as this may be limiting to other use cases, however, adding some toggle to filter to only the NSG Streets associated with the job would be useful in this case.
As well as that, one of the following may be required:
Do not default the USRN
Continue to auto-select the first but warn the user there is more than one parent network linked
In the meantime, these jobs could be flagged up to the permit manager using a custom attribute on the job
