search results

(...) I need your assistance with something. I am currently working on a Business Rule that should return a value using SQL. The Business Rule needs to be as universal as possible, and I want to pass two parameter s to the SQL query. So far, so good. The issue is that I want to pass the same form field as a parameter twice: once as a value and once as a "column name" (essentially as an object value that I ca (...)

(...) lue path or to the purple path in WF (2). The issue is that the business rule in the 'Start a Sub Workflow (SQL)' actions, which checks if someone has an AD user or not, isn't working when I pass parameter s like ##Vorname## [engl. Firstname] and ##Zuname## [engl. Surname] (which turns into {Vorname} & {Zuname}). The filter works with hardcoded names but fails with passed parameter s. Any ideas on w (...)

(...) ill be displayed.   Fig. 6. The Account dictionary   Fig. 7. The configuration of the "New deposit" button   The user's login in the only passed parameter .    Fig. 8. The configuration of the hyperlink used to start an instance   Transactions dictionary Using the “Transactions” dictionary you can change the (...)

(...) Then, in each of the sub-sections, you will put a table which, after correct configuration, will display your data (both tables look identical). At the start, create a table and set their basic style parameter s:   Fig. 10. HTML style parameter s   Border-(top, bottom, left, right)-color: the color of the border of our table Margin-(top, bottom): the size of the margins in pixels (...)

(...) ant - Maximum number of tasks per person   A good practice is to use constants in processes – they allow for wide parametrization and also protects you against the need to change the parameter value in all places where it is used. Next, configure the “Queue or assign” control step – below there is a business rule used to select the appropriate path:   Fi (...)

(...) h time.   Where can action templates be used? There is a scenario where we have a project that contains multiple stages that are supported by separate processes. During each stage, some parameter s of the process can change which may cause inconsistencies in the subsequent stages of work. To avoid them, you can create a process that contains the history of changes of the important project para (...)

(...) environment.   Fig. 5. The import of the process – Deployment mode   Enabling the global deployment mode The global deployment mode can be set in the global system parameter s (Fig. 6).   Fig. 6. Enabling the global deployment mode   To enable the global deployment mode: Click in the System setting -> Global parameter s -> E-mail notif (...)

(...) attachment status verification and move the instance to the appropriate step.   Fig. 6. The cyclical action configuration   In addition to the AdobeSign key, there are more parameter s that you should configure: Step ID – the ID system step in which the documents are waiting to be signed Success Path ID – the path leading out from the “Waiting for signatu (...)

(...) er of the preview window.   Example of use Moving from the report level to the instance displayed in the full window, the address bar will contain the full link along with the returnurl parameter :   Fig. 1. Instance in the full mode   Regardless of whether it is done from the instance preview window or the full window view, you get a “clean” link to the i (...)

(...) Username and Skribble API key Note: Using SDK plugins in WEBCON BPS may require a specific license depending on the version being used. It is a good practice to store the Skribble connection parameter s in global or application constants so that they may be easily used across multiple configurations, according to the example table below.   Name Example valu (...)

(...) ion of this action may look like this:   Fig. 5. The API setting in the action configuration   In the “DocuSign API settings” section, enter the DocuSign account parameter s that allow the use of APIs. This data is necessary for all SDK actions so you can enter them as constants in the process. In the “Attachment section”, define  the method of attac (...)

(...) ep is presented below:   Fig. 3. The form view on the start step   The fields with the register person and date are automatically filled in. The selection of the other three parameter s seen on the form: the person to be added, the accepting person, and the group that will be modified, is done by using three “Person or group” form fields. To limit the possible selection (...)

(...) dquo;Data sources” section and some places in the “System settings” section. In the “System settings” section you can get information about settings in the “Global parameter s” tab what is not possible by using the mouse. Below there is a screenshots presenting the history of the setting for language translations.   Fig. 9. The history of changes fo (...)

(...) f storing information about the rule ID in the WFSteps table   Below there is a description several other results which can be obtained in queries of this view: TableName: WFBusinessRuleparameter s, OBjectIDColumnName: BRP_ID, ColumnName: BRP_RuleID   Entries referring to the WFBusinessRuleparameter s table contain parameter s that can be defined when creating the business rules (...)

(...) rivileges can be scaled and applied globally, per application, per process and even per specific form type.   Types of privileges     Global privileges The global parameter s allow you to grant selected users the global administration or read-only privileges on all existing processes. To do this, go to the “System settings” tab and then, in the “Global (...)

(...) at– setting up a form rule on the path. This article describes the use of this functionality.   Description the functionality During configuration the workflow path, in the “parameter s” tab there is an “Additional path validation form rule” field.   Fig.1. The “parameter s” tab   This field allows you to set an additional vali (...)

(...) tor’s name placed on the “Contractors with arrears” item list to the “Contractor” form field in the “Outgoing correspondence” subworkflow. In the DET_WFCONID parameter , provide the item list ID from the data originates and the DET_WFDID refers to the given instance ID. After going through the path and executing the action, the subworkflows will be created &ndash (...)

(...) base can be maintained on relatively slow and cheaper discs.   Construction of an Attachments database An external attachments database consists of two tables – the “Globalparameter s” table contains a database configuration, while the “WFAttachmentFiles” stores the attachment files.   Fig. 1. Construction of external attachments database   (...)

(...) web/icons.   The link address that was used in this solution refers to the start address of the workflow defined in the WEBCON BPS environment.   In the link, the additional parameter s are also passed such as: [$ Title] – to the AttText1 field in our form we pass the value of the Title field [$ ID] – to the AttText4 field of the form we pass the ID value of the (...)

(...)   There are three methods of selecting the Word file: From url From attachment From document template process     In the Output tab the output file saving parameter s are set. Selecting the “Show on the screen” option allows to display the preview of the generated file in the browser window. If you select the “Save as an attachment” opt (...)