(...) 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 (...)
(...) 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 (...)
(...) the Calendars table. Table description The Calendars table stores the calendar days. To modify the calendar, go to the “System settings” and in the “Global parameter s” tab select the “Working days calendar” option. Fig. 1. The configuration of the calendar in WEBCON BPS Designer Studio You can define the non-working (...)
(...) to pass information from the current form to one in another workflow is by using the Hyperlink action. Hyperlinks allow you to go through to the linked form, open it in the new tab, and pass a set of parameter s to the other workflow. The Hyperlink action (in the WEBCON BPS 8.x.x version) was described in the following articles: https://howto.webcon.com/process-start-from-hyperlinks-top-link-bar-ac (...)
(...) these elements is defined in the StartBpsCommandSet.ts file in the onExecute() section at the end of the file. @override public onExecute(event: IListViewCommandSetExecuteEventparameter s): void { switch (event.itemId) { case ’COMMAND_1′: // Start workflow // Generate Document Link const absolu (...)
(...) ubstitutions action The screenshot above shows the configuration window of the “Add a substitution” action. On the left there are sections related to the setting substitution parameter s, on the right there is the variable editor window. The “Add a substitution” panel can be divided into four sections: User selection – it allows you to indic (...)
(...) path’s ID. An example of a request address: http://wdr04/api/data/v2.0/db/1/elements?path=89083a10-b8f4-44f8-b500-df2cb417aa98 In the request BODY, provide the parameter s to initialize the workflow instance: All GUIDs can be found in WEBCON BPS Designer Studio. In response to this request, you will receive an ID, Instance number, and Status. (...)
(...) action Fig. 3. The configuration of “Hyperlink” action In the expression edition window select the “Start Element (…)” function and then the “parameter s mapping” option. Fig. 4. The configuration of “Hyperlink” action In the hyperlink edition window enter the necessary information about the workflow which will b (...)
(...) p; Configuration in WEBCON BPS Designer Studio To enable authentication in the Portal, you must activate the ADFS authentication provider in the system configuration. The following parameter s must be passed in the configuration: ADFS server metadata address Application identifier in ADFS, which is the address of WEBCON BPS Portal Provider address which is the address of the act (...)