WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question

search results

for break inheritance

Hi, In Webcon, it is possible to make modifications to the form at the step level. When the "break settings inheritance" option is activated, these modifications apply only to that specific step. For a more visual experience, it would be nice to highlight these steps in the flow, similar to how steps containing "on entry" or "on exit" actions are highlighted. Thanks, Raluca

Hi, This would be great. I would also add something: when in the Forms tab, if fields had been moved to a different position they should be highlighted somehow. I am not sure how this could be best done, if in the same Main form tab or a new tab, but I can see how this would help specifically when working with lots of Item lists on the same step. Regards, George

Applies to version: 2020.3.x and above; author: Jakub Okrzesik   The article is an update of the already existing article, it shows the configuration in version 2020.1.3. For the original see: https://howto.webcon.com/action-templates/.   Introduction Action templates is a feature that allows you to save a lot of time when implementing processes and reduces the p

Applies to version: 2020.1.x and above; author: Dawid Golonka   Introduction When designing processes for business applications, in addition to ensuring that the created solution works correctly when it comes to functionality, it is also worth paying attention to the visual side of the form. The form view should be intuitive and understandable to the end user. Each workflow crea

(...) y at the selected step (instead of first one where the form field will be visible), add the appropriate condition in the rule (it is recommended for facilitating and maintaining the configuration) or break inheritance of the form field configuration in the form settings on the selected step.   Fig. 4. Configuration of the default value set on the selected step by using IF rule   Fig. (...)

 PDF version 1. Application assumptions WEBCON BPS 2020 mobile application facilitates working with WEBCON BPS system from the level of mobile devices.     Basic assumptions of the application architecture: Dedicated application for mobile devices Android – support from version 4.2 iOS – support for the last two versions   Works in tw

(...) e process tree. This means that the order of the form fields in the group and columns on the item list configured in the process correspond to their location on the global form template.   To break inheritance on the main form, click the “Break settings inheritance” button in the Global form template tab and confirm “Yes” in the information window (Fig. 1).   Fig. 1. (...)

(...) ;s global form template. The compact global form template inherits settings from the main global form template. Logically, a compact step form inherits from its main form version.   If we break inheritance for a compact workflow form, it will become independent of the workflow's main form. This way, compact step forms will also become independent of the main form steps.  In this case, field vi (...)

Applies to version: 8.2.x, author: Marcin Wiktor   Item list buttons Apart from managing visibility or editability of individual item list columns in the field matrix, WEBCON BPS allows users to change availability of item list buttons, such as “Add”, “Delete”, etc.   Item list buttons Item list buttons can be configured globally for the whole w

Applies to version: 2023 R3 and above; author: Łukasz Maciaszkiewicz   Introduction With the WEBCON BPS mobile application, users gain the ability to access the WEBCON BPS platform from anywhere using their mobile devices. This article delves into the core assumptions regarding the architecture of the mobile application mentioned above.   Assumptions The fundamental ar

Hi Fabian, if you only need this in one step, you could simply break the inheritance. This will allow you to create a completely different layout. I personally hate this option, but there are these cases where you have to fall back to it. The reason why I hate this: You always have to remember that reapply all changes regarding field order / visibility. Something which is easily forgotten. Of c

Hi Robert, you can at least achieve this without "hacks" on step level. The available attachment actions are defined on the form layout. If you want to deactivate add, delete, edit on a specific step you can: 1) break the inheritance 2) click on the attachments element 3) uncheck the actions you want to prevent. Unfortunately this makes it harder to maintain. If you move the fields they

(...) step, define some rules there and break the settings to change the allowed actions. The screenshot shows the configuration of the item list in the form definition of a step. I for my part, hate to break inheritance. This requires documentation, so that I won't forget it, but I know that I won't read it anyway. :) Best regards, Daniel