text
stringlengths 65
20k
|
|---|
7.Once you see an access allowed message, you can test your connection.Test the Connection Test your connection to ensure that it's configured successfully.1.In the page title bar, click Test.What happens next depends on whether your connection uses a Web Services Description Language (WSDL) file.If Your Connection...Then... Doesnt use a WSDL The test starts automatically and validates the inputs you provided for the connection.Uses a WSDL A dialog prompts you to select the type of connection testing to perform: Validate and Test : Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs.Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful. |
Test the Connection Test your connection to ensure that it's configured successfully.1.In the page title bar, click Test.What happens next depends on whether your connection uses a Web Services Description Language (WSDL) file.If Your Connection...Then... Doesnt use a WSDL The test starts automatically and validates the inputs you provided for the connection.Uses a WSDL A dialog prompts you to select the type of connection testing to perform: Validate and Test : Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs.Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save . |
1.In the page title bar, click Test.What happens next depends on whether your connection uses a Web Services Description Language (WSDL) file.If Your Connection...Then... Doesnt use a WSDL The test starts automatically and validates the inputs you provided for the connection.Uses a WSDL A dialog prompts you to select the type of connection testing to perform: Validate and Test : Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs.Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections. |
What happens next depends on whether your connection uses a Web Services Description Language (WSDL) file.If Your Connection...Then... Doesnt use a WSDL The test starts automatically and validates the inputs you provided for the connection.Uses a WSDL A dialog prompts you to select the type of connection testing to perform: Validate and Test : Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs.Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown. |
If Your Connection...Then... Doesnt use a WSDL The test starts automatically and validates the inputs you provided for the connection.Uses a WSDL A dialog prompts you to select the type of connection testing to perform: Validate and Test : Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs.Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate. |
Uses a WSDL A dialog prompts you to select the type of connection testing to perform: Validate and Test : Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs.Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services. |
Complete validation can take several minutes depending on the number of imported schemas and WSDLs.No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration. |
No requests are sent to the operations exposed in the WSDL.Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates . |
Test: Connects to the WSDL URL and performs a syntax check on the WSDL.No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog. |
No requests are sent to the operations exposed in the WSDL.2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed). |
2.Wait for a message about the results of the connection test.If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted. |
If the test was successful, then the connection is configured properly.If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page. |
If the test failed, then edit the configuration details you entered.Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed. |
Check for typos, verify URLs and credentials, and download the diagnostic logs for additional details.Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description. |
Continue to test until the connection is successful.3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type. |
3.When complete, click Save .Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services. |
Upload an SSL Certificate Certificates are used to validate outbound SSL connections.If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category. |
If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown.In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate. |
In that case, you must upload the appropriate certificate.A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload. |
A certificate enables Oracle Integration to connect with external services.If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication. |
If the externalChapter 2 Upload an SSL Certificate 2-4endpoint requires a specific certificate, request the certificate and then upload it into Oracle Integration.To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload. |
To upload an SSL certificate: 1.In the left navigation pane, click Home > Settings > Certificates .All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password. |
All certificates currently uploaded to the trust store are displayed in the Certificates dialog.The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore. |
The link enables you to filter by name, certificate expiration date, status, type, category, and installation method (user-installed or system-installed).Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported. |
Certificates installed by the system cannot be deleted.2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload . |
2.Click Upload at the top of the page.The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected. |
The Upload Certificate dialog box is displayed.3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support. |
3.Enter an alias name and optional description.4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate. |
4.In the Type field, select the certificate type.Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload. |
Each certificate type enables Oracle Integration to connect with external services.X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload . |
X.509 (SSL transport) SAML (Authentication & Authorization) PGP (Encryption & Decryption) X.509 (SSL transport) 1.Select a certificate category.a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category. |
a.Trust : Use this option to upload a trust certificate.i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication. |
i.Click Browse , then select the trust file (for example, .cer or .crt) to upload.b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files. |
b.Identity : Use this option to upload a certificate for two-way SSL communication.i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action. |
i.Click Browse , then select the keystore file ( .jks) to upload.ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file. |
ii.Enter the comma-separated list of passwords corresponding to key aliases.Chapter 2 Upload an SSL Certificate 2-5Note: When an identity certificate file (JKS) contains more than one private key, all the private keys must have the same password.If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload. |
If the private keys are protected with different passwords, the private keys cannot be extracted from the keystore.iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password. |
iii.Enter the password of the keystore being imported.c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file. |
c.Click Upload .SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload. |
SAML (Authentication & Authorization) 1.Note that Message Protection is automatically selected as the only available certificate category and cannot be deselected.Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No. |
Use this option to upload a keystore certificate with SAML token support.Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor. |
Create, read, update, and delete (CRUD) operations are supported with this type of certificate.2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter. |
2.Click Browse , then select the certificate file ( .cer or .crt) to upload.3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII. |
3.Click Upload .PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format. |
PGP (Encryption & Decryption) 1.Select a certificate category.Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content. |
Pretty Good Privacy (PGP) provides cryptographic privacy and authentication for communication.PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format. |
PGP is used for signing, encrypting, and decrypting files.You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use. |
You can select the private key to use for encryption or decryption when configuring the stage file action.a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text. |
a.Private : Uses a private key of the target location to decrypt the file.i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked. |
i.Click Browse , then select the PGP file to upload.ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties. |
ii.Enter the PGP private key password.b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration. |
b.Public : Uses a public key of the target location to encrypt the file.i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration. |
i.Click Browse , then select the PGP file to upload.ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection. |
ii.In the ASCII-Armor Encryption Format field, select Yes or No.Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name. |
Yes shows the format of the encrypted message in ASCII armor.ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities. |
ASCII armor is a binary-to-textual encoding converter.ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application. |
ASCII armor formats encrypted messaging in ASCII.This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run. |
This enables messages to be sent in a standard messaging format.This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run. |
This selection impacts the visibility of message content.No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run. |
No causes the message to be sent in binary format.iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition. |
iii.From the Cipher Algorithm list, select the algorithm to use.Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition. |
Symmetric- key algorithms for cryptography use the same cryptographic keys for both encryption of plain text and decryption of cipher text.c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected. |
c.Click Upload .Chapter 2 Upload an SSL Certificate 2-63 Add the Zendesk Adapter Connection to an Integration When you drag the Zendesk Adapter into the trigger or invoke area of an integration, the Adapter Endpoint Configuration Wizard is invoked.This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value. |
This wizard guides you through configuration of the Zendesk Adapter endpoint properties.The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared. |
The following sections describe the wizard pages that guide you through configuration of the Zendesk Adapter as a trigger or invoke in an integration.Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition. |
Topics: Basic Info Page Trigger Conditions Page Invoke Action Page Invoke Operations Page Summary Page Basic Info Page You can enter a name and description on the Basic Info page of each adapter in your integration.Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform. |
Element Description What do you want to call your endpoint?Provide a meaningful name so that others can understand the responsibilities of this connection.You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation. |
You can include English alphabetic characters, numbers, underscores, and hyphens in the name.You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application. |
You cant include the following characters: No blank spaces (for example, My Inbound Connection ) No special characters (for example, #;83& or righ(t)now4 ) except underscores and hyphens No multibyte characters What does this endpoint do?Enter an optional description of the connection's responsibilities.For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed. |
For example: This connection receives an inbound request to synchronize account information with the cloud application.Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ). |
Trigger Conditions Page Specify the ticket conditions that must be met for the trigger to run.Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application. |
Trigger should meet ALL of the following conditions : All trigger conditions must be met for the trigger to run.3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields. |
3-1Trigger should meet ANY of the following conditions : Either condition must be met for the trigger to run.Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page. |
Element Description Field Select the application field names to use in the condition.Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on. |
Operator Select the operator to use for the trigger condition.Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list. |
Available operators depend on the field name selected.Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket . |
Value Enter or select the value.A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list. |
A trigger condition value is the value to which the selected field is compared.Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call. |
Remove Click to remove the selected condition.Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20. |
Invoke Action Page Select the type of action to perform.Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page. |
Element Description Select action type Query information : Retrieves information from the Zendesk application corresponding to the selected module and operation.Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard. |
Create, update, or delete information : Creates a new record, updates an existing record, or deletes a record in/ from the Zendesk application.Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter. |
Operations such as Create Ticket, Update User , Permanently Delete a Ticket , and so on are performed.Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed. |
Import bulk data : Imports a large volume of records into Zendesk (for example, Bulk Update Users and Update Tickets in Batches ).Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. |
Invoke Operations Page Select the module and operation to perform on the Zendesk application.Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back. |
Note: If you cannot see one or more custom fields in the mapper or API response after you configured the operations related to the Tickets module, you must regenerate the Zendesk endpoint to see the missing fields.Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern. |
Element Description Select Create, Update or Delete (Displayed if the Create, update, or delete information option is selected on the Action page.)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations. |
)Displays the following options: Create, Update, and Delete.Chapter 3 Invoke Action Page 3-2Element Description Select module Select a module, such as Tickets, Users, Organization , and so on.Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements. |
Filter by module name Type the initial letters of the module name to filter the display of names in the list.Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions. |
Select operation Select an operation name, such as Create Ticket .Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center. |
Filter by operation name Type the initial letters of the operation name to filter the display of names in the list.Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents. |
Specify the number of records per page (Default:20 and Max:100)Enter a numerical value between 1 - 100 as the number of records to return per API call.The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow. |
The default value is 20.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps. |
Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration. |
Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration.2.Create a schedule variable to store the last run time. |
The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration.2.Create a schedule variable to store the last run time.$lastrun="" 3.Drag and drop an assign action and create two variables: Flag variable to check whether the loop has completed or not: $flag="false" Link variable to store the next pages value: $link= 4.Drag a while action and specify the condition as follows: $flag="false" 4-15.Drag a Zendesk Adapter and configure it as follows. |
For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration.2.Create a schedule variable to store the last run time.$lastrun="" 3.Drag and drop an assign action and create two variables: Flag variable to check whether the loop has completed or not: $flag="false" Link variable to store the next pages value: $link= 4.Drag a while action and specify the condition as follows: $flag="false" 4-15.Drag a Zendesk Adapter and configure it as follows.a.On the Basic info page, provide an endpoint name, and click Next . |
For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration.2.Create a schedule variable to store the last run time.$lastrun="" 3.Drag and drop an assign action and create two variables: Flag variable to check whether the loop has completed or not: $flag="false" Link variable to store the next pages value: $link= 4.Drag a while action and specify the condition as follows: $flag="false" 4-15.Drag a Zendesk Adapter and configure it as follows.a.On the Basic info page, provide an endpoint name, and click Next .b.On the Action page, select Query information , and click Next . |
To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration.2.Create a schedule variable to store the last run time.$lastrun="" 3.Drag and drop an assign action and create two variables: Flag variable to check whether the loop has completed or not: $flag="false" Link variable to store the next pages value: $link= 4.Drag a while action and specify the condition as follows: $flag="false" 4-15.Drag a Zendesk Adapter and configure it as follows.a.On the Basic info page, provide an endpoint name, and click Next .b.On the Action page, select Query information , and click Next .c.On the Operations page, select the Tickets module and Search Zendesk Modules operation, provide a value for the number of records per page, and click Done . |
To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-34 Implement Common Patterns Using the Zendesk Adapter You can use the Zendesk Adapter to implement the following common pattern.Topics: Synchronize Zendesk Tickets With ServiceNow Incidents Synchronize ServiceNow Incidents and Attachments with Zendesk Note: Oracle Integration offers a number of pre-assembled solutions, known as recipes, that provide you with a head start in building your integrations.You can start with a recipe, and then customize it to fit your needs and requirements.Depending upon the solution provided, a variety of adapters are configured in the pre-assembled solutions.See the Recipes page on the Oracle Help Center.Synchronize Zendesk Tickets With ServiceNow Incidents This use case describes how to use the Zendesk Adapter to synchronize Zendesk tickets updated at or after a certain time with ServiceNow incidents.The tickets updated in Zendesk are fetched and the details of the ticket are added as an incident in ServiceNow.This implementation pattern provides an overview of the steps.1.Create a scheduled orchestrated integration.2.Create a schedule variable to store the last run time.$lastrun="" 3.Drag and drop an assign action and create two variables: Flag variable to check whether the loop has completed or not: $flag="false" Link variable to store the next pages value: $link= 4.Drag a while action and specify the condition as follows: $flag="false" 4-15.Drag a Zendesk Adapter and configure it as follows.a.On the Basic info page, provide an endpoint name, and click Next .b.On the Action page, select Query information , and click Next .c.On the Operations page, select the Tickets module and Search Zendesk Modules operation, provide a value for the number of records per page, and click Done .d.On the Summary page, review your selections, and click Done . |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.