search results

(...) ate one. There, you can store relevant information about employees, as well as their XP or badges that they can later boast about. In their profile, we added an HTML field where, using a few business rule s, we easily displayed in a somewhat non-standard WEBCON manner, some interesting details about the employee. This would have been substantially more challenging without the new perform (...)

(...) be uploaded. As there are other file extensions allowed in further processes, we can not only limit the extensions globally. To enforce this requirement, we first configured a validation rule , which basically did the trick. However, from a user experience perspective, it would be great if the open file dialogue would only show pdf's: How is it done: Add a Html-Field to the (...)

(...) nd maximum values.   It is time to share a little secret: while the company typically applies a 10-percent margin to each project by default, there are cases where it can deviate from this rule . Now that the secret is revealed, it seems reasonable to include the margin in the configured Widget. To do that, select the Additional coloring conditions checkbox. This functionality allows you to (...)

(...) according to the application to which they belong. However, please note that the list can also contain elements that do not belong to any specific application, such as global automations and business rule s. These elements are grouped in a separate node and are visible only to system administrators. You can freely modify this default grouping method using the Filter editor… option in the context (...)

(...) a field value is unique per form type/business entity/step(s)? I for my part now, did implement this dozens of times Finally, I realized, that I should streamline this approach and create a business rule for this. Even if it's easy to create the check, the business rule will force you to think about each parameter   You can read up on the business rule and the parameters: here (...)

(...) recommended to integrate this image text using placeholders. This maintains the readability and maintainability of the document. In my example for "Go to Element", I used a GLOBAL BUSINESS rule : If you want to learn more about using HTML to give your emails a more personal touch, visit the external Knowledge Base article by Razvan Ogrezeanu dated April 15, 2024: [EXTERNAL] REV (...)

External content by Daniel Krüger; July 06, 2024 ;  The original post has appeared on daniels-notes.de     WEBCON BPS 2024 introduced different kind of form templates: While this is great for WEBCON BPS 2024 users. You can already achieve something similar with a little HTML field in previous version. You could even make it dynamic. If one tab needs a lot of

(...) h Business administrator privileges. In addition to detailing the specifics of the aforementioned mode, the article addresses the process of granting Business Administrator privileges and configuring rule s that include the Is admin mode active? variable.   Who is the Business administrator? In simplest terms, the Business administrator in the WEBCON BPS platform is the individual with th (...)

(...) ware that this change will have consequences. This global setting will result in collecting a large number of entries, making it more difficult to find relevant information.   Modifying rule s in the Nlog section The configuration above specifies what information is saved and at what level, while the Nlog library determines how this information is recorded. It collects entries, proce (...)

(...) y allow certain steps in between the range. You can then increase/decrease the value by using the arrow up/down keys. This can be achieved by the following steps: Create a global Form rule , switch the Edit mode to "JavaScript mode" and add the following JavaScript window.nxWebcon = window.nxWebcon || {}; nxWebcon.integerRange = nxWebcon.integerRange || {}; nxWebc (...)

(...) ittle solution for this question.  While creating the solution, a whole bunch of question arose how the "support" could be defined. In the end I settled with an explanatory business rule which returns the process supervisor, application supervisor or the support team as a fallback if none of the others are defined. You can read up on it here:   This is probably (...)

(...) to the list, set them as default value : Ordinal number, and change the configuration as in the attached screenshots. ID: T_ID:     Next, we create 2 JavaScript form rule s FRJ_Moveable_List_ID_SET   FRJ_Moveable_List_Delete: We add in the configuration of the change item list: - Deselect showing system ID - We set the FRJ (...)

(...) style parameter that we’d like to share. We’re happy with the design, and we hope some of you might find it useful as well. The CONTROL STYLE parameters are as follows [tip: use a FORM rule with parameter - see attached image]: margin-bottom: 30px; padding-bottom: 8px; outline-offset: 5px; outline: 1px #C0C0C0 solid; border-radius: 1rem;   Here’s a brief description of (...)

(...) d. Additionally, the interface allows for navigation between document pages, providing flexibility and control over the entire signing process. To configure this solution, three essential business rule s are required: Attachment Retrieval rule : This rule gathers the names, IDs, and content of the attached documents.     CODE:     2. Signatory Id (...)

(...) thentication provider and, after the user has logged in, displays the corresponding status. JavaScript – in JavaScript mode, the control for the form field is not displayed. Instead, all Form rule s (and JavaScript) work, including the GetToke rule , which allows you to programmatically retrieve the access token issued during user authentication. In this case, the authentication may take place & (...)

(...) ther options in the system, specifically the 3 options directly below it in the configuration. Access authorization effectively overwrites these settings: Index in SOLR regardless of visibility rule s – treated as “Disabled” – fields requiring authorization are not indexed. Always show in instance history – treated as “Disabled” – fields requiring (...)

(...) Calculating timer start dates A wide range of configuration options allows you to define timers whose execution and repetition will correlate exactly with the type of action and related tasks. The rule s for calculating timer start dates are described below, with examples of configurations and their results. Note: the examples presented in this article are for the calendar year 2024 (unless expli (...)

(...) ll use a character which would cause an error, when the document should be uploaded to SharePoint. You can find an overview of the unsupported characters and an example implementation of the business rule in this post.  

(...) e instead of single solution license Create new custom themes Verify updated item list actions Type error when executing a path Instance start buttons Empty report tiles REST and business rule s   Updating to BPS 2023 Calculated columns for Choose fields New database field Breaking change due to one’s own laziness Checks before upgrading to BPS 2023 (...)

(...) tion on the local disk.     Note: Creating a file with a global automation definition will not be possible if it contains references to another Global automation, Global business rule s, Global constants, Data sources, or SDK plugins. In this case, an appropriate message is displayed and the configuration of the exported automation must be modified. If the automation definition (...)