User Voice

Hello,

We recently started to take better care of translating our applications in our native language as well as English.
This way our clients will have a more professional experience.
Even if we have everything translated, the preview that we see is in the language used for naming the steps/paths initially.
It would be a nice touch if the language of the preview would be the same as the language selected in the users settings.
Obviously, if a path/step has missing translations, the default value would be used.

Regards

Hello,

Right now there are Next step, and Previous step buttons on the Step Edit window, but if we need to edit two steps, which are X steps apart, then we have to:
* Click X times - and every have some delay - loading the data.
* Close step editor, and use list on the workflow, or the diagram to select step which we want to edit.

I've got an idea that in the Step Edit window, we could add list of steps (list, tree, tabs) to choose from.


An example in attachments :)

Hello,
I'm looking for a feature to be able to display images inside drop-down, or pop-up choice field.
Either form Picture field, or from Single line of text in Picture mode.

Use case:

I'm working on a process, where sales department should specify which base product should be used as a starting point to create a new one.
There is a long list of those base products, and remembering how each one looks just by number/name is not possible.
Displaying the base product during selection could help with selecting right base, and speed up further processes.

I've been showing the image after selecting value from choice field, but in the end it's not the same (had similar need in 2 processes so far).

The only reason for naming /displaying the automation at all is the documentation.

Would be nice, if the automation uses the same name as the parent object, renaming the parent object would also update the automation. Ok, this could only happen for paths, but I was lazy enough to forget about it. :)

I've been thinking about it too lately.
It had a purpose to name Actions under single path, but if there is no way to have more automations on path than 1, then I don't see a point in naming them at all.

Default name like that would be good enough :)

Hi,
Maybe it would be a good idea for a new automation to be created by default to receive the name of the element for which it was created.
This would help keep the system tidy, reduce the workload for each time you assign a name,.
And for people who prefer other names, nothing will change because you will have to enter your name anyway.

Regards

Hi,

it would really be great, if we could trigger the documentation generation for a whole application.
It doesn't have to be a single document. It would be fine if this would just create a zip package. In this zip packages there would be the default documents for all processes. This would include the related processes too.

Now I'm going back to generating the documentation for ten processes again...

Best regards,
Daniel

Hi,
It would be nice if we also had fields of the time type.
Some clients need to record, for example, the time of arrival and the time of departure, and this is not possible through standard fields.

Thanks,
Raluca

Hello,

While designing form I'm often getting questions about possibility to set some additional description to the field.
I'm usually talking about the tooltip, but it requires the action of end user - he have to willingly hover on the (ℹ️) icon, to display the message, and there is no guarantee, that he will see it.

Right now it ends with creating HTML field with some description near the field, which in my opinion unnecessary clutters the form.

My idea is that we could have some configurable checkbox - 'Auto expand tooltip on field edit', and maybe some duration setting so it would disappear after x seconds.

True story. The introduction of the foreach operator was an amazing and long waited feature. It solved many performance issues.

P.s. Can't wait for the case operator.