Filip Miśko

Hi. Are you sure? https://kb.webcon.pl/kroki-systemowe-jak-dzialaja/ There we've got one path from the start step.

Have you checked the layout inheritance on those specific steps yet? I’d double-check if they are inheriting from the global form or if there's a "Custom layout" override active for the steps where the old instances are stuck. If inheritance looks fine, try to "kick" that field or group in the attr

Unfortunately, I haven't found a sensible way to edit those fields directly once the table has been generated. Whenever I need to make a changes, like adding a new column or renaming things I usually find it’s much faster to just delete the old table and insert a new one with the correct settings

Hi Arek, You can handle conditional logic in .docx templates using these two methods: Business Rules with SQL logic: This is the easiest way to display conditional phrases or paragraphs. Create a Business Rule (SQL type) that returns either the desired text or an empty string ('') based on you

If it didn't work, the most common couse is invisible leftover tags. Here is what you should try: Clear the entire area (watch out for invisible elements). Sometimes, when you delete a previously inserted Webcon element, invisible formatting or partial tags remain "underneath" and break the docum

Hi Phil, To display the signature instead of the raw code, the field must be mapped to a Picture Content Control in Word. Here is how it works for me: 1. Enable the Developer tab in Word (if it's hidden) Go to File -> Options -> Customize Ribbon. In the list of Main Tabs on the right side,

Try moving the logic from the field's 'On Change' event directly to the Item List configuration. Instead of triggering the rule directly on the column, use the 'For each row' operator within the Item List rules. You should place your IF statement (the one responsible for setting the cell backgrou

Hi, I'd like to suggest a functionality improvement for Item Lists. When configuring a standard Choice Field, in the "Picker" tab, enabling "Allow adding values not in data source" unlocks the option "Allow editing target fields when new value is added". This allows us to open a pop-up form to fi

You need to use wfelems.WFD_ID because WFD_ID alone isn’t recognized inside the subquery. At that level, SQL doesn’t know which table the column belongs to. By adding the alias wfelems (which i think refers to the V_WFElements view in the main query), SQL can correctly link both tables. So the