search results

(...) mplementation of the electronic signatures by using AdobeSign requires: WEBCON BPS 2020 or higher Uploading the plugin Integration key to the AdobeSign account along with the ability to use API interfaces   First scenario A user prepares the document to be signed and then adds a list of people who should approve it.   Fig. 1. Preparing the document form &nb (...)

(...) gning documents by using DocuSign software. The plugin can be installed in any WEBCON BPS installation that uses version 2020 or higher. You must have the DocuSign account (with the ability of using API ) and an integration key generated.   Signing a document – an example of use In the contract approval workflow, a user registers a document to be signed and enters people who can a (...)

(...) the Office 365 group. To create this group, use the https://graph.microsoft.com/beta/groups (advanced description of this method can be found at https://docs.microsoft.com/en-us/graph/API /group-post-groups?view=graph-rest-beta&tabs=http). At first, configure the action of invoking the REST WebService:     In the action select the connection to the Microso (...)

(...) to deploy the solution to all sites immediately without running any feature deployment or adding apps in sites? N Will the components in the solution require permissions to access web API s that are unique and not shared with other components in the tenant? N Which type of client-side component to create? ExtensionListView Command Set What is your Comman (...)

(...) click Next.   After logging in, you will need to complete the following information: Application Name, Application Type – Server-side web application (for web apps or web API s), Home Page URL (e.g. https://webcon.com/WEBCONBPS), Redirect URL – you need to enter the address in the form: <portal address>/powerbiredirect (e.g. https://webcon.com/WEB (...)

(...) on in the AAD Register a new application in the AAD management console. It is done in a similar manner to registering an application to synchronize BPS user list.  The difference is in the API Permissions window, a new application should be granted following privileges:        2. Creating user in AAD with REST invoke method Methods which we can use in (...)

(...) p module. This includes licensing mechanisms, reports from various modules, reading and writing configuration. This component communicates with the business logic of the WEBCON BPS system. BPS Web API (REST) – a set of REST Web services hosted within WEBCON BPS Portal, responsible for handling requests from external applications. Integral to the functions of the public Web API such as loadin (...)

(...) re, after entering the correct credentials, they will return to WEBCON BPS Portal handing over the generated access token to the mobile application.   The access token is used in all REST API invoke methods and when entering on the Portal’s main page (a token is added to the request header): The access token lifetime is 1 day; when it expires – it is refreshed using the (...)

(...) or Google Drive. It allows you to avoid situations where you have several different versions of the same document because the changes made by you and by the client are not merged.   Google API preparation The process preparation should start with the Google API configuration – see https://developers.google.com/drive/API /v3/about-sdk. First, go to https://console.developers.goog (...)

(...) among other things) into email notifications to instance links.     Restoring the BPS_Config database is important if WEBCON BPS is integrated with other applications where the API Secret Key is used. Until all work is complete, you can add an entry to hosts to verify your changes.   9. Transferring the SOLR index If WEBCON BPS Search Server has been installed (...)

(...) Applies to version: 2020.1.x; author: Dawid Golonka   Introduction One of the functionalities in WEBCON BPS system is the ability of using the REST API interface. API is the basic method of data exchange between two systems and it is often used both to download data and transfer it from WEBCON BPS to other applications (e.g. data transfer to the vacation system). For more information (...)

(...) ies to version: 2020.1.x; author: Franciszek Sakławski   Introduction One of the functionalities significantly extending the potential of WEBCON BPS is the possibility of using the REST API interface. This article describes how to configure a data source based on information returned by the external services that provide their API . An example of using a REST data source can be a &ld (...)

(...) osniff Content-Security-Policy default-src 'self'; object-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' maps.googleAPI s.com; style-src 'self' 'unsafe-inline' fonts.googleAPI s.com; img-src blob: data: 'self' maps.gstatic.com *.googleAPI s.com *.ggpht; font-src 'self' fonts.gstatic.com; f (...)

(...) the access to the processes using the "Run an SQL procedure" action should be limited, as this action allows interference with the data stored in the database. The use of this action with API provided by WEBCON BPS allows you to save data from external databases such as ERP systems or a non-standard organizational structure. Downloading data from external systems can be organized in time (...)

(...) dash; 32-bit version Supported Supported Not supported (64-bit version of MS Outlook must be used) Not supported (64-bit version of MS Outlook must be used) SOAP API Not available - replaced with Public REST API (available from BPS 2019) N/A N/A N/A Public REST API 1.0 Removed N/A N/A N/A Public REST AP (...)

(...) p module. This includes licensing mechanisms, reports from various modules, reading and writing configuration. This component communicates with the business logic of the WEBCON BPS system. BPS Web API (REST) – a set of REST Web services hosted within WEBCON BPS Portal, responsible for handling requests from external applications. Integral to the functions of the public Web API such as loadin (...)

(...) bject ID 7b02e37f-73dd-445a-9138-5289e8b73ac2   Log-in provider configuration To configure our log-in provider in SharePoint we’ll use Powershell script. Add-PSSnAPI n "Microsoft.SharePoint.PowerShell" $ realm = "<Realm from Table>" $wsfedurl="<SAML single sign-on service URL from Table>" $filepath="<Full path to SAML signing certificate fi (...)

(...) pts, executables, spreadsheets with macros. The restriction will be set globally for all applications/processes and all places where you can add an attachment – forms, HotFolders, HotMailBoxes, API . When specifying the attachment size – remember that the IIS server setting is the overriding limitation on the size of the added file. NOTE: from WEBCON BPS 2022 R1 version onwar (...)

(...) onal study. WEBCON does not provide web services on servers other than  WEBCON BPS installations More information within this respect you may find at: https://developer.webcon.com/docs/rest-API / Current addresses of standard WEBCON BPS web services (BPS Web API ): [BPS Portal URL]/API  -> e.g.: https://www.mycomapny.com/webconbps/API WEB Service REST allows for, among o (...)

(...) 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 progressing f (...)