search results

(...) avoid inconsistent naming such as “Cancel”, “Abort”, “Close process” or “Stop workflow” being used differently across applications. A central path name and color configuration would support better UX , clearer process design, and easier governance in larger WEBCON environments. Kind regards Sébastien

(...) only to realize later that they lack central data management. This forces us to either explain technical trade-offs or implement custom SDK solutions to get both: a central Dictionary and a checkbox UX . I have documented this recurring architectural challenge and our current SDK workaround here: https://www.linkedin.com/feed/update/urn:li:activity:7492527653489512448/ A dedicated Checkbox Fie (...)

(...) the upload to be completed without selecting a category. A validation on a workflow path could of course check afterwards whether attachments without a category exist, but this is not ideal from a UX perspective. The user may upload several files, continue working on the form, and only discover later when trying to move the workflow forward that one or more attachments have no category. The be (...)

(...) ew”. The configured URL opens in a modal dialog. User creates/saves the new object. The modal is closed and the user continues working on the original form. This would significantly improve the UX for small aUX iliary forms and dictionary maintenance, where opening another browser tab interrupts the workflow. Ideally, an additional option to refresh the Choice field data source after closing (...)