1. CRM To-Do OA Connector

Connector Capabilities

1. Binding between CRM accounts and OA accounts.

2. Single Sign-On (SSO) from OA system to CRM (SSO from CRM to OA is not supported).

3. Pushing CRM reminders and CRM To-Do tasks to the OA system.

I. OA Integration Process

1.1 Purchase the Integration Platform - OA - CRM To-Do OA Connector

Locate the corresponding product, place an order to purchase it, and the configuration entry will be automatically enabled. The configuration entry is under Admin > System Integration Management.

picture coming soon:

1.2 Account Binding

Navigate to Integration Platform Management > Connectors > CRM To-Do OA. You can bind ShareCRM employees with OA employees by creating new bindings or importing them.

picture coming soon:

Automatic Account Binding

Learn more here

1.3 Configure the Interface for Sending Messages to OA

Confirm the customer’s interface invocation method. There are slight differences in configuration between WebService and RESTful calls. The configuration documentation below will clarify how to configure each method.

II. OA Integration Configuration Steps

2.1 General Parameter Settings

Navigate to Integration Platform Management > Connectors > CRM To-Do OA > Initial Settings > General Parameter Configuration. This includes Headers Parameter Settings and Result Format Settings:

picture coming soon:

1. Headers Parameter Settings: Add key-value pairs as required by the customer. Click “Add Row,” enter the key and value, then save.

   picture coming soon:

2. Result Format Settings: Predefined keys are provided. Values must be added based on the customer’s interface response.

   picture coming soon:

   • codeName: Enter the field name for the response code.

   • msgName: Enter the field name for the response message.

   • dataName: Leave blank by default.

   • successCode: Enter the code value for a successful call.

   • xmlJsonField: For WebService, default is “out”; for RESTful, leave blank.

Example: For the response below, set codeName as code, msgName as message, and successCode as 0.

picture coming soon:

2.2 Scenario Parameter Settings

1. Navigate to Integration Platform Management > Connectors > CRM To-Do OA > Initial Settings > Scenario Parameter Settings. Enable and configure scenarios as needed. Enabled scenarios will push To-Do tasks to the OA system; disabled ones will not.

   picture coming soon:

2. Example: Adding a To-Do Task
   Click Settings under “Add To-Do” to configure:

   picture coming soon:

   • Interface URL: Enter the OA system’s To-Do task creation URL.

   • Interface Type: Select the request method (e.g., POST).

   • Body Parameters: Configure parameters using placeholders (e.g., #F001). For WebService, use XML format; for RESTful, use JSON.

   • Editing/Deleting To-Do Tasks: Update the URL, method, and parameters as per the customer’s API documentation.

3. Example Configuration
   Assume the customer provides the following API documentation:

   • Method: POST

   • URL: http://test.com.cn:909/rest/transmit/fxiaoke/create

   • Request Parameters:

     picture coming soon: picture coming soon:

   Configuration: - Interface URL: http://test.com.cn:909/rest/transmit/fxiaoke/create - Interface Type: POST - Body Parameters: Replace values with CRM field placeholders (e.g., #F001 for receiverId).

   picture coming soon:

III. Verify OA Message Push Interface

After adding, editing, or deleting To-Do tasks in ShareCRM, check the sync logs and confirm successful delivery in the OA system.

picture coming soon:

IV. SSO Integration

When users click To-Do messages in OA, they should be able to SSO into CRM. Configurations vary by vendor.

4.1 Seeyon OA

1. Authentication Method: Select “Application Registration.”

   picture coming soon:

2. Product Registration:

   picture coming soon:

3. Application Integration: Locate the app under “Application Integration.”

   picture coming soon:

4. User Binding:

   picture coming soon:

5. To-Do Integration:

   picture coming soon:

   Note: The customer must provide application credentials.

4.1.1 To-Do Message Push

Use Seeyon OA’s V5auth authentication. The system requires a token for API calls. The customer must create a ShareCRM app in Seeyon OA and provide credentials. Tokens are appended to request headers.

Script Template: ```groovy import groovy.json.JsonSlurper import sun.net.www.protocol.https.DelegateHttpsURLConnection import javax.crypto.Mac import javax.crypto.spec.SecretKeySpec

public String getToken() { String token = null; String userName = “**”; // Customer-provided username String password = “******”; // Customer-provided password String requestUrl = “http://****/seeyon/rest/token/” + userName + “/” + password; // Update the URL HttpURLConnection connection = (HttpURLConnection) new URL(requestUrl).openConnection(); connection.setRequestMethod(“GET”); connection.setConnectTimeout(15000); connection.setUseCaches(false); connection.setRequestProperty(“Content-Type”, “text/xml; charset=UTF-8”); connection.setReadTimeout(60000); connection.setDoOutput(true); connection.setDoInput(true); connection.connect(); int code = connection.getResponseCode(); if (code == 200) { InputStream inputStream = connection.getInputStream(); BufferedReader bufferedReader = new BufferedReader(new InputStreamReader(inputStream)); String line; StringBuffer buffer = new StringBuffer(); while ((line = bufferedReader.readLine()) != null) { buffer.append(line); } String str = buffer.toString(); def jsonSlurper = new JsonSlurper() Map map = jsonSlurper.parseText(str) token = map.get(“id”) } else { throw new RuntimeException(“Handshake error (“ + connection.getResponseCode() + “)!” + connection.getResponseMessage()) } return url + “?token=” + token; } url = getToken(); return url; ```

4.1.2 Single Sign-On (SSO)

SSO is authenticated via Seeyon OA’s portal mechanism. The OA platform exposes the SSO interface: https://www.fxiaoke.com/erp/syncdata/open/oa/authorizeWeb/SeeYon/login/{ei}/{isApp} Example:
https://www.fxiaoke.com/erp/syncdata/open/oa/authorizeWeb/SeeYon/login/89161/true

When a user clicks a To-Do task or the ShareCRM app in OA, the platform retrieves the token, authenticates the user via the OA portal, and redirects to the SSO page.

4.1.3 Redirect from Seeyon OA to CRM

After SSO, user information is retrieved. Redirect to CRM using: - To-Do Task:
https://www.fxiaoke.com/erp/syncdata/open/oa/authorizeWeb/SeeYon/{apiName}/{dataId}/{ei}/{isApp} - CRM Homepage:
https://www.fxiaoke.com/erp/syncdata/open/oa/authorizeWeb/SeeYon/login/{ei}/{isApp}

Reference: picture coming soon:

json { "registerCode": "3004", "taskId": "#F012", "title": "#F054 #F056 #F053", "senderName": "#F054", "state": "0", "thirdSenderId": "#F049", "thirdReceiverId": "#F001", "creationDate": "#F009", "content": "", "h5url": "https://www.fxiaoke.com/erp/syncdata/open/oa/authorizeWeb/SeeYon/#F037/#F015/714439/true", "url": "https://www.fxiaoke.com/erp/syncdata/open/oa/authorizeWeb/SeeYon/#F037/#F015/714439/false", "noneBindingSender": "", "noneBindingReceiver": "#F001" }

4.2 Weaver OA

Weaver OA Integration Case

Two implementation methods:

4.2.1 Option 1: SSO via Authentication Provider

Learn more here

4.2.2 Option 2: OA Provides Authentication Interface

picture coming soon:

When users click To-Do links in OA, additional parameters are appended to the URL for authentication.

Encryption Code: ```java import java.security.MessageDigest; import java.security.NoSuchAlgorithmException;

public class Sha1Util { public static String getSha1(byte[] input) throws NoSuchAlgorithmException { MessageDigest mDigest = MessageDigest.getInstance(“SHA1”); byte[] result = mDigest.digest(input); StringBuffer sb = new StringBuffer(); for (int i = 0; i < result.length; i++) { sb.append(Integer.toString((result[i] & 0xff) + 0x100, 16).substring(1)); } return sb.toString(); }

public static void main(String[] args) { String secret = “d73ec6289574d272c9cc2df5ff70488b”; String loginid = “0001”; String stamp = “1634128095994”; String encryptValue = secret + loginid + stamp; try { String getData = Sha1Util.getSha1(encryptValue.getBytes()); System.out.println(getData); } catch (NoSuchAlgorithmException e) { e.printStackTrace(); } } } ```

4.3 Landray OA

Contact technical consultants for identity interface details.

4.4 Yunzhijia OA

Leverage Yunzhijia’s OpenAPI for SSO:

1. Create an App in Yunzhijia’s App Center.
   Guide

2. Configuration Page:

   picture coming soon:

   API Settings Page:

   picture coming soon:

   To-Do Push URL:
   https://www.yunzhijia.com/gateway/newtodo/open/generatetodo.json?accessToken=

   picture coming soon:

   Payload Example: ```json { “content”: “Submitter: #F054”, “title”: “#F055”, “itemtitle”: “#F056”, “headImg”: “