AWS partner-central documentation change
Summary
Restructured documentation with improved section organization, removed 'Sending and receiving opportunities and leads' section, updated terminology for clarity, and revised sync log descriptions
Security assessment
Changes focus on documentation structure and clarity improvements rather than addressing security vulnerabilities. The removed section about sync eligibility criteria and field requirements could impact data synchronization understanding but doesn't indicate a security flaw. No new security features or vulnerabilities are explicitly mentioned in the diff.
Diff
diff --git a/partner-central/latest/crm/crm-connector-sync-logs-and-reports.md b/partner-central/latest/crm/crm-connector-sync-logs-and-reports.md index d69266a8c..221cf9f8c 100644 --- a//partner-central/latest/crm/crm-connector-sync-logs-and-reports.md +++ b//partner-central/latest/crm/crm-connector-sync-logs-and-reports.md @@ -5 +5 @@ -Sync logsReportsSending and receiving opportunities and leads +Sync logsReports @@ -8,0 +9,11 @@ Sync logsReportsSending and receiving opportunities and leads +The following topics explain how to use sync logs and reports in the AWS Partner CRM connector app. The topics also list the log and report types, and the data they contain. + +###### Topics + + * Sync logs + + * Reports + + + + @@ -11 +22 @@ Sync logsReportsSending and receiving opportunities and leads -The **Sync Log** tab in the connector app shows the status of the synchronization records for inbound and outbound synchronization with the AWS Partner Network (APN). Partners use the tab to verify a successful sync and troubleshoot potential sync errors. +In the connector app, the **Sync Log** tab displays the status of the synchronization records for inbound and outbound APN synchronization. You use the tab to verify a successful sync and troubleshoot sync errors. @@ -13 +24 @@ The **Sync Log** tab in the connector app shows the status of the synchronizatio -AWS Partners can also use the included list views to toggle between **Inbound** and **Outbound** synchronization logs. +Use the included list views to toggle between **Inbound** and **Outbound** synchronization logs. @@ -15 +26 @@ AWS Partners can also use the included list views to toggle between **Inbound** - * **Inbound Orchestration** – Indicates the job that checks for available inbound records from APN to process. + * **Inbound Orchestration** – Indicates the job that checks for available inbound records from APN. @@ -19 +30 @@ AWS Partners can also use the included list views to toggle between **Inbound** - * **Outbound Orchestration** – Indicates the job that sends pending outbound transactions from the partners organization to APN. + * **Outbound Orchestration** – Indicates the job that sends pending outbound transactions from your organization to APN. @@ -26 +37 @@ The **Sync Log** record page shows the status of the synchronization job, the nu -The related **Sync Log** details show the individual record details processed as part of the synchronization job and their individual statuses. The following tables explain each type of log file and its related contents. +The related **Sync Log** details show the individual record details processed as part of the synchronization job, plus their individual statuses. The following tables explain each type of log file and their related contents. @@ -32,3 +43,3 @@ The related **Sync Log** details show the individual record details processed as -**Outbound File Retrieval** | Created when the outbound job runs based on frequency and whether a new set of pending records must be synced with AWS. Logs are created only when records must match the following filter specification for the outbound sync: `Updates for AWS` is `true` and `Last Sync Date` is null or `Last Sync Date` is before the `Last Modified Date` and `Last Modified By` is the user who scheduled the sync jobs. -**Inbound File Retrieval** | Created based on your inbound sync schedule. The log lists the callouts that check for pending inbound transactions from AWS to be processed. -**Inbound Record Retrieval** | Created only when the parent Inbound File Retrieval job identifies pending inbound transactions from AWS. The log contains the details of the file from AWS containing the opportunity or lead records. +**Outbound File Retrieval** | Created when the outbound job runs based on frequency and whether a new set of pending records must be synced with AWS. Logs are created only when records must match the following filter specification for the outbound sync: `Updates for AWS` is `true` and `Last Sync Date` is null, or `Last Sync Date` is before the `Last Modified Date` and `Last Modified By` is the user who scheduled the sync jobs. +**Inbound File Retrieval** | Created based on your inbound sync schedule. The log lists the callouts that check for pending inbound transactions from AWS. +**Inbound Record Retrieval** | Created only when the parent Inbound File Retrieval job identifies pending inbound transactions from AWS. The log contains the details of the file from AWS that contains the opportunity or lead records. @@ -47,3 +58,3 @@ The related **Sync Log** details show the individual record details processed as -**From AWS** | Inbound record retrieval | `API success` | A get call was made to retrieve the file listed from the `Inbound File Retrieval` operation, if one or more files exist and are pending to be processed. -**From AWS** | Inbound record retrieval | `Partial` | The file was retrieved, processing started, but not all of the records were successfully processed. In this case, review the sync log to troublshoot the failure. -**From AWS** | Inbound record retrieval | `Error` | None of the records were successfully processed due to one of the following reasons: +**From AWS** | Inbound record retrieval | `API success` | A `get` call was made to retrieve the file listed from the `Inbound File Retrieval` operation, if one or more files exist and await processing. +**From AWS** | Inbound record retrieval | `Partial` | The file was retrieved but processing failed for some records. Review the sync log to troubleshoot the failure. +**From AWS** | Inbound record retrieval | `Error` | Processing failed for all records due to one of the following reasons: @@ -55,3 +66,3 @@ The related **Sync Log** details show the individual record details processed as -**From AWS** | Inbound record retrieval | `API success` | If one or more files are present and awaiting processing, a get call is made to retrieve the file listed from the `Inbound File Retrieval` operation. -**From AWS** | Inbound record retrieval | `Partial` | The file was retrieved and processing started, but not all of the records were successfully processed. In this case, review the sync log to troubleshoot the failure. -**From AWS** | Inbound record retrieval | `Error` | None of the records were successfully processed due to one of the following reasons: +**From AWS** | Inbound record retrieval | `API success` | If one or more files are present and awaiting processing, a `get` call is made to retrieve the file listed from the `Inbound File Retrieval` operation. +**From AWS** | Inbound record retrieval | `Partial` | The file was retrieved but processing failed for some of the records. Review the sync log to troubleshoot the failure. +**From AWS** | Inbound record retrieval | `Error` | Processing failed for all records due to one of the following reasons: @@ -60 +71 @@ The related **Sync Log** details show the individual record details processed as - * The file was retrieved but none of the records in the file could be written to your Salesforce object (most likely due to a validation or permission issue). + * The file was retrieved but none of the records in the file could be written to your Salesforce object, most likely due to a validation or permission issue. @@ -63 +74 @@ The related **Sync Log** details show the individual record details processed as -**From AWS** | Inbound record retrieval | `Processed` | Record(s) included in the file were successfully processed and inserted into your mapped object. +**From AWS** | Inbound record retrieval | `Processed` | Processing succeeded and the records inserted into your mapped object. @@ -67 +78 @@ The related **Sync Log** details show the individual record details processed as -The AWS Partner CRM connector package includes reports to allow AWS Partners to track the ongoing status of the synchronization between the AWS Partner's organization and APN. +The AWS Partner CRM connector package includes reports that allow you to track the status of the synchronization between your organization and APN. @@ -93,15 +103,0 @@ Available reports include the following: -## Sending and receiving opportunities and leads - -To designate an opportunity or lead for synchronization with APN, the **Sync with Partner Central** field must be set to **True**. Additional key fields for integration include the **Last APN Sync Date** and the **Eligible to Sync with APN** field. - -These fields are included for standard opportunities and leads; however, they must be created and mapped for the corresponding object when the source objects are set to custom. - - * **Sync with Partner Central** —Included in the app for standard opportunities and leads. If a AWS Partner chooses to map to custom objects, a custom boolean field must be created and mapped in the opportunity and lead mappings, respectively. - - * **Last Sync Date with APN** —Indicates the last time the record was successfully sent to APN or received from APN. This field is autoset when the record is successfully sent to APN or an update is received from APN. - - * **Eligible to Sync with APN** —A formula field that determines if the record is targeted to be sent to APN in the next scheduled job. Calculated based on if the record was modified since the last time the outbound schedule ran, and it was updated by a user other than the designated integration user for the AWS Partner's organization. - - - - @@ -114 +110 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Creating synchronization schedules +Picklist mapping @@ -116 +112 @@ Creating synchronization schedules -Production checklist +Configuring the CRM connector