Alloy Ideas Portal

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.

ADD A NEW IDEA

All ideas

Showing 290 of 290

Increase the API page return limit

Currently any data from a query will be erroring after page 100 as the API has a limit of 100 pages returned from the /api/aqs/query and /api/aqs/join endpoints. This is not practical for returns that run into well over 100 pages, which is normal ...
Michael Daw about 2 years ago in Alloy Web 2 ⛔Will not do

Items Metadata - Do Not Display Alloybot Edits

We’ve added the Items Metadata interface to most of our designs so we can have a better understanding of who in our team is editing the data, where issues are occuring and then be able to supervise/check data and offer training & support where...
Guest about 2 years ago in Alloy Web 1 ⛔Will not do

Display More Information on Forms

It would be good to add tooltips for attributes on the mobile software (and web to be honest), so that a user can hover over an item and see more detail as to what is required for that attribute.
James Gladwin about 2 years ago in Alloy Mobile 3 ⛔Will not do

Hide activities card

The way we are setting up Alloy means that the user won't need to be able to create anything via the activities card. It would be good if we could do one of the followinf: Hide the activities card Hide the create buttons on the activities card (pr...
James Gladwin about 2 years ago in Alloy Web 0 ⛔Will not do

Handling of special characters in AQS queries

We were setting up different styles for a mapping layer based on one of the fields on a design. It wouldn't let us pull out records that had a > or a < in the field. I am assuming the same applies to + - and =. To get around it, those symbol...
James Gladwin about 2 years ago in Alloy Web 0 ⛔Will not do

long press on map start "context menu" e.g. create asset here etc...

Challenge / Problem: HMW (How might we ) make it quicker to set geometry on asset creation Solution idea: long click on map should start "context menu" e.g. create asset here (Idea) User story: As a field operative and mobile user, I want to quick...
Sean McIntosh about 4 years ago in Alloy Mobile 0 ⛔Will not do

Allow Pathcasting for Join Paths

User Story As a Data Explorer User, I need to be able to path cast on Join Paths, so that the count for each attribute selected in the data explorer shows correctly. Currently if I select the title of two different designs that have the same join ...
Robert Langton about 2 years ago in Alloy Web 0 ⛔Will not do

Virtual field attribute

to be able to have a attribute which would automatically populate based on another attribute , especially based on a aqs query. e.g. if the geometry is within the township layer. to pull off the name of the township and populate it. This will save...
Guest about 2 years ago in Alloy Web 0 ⛔Will not do

TEXT CHANGE: WORK ITEMS MODULE - 'VALUE' TO 'QUANTITY'

We noticed a slightly confusing terminology in the work items form (please see attached screen shot). There is are a couple of columns with headers called 'estimated value' and 'actual value'. Could these possibly be changed to read 'estimat...
Tom H about 2 years ago in Alloy Web 1 ⛔Will not do

Allow WMS services as a Layer Style

Currently styles must use WFS data and base maps can only use WMS/WMTS. We use a lot of public flood extent data, served in either WFS or WMS and in some cases it is only available in WMS. Adding this as a WMS base map does not work as this is sup...
Guest about 2 years ago in Alloy Web 0 ⛔Will not do