Change History

You can view the change history for Salesforce B2C Commerce objects.

The list of types change depending on the enabled settings. See Configuring Change History Preferences.

For each object, you can see when it was created, updated, or deleted. For each change, B2C Commerce generates a change event, which indicates:

See Viewing Change History.

After an object is changed, B2C Commerce stores a JSON representation of the object in its new state. If an object is deleted, B2C Commerce creates and stores a deletion notice indicating the deleted object's type, ID, and name (if available).

Different types of objects are interrelated, so an object's change history often shows changes to related objects, not just changes to the object itself. For example, if a product was added to a category or was removed from a category, the product's change history would include the change event.

Change events are aggregated over time. As a consequence, changes are not immediately viewable. It can take up to 15 minutes for B2C Commerce to recognize changes and show them in the change history.

You can view the change history for the following B2C Commerce objects.

History tabs are not available for the following object types: A/B tests, campaigns, coupons, promotions, search settings, slot configurations, and sorting rules.

Change History Details

When you are viewing change history in Business Manager: Administration > Operations > Change History (Beta), changes are summarized based on the unique combinations of five variables: date, user, scope, object, and action. Each summary line shows information using the following format:

[date] [user] [scope /] object <object_ID>] [ - action]

where:

date day on which the summarized changes occurred.
user One of the following values: name of a user; name of a user followed by "(job)" if the user manually started a job; or name of a scheduled job shown in the format "job: job_name".
scope /

One of the following values, followed by the slash character. Scope is optional and appears only if the scope is ambiguous. For example, the scope is ambiguous if you select Product in the Object Type field and accept the default values for all of the other search fields. This causes B2C Commerce to return product changes occurring in multiple scopes, which are then added to the summary line to clarify the scope in which the change occurred. If the scope is not ambiguous—for example, if you select a value in the Scope field—it doesn't appear in the summary line:

  • "Catalog <catalog_ID>" (where catalog_ID is the ID of the catalog)
  • "Price Book <price_book_ID>" (where price_book_ID is the ID of the price book)
  • "Inventory List <inventory_list_ID>" (where inventory_list_ID is the ID of the inventory list)
  • "Library <library_ID>" (where library_ID is the ID of the library)
  • "Site <site_ID>" (where site_ID is the ID of the site)
  • "Organization <organization_ID>" (where organization_ID is the ID of the organization)
object object type followed by the ID of the object.
- action

A dash character followed by one of the following values: Creation, Deletion, Update,or one of the values in the Update Actions column (see Viewing Change History).

The action is optional and appears only if the action is ambiguous. For example, the action is ambiguous if you select Product in the Object Type field and accept the defaults for all of the other search fields. This causes B2C Commerce to return product changes related to multiple actions, which are then added to the summary line to clarify the action for each change. If the action isn't ambiguous—for example, if you select a value in the Action field—it doesn't appear in the summary line.

If an object is deleted, B2C Commerce creates and stores a deletion notice indicating the deleted object's type, ID, and name (if available).

Related Links

Global Preferences