search results

for suffix

(...) e form more readable and facilitated user orientation in the case of multi-currency forms. However, WEBCON BPS 2021 has introduced some improvements that are described in this article. Prefix and suffix The name of the currency code field has been changed to “suffix.” However, no changes have been made to the way it operates. If the currency code is placed after the number, use the &l (...)

(...) Studio:   Fig. 19. The action configuration   The configuration fields are the same as the fields from the previous actions, except for the “Category” and “suffix” fields. The “Category” field defines the document category that will be assigned to the downloaded, signed document. The “suffix” field specifies the suffix that will b (...)

(...) g through the “Signed” path. In this action configuration, re-enter the AdobeSign key and indicate the technical fields with information about the uploaded file. Also you can indicate the suffix and category to which the downloaded attachment should be added.   Fig. 7. The action configuration   After creating the action of downloading the attachment,  you can (...)

(...) l be downloaded Message content – the content of the reminder sent   j) DownloadDocument It is used to download the signed document.   k) Attachment selection suffix – a suffix that will be added to the name of the downloaded document Category – a category to which the downloaded document will be sent Copy attachment ID to field – the field (...)

(...) when going through the “Signed” path – in their configuration enter the API DocuSign key settings and technical form fields with the envelope ID in DocuSign. You can also enter a suffix to the file name to distinguish them from unsigned (“_signed”).   Fig. 9. The configuration of the DownloadDocument action   There are several SDK actions that a (...)

(...) sp;   The group name (“displayName” attribute) should be consistent with the organization policy. Depending on the settings, the group naming may require specific prefix or suffix. For more information see -> https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-naming-policy. When creating the group without the required prefix, Microsoft (...)

(...)     2.2. REST Invoke Method – creating AAD user In the first tab select a previously configured connection:     In the next tab, configure REST suffix and select a HTTP method, if creating a new user set it to POST:     Next step is transferring the user object in JSON format, form field list of the user workflow is available (...)

(...) ging the authentication process. In the App registrationswindow add a new application. In the Redirect URI section provide the Portal address along with the added /signin-aad suffix. If the WEBCON BPS Portal address has not yet been defined, you can enter it after installing WEBCON BPS.     Once an app is registered, you can fill in its configuration. In t (...)

(...) At the bottom of the panel, enter the base service instance URL; it is also possible to disable the HTTPS certificates checking. On the “Request data” tab enter the URL/REST request suffix. In this example – the suffix with NIP (provided from the form) and today’s date (system variable) are given. To load responses for later mapping, instead of form fields, you must man (...)

(...) Fig. 2. Creating the REST Web Service connection     The next step is to create the REST Web Service data source – in the configuration, select the connection and the suffix URL (it will be added to the base service instance URL). The suffix can be parametrized if the API requires it (or allows it). Next, select the HTTP method (GET, POST, PUT, PATCH or DELETE). In this (...)

(...) e. Another important information is the address of the log-in website which we can find in Single sign-on configuration section in Set up SharePoint SAML tab. After copying change the address suffix from /saml2 to /wsfed.     The last step in preparing the table is copying our application’s ID. It can be found in Properties tab in Object ID field. With a correctly (...)