search results

(...) guration. Basic editing mode     SharePoint group as a global constant Another, more complex example, is the use of the SQL function that checks whether a user with a given login belongs to a given SharePoint group. This condition can be used to define the visibility of the form field (Invalid).   Fig.16. SharePoint group ID assigned manually. Incorrect conf (...)

(...) user.userprincipalname Remember to change class.webconbps.com in URL addresses to the website of your application. Now it’s worth to prepare all the necessary information to configure our login provider. To do that create a table with all the necessary values. Realm urn:sharepoint:class.webconbps.com Full path to SAML signing certificate file C:tempSharepo (...)

(...) on providers is described under the addresses: MSAL2 provider - Microsoft Graph | Microsoft Docs MSAL Provider - Microsoft Graph | Microsoft Docs To enable users to log into Microsoft Graph, a login component should be used. Below is the minimum set of privileges that must be granted to the application used by the authentication provider for the correct operation of the login component. Note - a (...)

(...) REGISTRATION_DATE Registration date (Date field) DATE Y Document registration date REGISTRANT Registrant (person or group) STRING Y Registrant (domain login or name) DOCUMENT_NUMBER Instance number (text field) STRING Y Automatically assigned upon registration e.g. F/2019/01/0001 WORKFLOW_ID Instance identifier (...)

(...) ios for document entry point configuration:  document entry point is a workstation accessed by many users and indicated by its IP address; document entry point is a person recognized by login entered in the browser. The person can work on many workstations; document entry point is a specific person (recognized by login ) using a specific workstation (recognized by IP address).   (...)

(...) ta from, add Metadata Access at Application level and Access all workflow instances (excluding attachments) at Process level for the user defined in the API application above (the Application’s login will be available as a user in the privilege settings). Launch Power BI and use the “Get Data” option to select the application context connector. Use the wizard to specify which proc (...)

Applies to all versions; Single-Use Access licenses available from 2023.1.1 and above. Licensing models WEBCON BPS is currently available in two licensing models – as a subscription or perpetual license paired with an annual Software Assurance payment (which allows updating to newer versions). Perpetual licensing is not usually offered on most modern markets, except for obta

(...) ve shares. The key icon indicates that identity verification is enabled for a specific share, while the general prohibition sign icon signals that the share has been locked (possibly due to exceeding login attempt limits or authorization intervals). An empty field indicates that the share is not secured. After hovering over the icons mentioned earlier, a tooltip is displayed providing information about (...)

(...) Other parameters can be left unchanged. Note that the container is not on a domain, so it is necessary to define a database username and password as an alternative to the more commonly used domain login . Start the container using the command: docker run -d -p 48441:48441 --env-file portal_env.dist --name bps_portal webconbps/portal:2023.1.1.41 where: -d – running the contain (...)

(...) profile picture. In the side menu, click on ① Integrations, and then ② Service agents → ③ New service agent.   Fill in the required fields – add the service Name and login . Note: in the login field, enter any login in UPN format. It will be used to identify the configured service agent. It is important that the Printing labels checkbox in the Service roles section (...)

(...) ple, the Honeycomb tool is used to that end. The tool is available at: https://ui.eu1.honeycomb.io/ and will be used to collect traces. Click the link provided above to enter the tool’s login page. Log in or if you have not created the account yet, click the Sign up for free today button [it is also possible to log in using your Google account (the login with Google button)].   (...)

(...) bsp;However, to gain access to Portal located at a specific address, you need to configure a respective connection. To do that, click the gear icon in the upper right corner of the mobile application login window to go to the application settings.   The window allows you to configure Portal connections (Edit connections), change system icon (Change the app icon), and gain access to info (...)

(...) ned by the data source. The columns with a gray background are required and cannot be unchecked. These are: COS_BpsID* COS_Department* COS_DisplayName* COS_Email* COS_JobTitle* COS_login * COS_ManagerBpsID COS_ManagerDisplayName The columns marked with an asterisk are the default columns loaded into the configuration of each Person or group field. Other columns can be loaded (...)

(...) llation details button takes you to a page with detailed information about your installation. The page is divided into two sections: CLIENT DATA – includes the client's name, login , and date of account creation. LICENSE SERVICES – lists the client's registered license services, including their name, status (active or inactive), environment type (DEV/TEST/PROD), and (...)

(...) udio's License management window. Follow these steps to prepare your environment for license activation: Log in to Designer Studio by selecting the authentication method and entering the login and password configured during program installation. Open the program’s main menu by clicking the icon in the upper left corner of the screen and select Licenses. The program (...)

(...) ble through Designer Studio, by going to the Licenses menu and pressing Deactivate.   Deactivation can be done Online and Offline. The Online deactivation will require the client's login and Password. If online is not possible, Offline can be used to generate a deactivation file. The deactivation can then be completed on https://activation.webcon.com by uploading the .REQ file. &n (...)

(...) the mobile application which requires access to an internet browser. Below are the functionalities listed based on how they are supported:     Native part: Profiles, login s, and PIN authorization Searching for information stored in barcodes and 2D codes PUSH notifications Scanning barcodes and 2D codes Determining exact device location Biometric authoriz (...)

(...) tegration and security are of paramount importance. It leverages existing Windows user credentials, eliminating the need for users who are logged on to their computers in the domain to re-enter their login s or passwords. The method is well-suited for automatic authentication in websites and web applications where users are usually already logged in to the Windows domain. However, due to the nature o (...)

(...) g entries to a file or the console. Detailed information on this topic, along with other useful tips, is available in the library documentation, which can be found here.   Monitoring users login s to Portal: configuration Let’s now examine the configuration that allows WEBCON BPS platform administrators to monitor user login s to Portal. As described in the previous chapter, all modif (...)

(...) llow the user to log in and perform the appropriate operations in SHO. It is a good practice to define the minimum set of permissions required to perform operations. User.Read level permissions allow login , while those from the Sites family allow operations within the SHO library. Fig. 1. Preview of application permissions in Azure   In terms of determining the required level of permi (...)