ANSWERED

Format string value to currency?

Is it possible to format a string in **itemTemplates** to a currency format? etc `29529.7975` to `29 529,80`? Similar to `{{item.createdate | dateFormat : 'YYYY-MM-DD HH:mm'}}`

Feature request to support OR filtering

I am trying to get two different type of items visible into the same list, but I noticed that there is no OR filter in search filter criteria. I don't want to show the base query sentence to the end user.
ANSWERED

Feature request about custom html response colors

It would be nice to have user profile color picker for some responses. If user would have adjusted responses like info,warning,error,success to own wanted colors and those would have saved into the user account settings. I could use those to color my html responses with user wanted colors beside the default scheme of responses color. This could be one way to improve the visibility issue of color issues of users reports about selected text colors. Read user color scheme about these settings from user settings and use those in your responses. I would also want to be able to have a color picker with preview box to set certain color if user wants response to be shown in that color.
ANSWERED

Feature Request - Translate strings in 'Admin' pages

It would be nice if '`strings`' also are translated in the Administrator UI (configuration) etc `admin/configuration/workspaces` list of all workspaces results. For example `{{t "_my_string_value"}}` is displayed instead of the translated text '`String Value`'. **See attached image for example** ![Image](https://i.imgur.com/hGCxQg6.png)
ANSWERED

Feature Request - Protection against robot spam

We would like a feature to add protection against robot spam, like Captcha, in forms that are public.
ANSWERED

Feature Request - DropDown/formElemet empty row

When we are using formElemet with `type 'select'` and parameter `required: true'` the dropdown list automatically gets an empty/blank row. The blank row should be automatically hidden if the dropdown is set to requiered. **See attached image for example** ![img](https://i.postimg.cc/g0MXxYK6/img.png)
ANSWERED

Feature requests for the formElementsTable

I have a couple of feature requests. These are not critical, but something that came to mind while working on some forms. 1. Would it be possible to use the 'required' attribute to refer to another element in the formElementsTable? Like the example below: elements: [ { type: "select", width: "col-md-2", name: "protocol", required: true, options: [{ label: "TCP", value: "TCP" }, { label: "UDP", value: "UDP" },{ label: "ICMP", value: "ICMP" }] },{ type: "textField", pattern: "^[0-9]{1,4}$", width: "col-md-3", name: "port", required: { ifField: 'protocol', hasValue: 'ICMP' } }] In my understanding the name refers to the attribute of the object itself in the array, so this solution does not seem work between the elements on the tables. 2. Would it be possible to define a minimum or maxinum number of rows in the formElementsTable? With the 'add', 'remove' and 'copy' functions, it might come in handy to define the max number of rows that the user can add to the table. For example to define a maximum number of devices they car order or a minimum number of contact persons to add to an asset. Thanks in advance!
ANSWERED

Feature request - workspace source

We would need an option on some workspaces to add include and exclude datasources, so that we could define what fields would we output in the results of the api query. Currently we are only able to access to the query part, but we would need the ability to optionally define include and exclude sources. Below is an example of elastic code what I understand that currently we can only modify in onify workspace the query part and there is no way to escape out of that to add the part _source that would have ability to define includes and excludes... { "_source": { "includes": [ "obj1.*", "obj2.*" ], "excludes": [ "*.description" ] }, "query" : { "term" : { "user" : "kimchy" } } }
ANSWERED

Two feature request - workspace and form

1. We would like to be able to prevent browsing to a hidden workspace that is not configured as a browseable, this still needs to be usable via the form lookup... Currently if you have a hidden workspace and a form is not limited with roles, that form is usable to anyone via hidden workspace that has no roles set up. 2. Option to list workspaces in form configuration which workspace is allowed to access to this form. Currently we can only limit form usage in the pug with this code: block formContent if(form.queryparam.workspace != 'workspace_name') h2 Wrong workspace! else
ANSWERED

Several attributes in a column in listitem

We would like to be able to display values in a column in the listitem element in dashboard, based on several different attributes where it is shown if value exists, similar to this code "{item.attribute.email ? item.attribute.email : ''} {item.attribute.username ? ' - ' + item.attribute.username : ''}"