Skip to main content

Advice and answers from the Salto Team

Search results for:change by
Last Change-by Username & Change-at Time Support
Salto supports fetching elements' last-change-by username (author) and change-at time for some business… support Netsuite changed at/by support Zendesk changed at/by support… During deployments, where users can select which changes to deploy according to the changes' author or change
Salesforce changed at/by support
Salto supports fetching elements' last-change-author and last-change-time in Salesforce, for the following… object fields Any other elements, e.g., ones from installed packages do not have the additional change-by… Note that fields will be annotated with last-change-authors from the parent object as well as the field
Netsuite changed at/by support
Note that Salto will only fetch NetSuite last-change-author and last-change-time information for changes… Salto supports fetching elements' "changed by" and "changed at" information in NetSuite
Change Management Overview
Both types of changes are accessible in the Change Log tab, where you can view all fetch and deployment… more about deploying with Salto Documentation: Salto lets you add meaningful context to each change… Each fetch and deploy operation is automatically pushed to git, maintaining a clear and traceable change
Zendesk changed at/changed by support
Salto supports fetching elements' last-change-author and last-change-time in Zendesk… The following Zendesk types have last-change-author and last-change-time: Automation App… and last-change-time after creation, and only last-change-time once they're updated: Custom Statuses
You cannot change the fullName property of an element
Changing the fullName of a Salto element is not supported… This can happen if you do a "find and replace" operation and, by mistake, change the name of an element… You cannot change the fullName property of an element
Monitor your configuration
Get informed about important changes to your configuration… Filtering change type… manual), we’ll check whether the elements you monitor were changed, and notify you accordingly, with the change
Manually Pushing Environment Changes
Manually Pushing Salto Deployed Changes… recent changes, or changes made by a specific user… On the right side you can document the nature of the change via the title and message boxes
Main Use Cases
Deployments & Change Management… staging and production This set of capabilities exposes the impact a certain configuration change… is represented by a git commit and can be linked to the relevant task(s) in your ticketing system
Getting Started with Salto for Jira
How to start using Salto to explore your Jira instance, assess your changes' impact, and deploy configuration between environments… Impact Analysis - is my intended change safe to do?… Then, create a new environment by clicking the + icon in the left bar: Then, enter your Jira Cloud