Community

Feature request to simplify css code writing, it would be nice to have support in the resource editor to be able to use var() function variables.

Is it possible to format a string in itemTemplates to a currency format? etc 29529.7975 to 29 529,80?

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.

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.

It would be nice if 'strings' also are translated in the Administrator UI (configuration) etc admin/configuration/workspaces list of all workspaces results.

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

When we are using formElemet with type 'select' and parameter required: true' the dropdown list automatically gets an empty/blank row.

I have a couple of feature requests. These are not critical, but something that came to mind while working on some forms.

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...

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.