Synchronization logging for non-technical users

Created on 2 February 2021, almost 4 years ago
Updated 31 January 2024, 11 months ago

Problem/Motivation

Site admins, who mainly oversee content and are not developers, cannot easily tell when a Salesforce sync fails for a site user. Having an easy place to view synch logs for mapped objects would be wonderful.

Backstory

We have set up a content type with fields that get pushed up to Salesforce to generate Contacts. Users log in, create content, and when their nodes are saved the synch happens. Typically. Sometimes it fails, and we cannot rely on these users to notify Site Admins. The dblog module is not enabled, Watchdog logs reside on the web server (Acquia). Not that we would want the Site Admins wading through Watchdog logs, they are not really technical folks.

Steps to reproduce

Map fields from a content type to be pushed up to Salesforce to create Contacts. Create lots of content. Observe eventual synchronization failures. Note that the only place they are logged is to Watchdog.

Proposed resolution

Based on what I read in this issue for salesforce-7.x-3.0 , evidently at one point “sync logs are recorded as revisions on each mapping object … under Content > Salesforce” which would be perfect.

Unless of course there is something wrong with my configuration that is preventing this expected behavior from happening (I have not found any documentation regarding logging), then assistance in getting that fixed would be perfect.

Remaining tasks

  1. Determine if logging as revisions on mapped objects is desired behavior.
  2. Make that happen, or implement something preferred.

User interface changes

  1. Render log info on mapped objects.
  2. Possibly offer additional options in Salesforce Logger configuration.

API changes

None.

Data model changes

None.

💬 Support request
Status

Closed: outdated

Version

4.0

Component

salesforce_logger.module

Created by

🇺🇸United States byronveale

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States AaronBauman Philadelphia

    I'm doing some cleanup on unsupported branches.
    Please re-open this issue and update the version to 5.0.x-dev if this issue is still applicable to the latest release.

Production build 0.71.5 2024