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!
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 3 days 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 6 days 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 6 days 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 6 days 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 about a month 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 about a month ago
Can we find a keyword list that are reserved into onify own usage, that we can avoid using those in our own usage that might have some unwanted behaviour if used without a knowledge that it might have some built in behaviour.
Posted by Markus Kalske about a month ago
We had an attribute sub property named as fag2_iamname, for some reason we got this error message... {"statusCode":400,"error":{"message":"[illegal_argument_exception] Limit of total fields [1000] in index [onify-hel-item] has been exceeded"}} After long investigations I found out that when that propertyname changed fagb_iamname it went ok without an error message. is there a bug in onify indexing or should we avoid using numbers in propertynames?
Posted by Markus Kalske about a month ago
We are using audit export API calls to collect action event data for statistical purposes. At this moment, this data contains information like title of "Submit form", userid, datetime etc. Could it be possible to add some custom categorization/classification "tags" to forms that we could use to create better statistics? For example: January 2020 Device management <- category - SCCM and Reporting Services 1487 pcs - SCCM Reports 851 pcs - Reinstall SCCM Client 130 pcs Orders <- category - order-a-laptop 401 pcs - Device-order-confirmation 66 pcs and so on.
Posted by Ari V 4 months ago
I didn't find where to set up session / login timeout, ie. kick out the user session after 12 hours. Currently I can have over a week or so session hanging with the onify and it would be better to be able to set cookie sessions to timeout after certain set timelimit. I think this should be adjustable setting somewhere in the onify GUI, but I can manage if it is some setting in other place also.
Posted by Markus Kalske 6 months ago
Currently the template format doesn't allow me to index items without "" surrounding the json value, I would like to be able to index items with integer values dropping those "" away, so that elastic search could be used more efficiently when doing searches > or < as with strings it only works with the first character :)
Posted by Markus Kalske 6 months ago
A customer requested a feature where they could reuse the filled form to make a second order with mostly similar values. Is it possible to define a default value to the lookup fields that search indexed items / options? The example element below: ``` +formElement[{ type: 'itemSelect', width: "col-md-3", name: 'faculty', label: t('form.vmorder.faculty_label'), required: 'true', lookup: { type: "item", workspace: "lookup", query: "filter=tag:laiterekisteri&term={searchstring}", sort: "name,asc", result: { value: "{item.key}", label: "{item.name}, {item.key}" } } } ```
Posted by Eetu Tarkamo 7 months ago