search results

(...) not recommended for production environments. In the production installations, a change of default settings is recommended to  minimalize the Portal response time to the first HTTP request after REST arting its process. When applying default settings, the response time to the first request may vary from several to several dozen seconds. Note! In the environments in which the WEBCON BPS applicat (...)

(...) Remove a substitution Select field storing Substitution ID Exchange Event Save event ID to field Exchange Task Save task ID to field REST and SOAP invocation Save results to fields chosen from a list Change value of a single field Choose a form field to set Change value of multiple fields Ta (...)

(...) n   Fig. 2. The Gantt chart presenting employees assigned to a given line   The final appearance of the application with a list of downtimes (date and time of stopping and REST arting the production) and the Gantt chart is presented below.   FIg. 3. The Downtimes item list   Application workflows The Production Line Workflow is used to supervise (...)

(...) eriodic synchronisation and the risk that the data in the table may be out of date.     4. WEBCON Services provided by WEBCON WEBCON holds a standard WEB Service based on REST technology WEBCON may deliver a dedicated service in SOAP, REST technology. Such dedicated service requires an additional study. WEBCON does not provide web services on servers other than   (...)

(...) the "Editability and requiredness" tab.The rule below returns TRUE when the total order amount exceeds the limit order amount.    Fig. 10. Configuration of requiredness REST riction rule   Then, in the field in which a user must provide a reason – select the “Value change will cause default values to be refreshed” option on the General tab. (...)

(...) ds to be set up as a choice field returning the following data (IDs of respective options are important here):   Figure 3. Choice field configuration     The Autenti REST API documentation states that once a  GUID is returned by the system, the document was uploaded properly into the company’s internal database. Therefore, the user is blocked from progressi (...)

(...) database integrity and for creating backups. The database administrator should independently take care of full, differential backups, and the log, so that in emergency situations it is possible to REST ore the database, regardless of the time of failure. More information on backup is available at: https://docs.microsoft.com/en-us/sql/t-sql/statements/backup-transact-sql?view=sql-server-ver16 (...)

(...) format is used for some complex items, such as choice fields, person fields, form types. If the field you have selected is stored in that format, you can choose which part of the name is of your inteREST in the context of the rule being created. To open a context menu with options to choose from, use the Ctrl + Space key combination when the field selection is active, i.e. it is in a black border (or (...)

(...) vice separately and one common one for all Portal frontends). The service configuration is reloaded and the caches are refreshed after hitting the “Save” button, so you do not have to REST art the service manually, nor reset the application pool in the Portal. You only need to wait for the conclusion of those operations – this can take a few minutes.      (...)

(...) ules, depending on the user’s needs. When working with form rules, there may be a situation where execution of one function or subrule interrupts execution of the entire rule. Consequently, the REST of the rule is not executed. This article provides a detailed description of the reasons for this behavior and a proposal for creating rules so that they work as intended by their author.   (...)

(...) ction will download data from OneDrive, save it to the BPS database, and then delete the files from the indicated location in the service. Additionally, the successful action will be evidenced by the REST oration of the original appearance of the attachment icons in the workflow instances (in the Archive in the present case).   Cancel editing a file using OneDrive In emergency situations, (...)

(...) ction Data from WEBCON BPS can now be loaded in OData format and used in Power BI Desktop and Online. This greatly simplifies WEBCON integration with Power BI, instead of manually constructing REST API queries and dealing with token-based authentication, we are able to use one of two custom connectors to easily load data from WEBCON BPS into Power BI. Handling this data is also less cumbers (...)

(...)   Fig. 2. Example of Instance history   History contains information about the instance, its workflow, and operations performed on it by users. Unless an appropriate visibility REST riction rule has been defined, History also displays the names of all form fields along with the values entered for them, even if the user has set these fields as invisible in the Field matrix. Not (...)

(...) tioned archiving mechanism in WEBCON BPS and includes information on its configuration.   NOTE: archiving should not be confused with backup – archived forms or attachments cannot be REST ored to the operational database. Archiving is a one-way, irreversible operation.   Archiving mechanism in WEBCON BPS In WEBCON BPS a user specifies processes to undergo archiving. This (...)

(...) may take a few minutes. After successful installation, close the installer window by clicking Close.       If you had Outlook open before, you need to close it and REST art it for the newly installed add-in to appear on the ribbon. The add-in will now be available in a dedicated area on the MS Outlook ribbon.       The WEBCON area, wher (...)

(...) CON BPS. Since privileges in Designer Studio are mostly handled using groups, adding the user to a group e.g. “Test Department” will automatically grant them privileges on par with the REST of the Test Department. To manage licenses, we use the Manage BPS user licenses action.     This is not strictly a new action but is only available for installations that us (...)

(...) ources     As can be seen from the table above, the Domain users source should be used only in cases where it is absolutely necessary and the user cannot obtain the data of inteREST using the BPS users source.   Business case A process will be created in which selected WEBCON BPS users will be informed about the scheduled webinar “WEBCON BPS – What' (...)

(...) ; The “Advanced settings” tab Once you configure the “General” tab proceed to the “Advanced settings” tab. The tab is divided into two sections: “REST riction of supported e-mail sender list” – the field allows you to specify that only e-mails from senders defined in the data source are processed. “Limits of processed e-mails&rdq (...)

(...) ; The “Advanced settings” tab Once you configure the “General” tab proceed to the “Advanced settings” tab. The tab is divided into two sections: “REST riction of supported e-mail sender list” – the field allows you to specify that only e-mails from senders defined in the data source are processed. “Limits of processed e-mails&rdq (...)

(...) ; The “Advanced settings” tab Once you configure the “General” tab proceed to the “Advanced settings” tab. The tab is divided into two sections: “REST riction of supported e-mail sender list” – the field allows you to specify that only e-mails from senders defined in the data source are processed. “Limits of processed e-mails&rdq (...)