search results

Hi, today, saving processes, apps, and artifacts in the Studio lacks a structured way to document what changed and why. This creates several limitations: - Low transparency: Changes are saved without clear intent or context. - Weak traceability: No consistent link between a change and a requirement, bug, or external ticket (e.g., Jira). - Inconsistent documentation: Teams rely on manual co

When migrating applications from SharePoint to WEBCON, the users are used to search documents only. This isn't a problem at all with WEBCON as long an element only has one document attached. If there are more attachments, the current full text search returns the element with all its documents even if only one document matches the search term. For Records Management processes, where we can have s

We need a dedicated Checkbox Field type that functions exactly like a Choice Field but provides a native checkbox-list UI. Currently, business users designing in Designer Desk intuitively use "Choice Lists" for checkboxes, 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 D