Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Connection Manager • Building a Workflow • Introduction (Bizweaver)
bizweaver:connections

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
bizweaver:connections [2024/05/15 16:54]
dlee [Delete A Global Configuration] 		bizweaver:connections [2025/06/10 14:26] (current)
afernandes [SMTP Connections]
Line 20: Line 20:
   - **[[bizweaver:connections#REST Connections|REST]]**   - **[[bizweaver:connections#REST Connections|REST]]**
   - **[[bizweaver:connections#SAP Service Layer Connections|SAP Service Layer]]**   - **[[bizweaver:connections#SAP Service Layer Connections|SAP Service Layer]]**
 +  - **[[bizweaver:connections#GraphQL Connections|GraphQL]]**
  
  
Line 148: Line 149:
 ===== SMTP Connections ===== ===== SMTP Connections =====
  
-SMTP connections are used to provide connection information for the server(s) that handle email. Most installations will only have one SMTP connection. However, there is no technical restriction on the number of connections that are defined.+SMTP connections are used to provide connection information for the server(s) that handle email. Most installations will only have one SMTP connection. However, there is no technical restriction on the number of connections that are defined. You can now create SMTP connections using either basic authentication or Oauth2 authentication 
 + 
 +**Basic Authentication**
  
 {{ :bw2:bizweaverconnectionmanager8.png |}} {{ :bw2:bizweaverconnectionmanager8.png |}}
Line 156: Line 159:
   * **Enable SMTP Credentials** (Username & password) \\ <WRAP info round center> Your installation may not require SMTP credentials to send mail from Bizweaver. However, identifying a valid user in this step is required to use the error handling functions of Bizweaver. </WRAP>   * **Enable SMTP Credentials** (Username & password) \\ <WRAP info round center> Your installation may not require SMTP credentials to send mail from Bizweaver. However, identifying a valid user in this step is required to use the error handling functions of Bizweaver. </WRAP>
   * The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.   * The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.
 +
 +**Oauth2 Authentication**
 +
 +{{ :bizweaver:oauthsmtp.png |}}
 +
 +  * **Tenant ID** is a unique identifier (GUID) for your Microsoft 365 organization (Azure Active Directory tenant).
 +  * **Client ID** is a GUID that uniquely identifies the OAuth app registered in your Azure AD.
 +  * **Client Secret** is a confidential string (like a password) generated for the registered app in Azure AD.
 +  * The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.
 +<WRAP info round center> Go to the //**[[versago3:oauthsetup|Oauth Setup Instructions]]**// for instructions on how to configure SMTP Oauth with Microsoft Exchange Online
 + </WRAP>
  
 ==== Email Setup for Microsoft Office365 ==== ==== Email Setup for Microsoft Office365 ====
Line 247: Line 261:
   - **Username** and **Password** are the credentials that will be used to "login" to SAP Business One.  This user should be identified as a "superuser" and should have either a Professional or Indirect Access user license. <WRAP info round center> If  single sign-on user is used to sign in to the service layer an extra backslash is needed to pass it through the Service Layer ex: domain\\user </WRAP>   - **Username** and **Password** are the credentials that will be used to "login" to SAP Business One.  This user should be identified as a "superuser" and should have either a Professional or Indirect Access user license. <WRAP info round center> If  single sign-on user is used to sign in to the service layer an extra backslash is needed to pass it through the Service Layer ex: domain\\user </WRAP>
   - The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.   - The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.
 +
 +===== GraphQL Connections =====
 +A GraphQL connection lets your application communicate with a GraphQL server through a single HTTP endpoint. Instead of multiple REST routes (e.g., /customers, /orders, /orders/{id}), the client sends a single, self‑describing query that specifies exactly which fields it needs and how they should be nested. The server resolves that query and returns a JSON payload with only the requested data.
 +{{ :bw2:graphql.jpg |}}
 +
 +* Enter the following fields:
 +    * Connection Name: provide a unique name (e.g., CountryGraphQLConn).
 +    * Description: an optional short description (e.g., GraphQL Connection for country data).
 +    * EndPoint URI: the full URL endpoint for your GraphQL API (e.g., https://countries.trevorbladed.com).
 +* Add headers (optional).
 +    * Enter the header key (e.g., Authorization)
 +    * Enter the header value (e.g., Bearer<token value>).
 +    * Click Add Header to populate the header in the list
 +    * Repeat for additional headers as needed 
 +* Save your connection.
 +    * Click Save in the Connection Details tab
 +    * Your new GraphQL connection will now appear in the Connections list.
  
 ====== Delete A Global Configuration ====== ====== Delete A Global Configuration ======
bizweaver/connections.1715806464.txt.gz · Last modified: 2024/05/15 16:54 by dlee

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki