User Voice

Hi,

I stumbled a while until I found the "autocomplete" field type in an item list element. I directly picked "choice field" under "choice columns" and didn't read the following entries because I knew that in normal "form field" with field type "choice field" one has to select "Autocomplete" under Settings > Behavior.

Maybe it would be more intuitive to align both configuration methods in the field type dropdown for the "choice fields" and "autocomplete" field types? I can't estimate this.

Kind Regards
Sébastien

Hi,

it would be nice if using a field type choice field with behavior autocomplete would not only set configured target fields in the columns of general tab in advanced configuration. When the choice field gets deleted and is empty the target field values remain instead of getting deleted too. To get them deletion one hase to create a form rule. This wouldn't be necessary any more if there would be this automatically or as an option in general tab kind of "Delete values of target fields if choice value is empty".

Kind Regards
Sébastien

Hi,

we just faced a situation in which we deployed a process to a new (customer) environment. The license did not include the "Advanced Analytics Framework". While testing everything we have run into a "License expired" error.
This was raised by the "Start /Stop performance indicator" action.

I didn't want to waste any more time and deactivated these action on the database level.
While this is an option, I think it would be better, if the action wouldn't be executed then throwing an error.

This is probably a partner only problem as it's unlikely that end customer will change their license for example from subscription to perpetual.

Best regards,
Daniel

Hi,

it would be nice having an option in the path parameter settings to tell the button if it shall be displayed on the left or the right of the button list.

Adding eg a class .path-button-container-right to the div containers of all right aligned buttons and the following css would do the whole trick:

.dynamic-form #pathPanel .path-button-container:not(.path-button-container-right) + .path-button-container-right {
margin-left: auto;
}

This addresses always the 1st button with option right after the last button with option left.

Kind Regards
Sébastien

Hi,

it would be nice having a global default button style template configuration for the button style of paths in the parameters tab. We would like to define some styles like "decline", "approve". This way all negative or positive buttons would always have the same look and everything could be controled through the global style template in system settings.

In the path parameter configuration a live preview would be nice too.

Moreover a CSS low-code editor would be nice to build those styles via drag & drop und autocompletion and colorpicker in all style configuration fields. Maybe with "..." like it is for form and business rules to open the rule editor.

Kind Regards
Sébastien

Hi,

it would be nice to have an option in system settings to set a global default text for chice fields with dropdown and active option "display empty element". This could be the default value instead of an empty display name.

Kind Regards
Sébastien

Hi,

adding a new picture form field requires us nearly each time to set a higher picture size limit in the advanced configuration. It would be amazing if we could set a global picture size limit ad default value in system settings.

Kind Regards
Sébastien

Hi,

we have several use cases (eg recurring drivers licence validity checks) with the need to force an image upload with a photo just shot through the camera. An upload from the photo gallery shall not be allowed because the photo must be recent and EXIF data could be manipulated easily in the photos option.

The image form field would need an option to force camera usage when a user uploads a photo without the default options of photo or document libraries. A second option to use front and/or rear camera would be nice too.
It’s similar too:
New field config combined with scan functionality of WebCon App

For web version the HTML input field could be structured like this eg:
<input type="file" accept="image/*" capture="environment" id="cameraOnlyInput">
Capture should be fixed to environment for rear camera. Front camera would ne capture to be set to “user”.

Example code snippets for native mobile apps:
iOS:
let imagePicker = UIImagePickerController()
imagePicker.sourceType = .camera
imagePicker.delegate = self
present(imagePicker, animated: true, completion: nil)

NSCameraUsageDescription needs to bee added to Info.plist

Android:
val cameraIntent = Intent(MediaStore.ACTION_IMAGE_CAPTURE)
startActivityForResult(cameraIntent, REQUEST_IMAGE_CAPTURE)

To force this the functionality is needed too to set a process only accessible for smartphone or tablet devices and not for PC. PC usage would only be acceptable with this feature request and if local image upload would be prevented and camera usage forced:
Enable using camera for no mobile devices

Kind Regards
Sébastien

Hi,

a function for expanding all child elements of an element in the tree of an application in Desiger Studio would be nice. Maybe via right click and context menu entry. This menu entry would be necessary for all tree elements containing child elements. Same for collapse all elements.

This would safe time for expanding the elements manually.

Kind Regards
Sébastien

While we’re on the subject of comments, it might be worth considering adding an additional field to the comment data structure (JSON)
that would store the version number of the document in which the comment was added.
This would make it easier to track and audit later.

Regards