Welcome to the Onify Support Hub. You'll find comprehensive guides and documentation to help you start working with Onify (Platform for Digital Transformation) as quickly as possible, as well as support if you get stuck. Let's jump right in!
We are getting data from rest-API, then use transform to map data. If the data contains special characters the transform task in index fails. Data from rest-API: "title": "lorem ipsum \"text\"" Errorlog: Could not transform Error: Invalid object passed in, ':' or '}' expected.
Posted by Henrik Andersson 3 months ago
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** 
Posted by Patrick 3 months ago
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!
Posted by Eetu Tarkamo 4 months ago
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" } } }
Posted by Markus Kalske 4 months ago
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
Posted by Markus Kalske 4 months ago
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 : ''}"
Posted by Henrik Andersson 4 months ago
This is actually not a question. I tried to figure out how to prevent some attribute not to be used in elastic search in a certain workspace. This is how my colleague Eetu Tarkamo figured it out. I was in the correct path and all he had to change in my faulty codeline was "attribute.<propertyname>.keyword": "{{<wrong itemvalue>}}" to a correct value {{term}}... ```json { "bool": { "must_not": [{ "term": { "attribute.<propertyname>.keyword": "{{term}}" } } ], "must": { "query_string": { "query": "{{term}}", "default_operator": "AND", "fields": [ "key^6", "name^4", "_all" ] } }, "filter": { "bool": { "must": [{ "bool": { "should": [{ "term": { "type": "<your type item>" } }, { "term": { "type": "<your another type item>" } } ] } }, { "bool": { "should": [{ "term": { "owner": "{{<item>.<itemvalue>}}" } }, { "terms": { "attribute.<value>.keyword": "{{<item.propertyname>}}" } } ] } } ] } } } } ``` Now the actual question... :D If i want to select just some fields to be able to be used in the elastic search in a certain workspace, I just replace that "_all", with typing all those wanted field names that I want to be enabled in the workspace search?
Posted by Markus Kalske 5 months ago
I don't fiqure out howto put workspace query that would sort all items ie. type This kind of query works in the shortcuts, but I would like to have the workspace default search include the sort. https://<servername>/workspace/<workspacename>/search?term=<username>&sort=type,asc
Posted by Markus Kalske 5 months ago