All Collections
Using Salto
Frequently Asked Questions
Last Change-by Username & Change-at Time Support
Last Change-by Username & Change-at Time Support
Support avatar
Written by Support
Updated over a week ago

Salto supports fetching elements' last-change-by username (author) and change-at time for some business applications.


This information is being used in environments' "Audit" tab, where you can filter changes according to their author and time, and in reports from monitors set in the "Monitor" tab.

Today, Salto supports fetching some of this information for these business applications: Salesforce, NetSuite and Zendesk.

Salesforce

Salto supports fetching elements' last-change-author and last-change-time in Salesforce, for the following:

  1. Standard object instances

  2. Custom objects, custom object instances and custom object fields

Any other elements, e.g., ones from installed packages do not have the additional change-by / at data.

Note that fields will be annotated with last-change-authors from the parent object as well as the field itself.

NetSuite

📘 Salto will only fetch NetSuite last-change-author information for changes made after an environment's first fetch.


Salto supports fetching elements' last-change-author in NetSuite, for the following types:

  1. subsidiary

  2. department

  3. classification

  4. location

  5. currency

  6. nexus

  7. account

  8. inventoryItem

  9. discountItem

  10. assemblyItem

  11. otherChargePurchaseItem

  12. descriptionItem

  13. lotNumberedAssemblyItem

  14. transactionbodycustomfield

  15. itemoptioncustomfield

  16. transactioncolumncustomfield

  17. entitycustomfield

  18. crmcustomfield

  19. itemcustomfield

  20. itemnumbercustomfield

  21. customlist

  22. customrecordtype

  23. role

  24. portlet

  25. usereventscript

  26. mapreducescript

  27. massupdatescript

  28. scheduledscript

  29. sdfinstallationscript

  30. restlet

  31. workflowactionscript

  32. suitelet

  33. clientscript

  34. bundleinstallationscript

  35. othercustomfield

  36. folder

  37. file

  38. savedsearch

  39. vendor

  40. otherChargeSaleItem

  41. serviceSaleItem

  42. nonInventoryResaleItem

  43. kitItem

  44. servicePurchaseItem

  45. paymentItem

  46. serializedInventoryItem

  47. lotNumberedInventoryItem

  48. serializedAssemblyItem

  49. nonInventoryPurchaseItem

  50. serviceResaleItem

  51. subtotalItem

  52. nonInventorySaleItem

  53. customsegment

  54. priceLevel

🚧 Note that Salto does not fetch NetSuite element last-change-time as of today. We plan to add this functionality in the future.

Zendesk

Salto supports fetching elements' last-change-author and last-change-time in Zendesk. To enable this, add the includeAuditDetails flag to your adapter configuration file fetch section:

zendesk {
  ...
  fetch = {
    ...
    includeAuditDetails = true
  }
}

Once this flag is activated, the last-change-author information will be added after the second fetch (for changes that happened after the last fetch).

The following Zendesk types will have last-change-author and last-change-time:

  • Automation

  • Macro

  • organization_field

  • business_hour_schedules

  • business_hour_schedule_holidays

  • app_installation

  • app_owned

  • Brand

  • custom_roles

  • Groups

  • category_translation

  • section_translation

  • article_translation

  • Locale

  • Trigger

The following Zendesk types will show last-change-author and last-change-time after creation, and only last-change-time once they're updated:

  • ticket_field

  • user_field

  • custom_statuses

  • Sla_policy

  • support_address

  • ticket_form

  • View

The following Zendesk types will only display the last-change-time, as Zendesk does not supply the last-change-author information for them:

  • routing_attribute_value

  • routing_attribute

  • All guide except for translations

  • Dynamic_content_item__variants

  • Dynamic_content_item

  • All guide elements (except for translations)

  • oauth_client

  • organization_field__custom_field_option

  • ticket_field__custom_field_option

  • user_field__custom_field_option

  • routing_attribute

  • routing_attribute_value

  • trigger_category

  • workspace

The following Zendesk types won't have last-change-author and last-change-time, as Zendesk does not supply this information for them:

  • All Salto created types

  • account_setting

  • macro_categories

  • target

  • webhook

  • guide_settings

  • guide_language_settings

  • channel

  • tag

  • macro_attachment

  • brand_logo

Did this answer your question?