Salto v0.3.52

Salto Version 0.3.52

New features and bug fixes

Zendesk Adapter

• Handle socket hang up errors. added the flag unassociatedAttachmentChunkSize under client to control the size of the chunks.
• Add default timeout for requests.

Jira Adapter:

• Now support deploy of order of assetsObjectTypes.
• Projects path are going to be changed to Projects -> {projects Type} ->...
• Added a fetch warning when form is untitled.

Netsuite Adapter:

• Add workflow condition warning when there are parameters with ACCOUNT_SPECIFIC_VALUES.

Salesforce Adapter:

• Data Deploy Errors will be linked to the failed Elements.
• Fixed a bug where we failed to resolve some internal ids of managed Elements.
• Salesforce partial fetch will now support deletions.
• Fixed a bug where data deploy group errors were falsely masked.

Okta Adapter:

• Validation error when user tries to add group push with groupId and application relation that already exists in the target environment.

Core:

• Change the missing dependency error to include a link to a "learn more" page.
• Added support for storing state static files in S3.

User Notifications

Jira Adapter:

• Projects path are going to be changed to Projects -> {projects Type} ->...

Salto v0.3.51

Salto Version 0.3.51

New features and bug fixes

Zendesk Adapter

• Remove merge errors on collision of elemIds
• Allow fetch without converting user Ids, either by configuration of resolveUserIDs = false in the adapter nacl, or if the users query is forbidden
• Inactive instances will be omitted by default

Jira Adapter:

• Support deployment of Asset Schema
• Support deployment of Asset Object Type
• Fix bug in deployment of Issue layout
• Change Forms elemId
• Automation elemIds can now be configured by the user
• Board type is now excluded when interfacing with the Jira Service Desk (JSM) server.
• Fix an issue with maps in Form type
• Notfiy user when trying to deploy a JSM linked Automation and JSM is not enabled in the adapter config
• Add validator to verify Board have at least one column before deployment
• Resolve bug in deployment of NotificationScheme type
• Allow fetching untitled Form
• Support deployment of Assets Attributes

Netsuite Adapter:

• Change default excluding in the adapter config
• Add important values (with adapter config addImportantValues=true)

Salesforce Adapter:

• Improved the coverage of resolving extra dependencies between Metadata components. This is a beta feature that requires the optional feature extraDependenciesV2

Core:

• New optional argument to loadWorkspace with ignoreFileChange. Using this parameter can lead to unexpected behavior if there was a NaCl change in the workspace. Use this only if you're sure there was no NaCl file update in the workspace.
• Fixed issue where loadWorkspace would have degraded performance when static file modification times changed

CLI:

• Added the option to store state file content in S3 instead of storing it locally, see command salto workspace set-state-provider

User Notifications

Jira Adapter:

• To change the current elemId for Form, perform a fetch with --regenerate-salto-ids flag. This will change the forms elemId, which may cause some disruptions
• Changes in Form structure

Zendesk Adapter:

• Inactive instances will be omitted

Salesforce Adapter:

• Using the beta feature extraDependenciesV2, may result in _extra_dependencies changes on existing NaCls.

Netsuite_Adapter:

• The _important_values annotation will be added to all types (custom record types will also have _self_important_values)

Salto v0.3.50

Salto Version 0.3.50

New features and bug fixes

Zendesk Adapter

• Move the replacement of fallback user emails also for custom object fields to happen before the deploy in order to reduce incorrect user errors (partial successes).
• Avoid crashing when resolving an article_body template expression with an unresolved reference
• Move the replacement of fallback user emails to happen before the deploy in order to reduce incorrect user errors (partial successes).

Jira Adapter:

• Now supporting metadata of fields in issueLayout, issueView and requestForm.
• Now support fetch of assets object types.
• Now supporting fetch of assets attributes.

Salesforce Adapter:

• improved validation of saltoManagementSettings configuration
• Lookup fields in records of custom objects that reference instances of metadata types are now handled correctly.
• Add deploy support in CPQ Custom Approval Rule and Conditions for accounts that use the old Salto ID Settings (non Id based).

Core:

• Removed code that would migrate very old state files to the "new" format - this would only affect workspaces that were not used for over 10 months

User Notifications

Jira adapter:

• Under issueLayout, issueView and requestForm, there will be more fields upon your next fetch.

Salto v0.3.49

Salto Version 0.3.49

New features and bug fixes

Core:

• Added environment flag SALTO_DISABLE_RESOLVE_TYPES_IN_ELEMENT_SOURCE that allows turning off type resolving in fetch / deploy
• Add skipValidations flag to preview API

Salesforce Adapter:

• Removed the valueSetFilter, which used to set deleted values of Picklist field value sets as "inactive" upon successful deployment

Jira Adapter:

• Add support for deploying JSM request types
• Add support for JSM forms (fetch and deploy)
• Add support for fetching JSM asset schemas
• Add support for fetching JSM asset statuses
• Resolve issue that caused HTTP error code 415 on some automation deletions

Zendesk Adapter:

• Remove validation for user and organization fields
• Add validation to prevent addition of a dynamic content with no default variant
• Child elements will be omitted when their parent is omitted due to elemId collision
• When the author_id in articles is a numerical value, we will no longer generate a fetch warning
• It is possible to add the email username as idField for support_address using &username
• Remove empty strings from side conversation group template expressions
• Improve performance of large deployments with no guide related changes
• Deploying order objects can now occur without all of the list items. This can assist deploying between environments that do not have some of the items in the list

Okta Adapter:

• Automation and AutomationRule elements will be added

Netsuite Adapter:

• Support excluding elements by criteria (e.g isinactive = true)

netsuite {
  ...
  exclude = {
    ...
    types = [
      ...
      {
         name = ".*"
         criteria = {
            isinactive = true
         }
      },
    ]
  }
}

Salto v0.3.48

Salto Version v0.3.48

New features and bug fixes

Core

• Fixed issue where fetching with a non-default account name could get stuck
• Omit conflicts on no-conflict core annotations.
• Ignore hidden values on calculatePatch
• Add calculatePatchFromChanges API
• Fix bug where if file x was removed and a new file was created under a (new) folder called x, we would fail on ENOTDIR (since the original file x was still there)
• Auto-merge conflicts in static-files / multi-line strings
• Add highlighted field in annotation of important values
• Fixed bug where restore/fetchFrom on element that has multiple fragments in the same file would create merge errors in nacl
• Trace log of instance deployment have bigger depth for the data
• Fixed issue where multi line quotes inside a multi line value were not properly escaped in NaCl

Workspace

• create path index for element API
• fix issue where unresolved references inside template expressions did not show as workspace warnings

Netsuite adapter:

• Fix SDF deploy dependencies when referencing an added inner object/field
• Fix CV to find invalid references in parent of field changes
• Better message in NS SOAP search error
• Support fetching bin instances. To start fetching bin instances in your environment, go to your environment configuration, remove { name = "bin" } from the fetch.exclude.types section, then add it to the fetch.include.types section.

Salesforce adapter:

• Warn when fetching data records with non-queryable fields.
• Hierarchy fields in data records are now treated as references
• The account ID of Salesforce Sandboxes will be the org URL, which is unique.
• The adapter will now use API version 59.0.
• validateCredentials on Sandboxes will now return the organization url as a stable accountId and will include extraProperties with the Organization Id
• More accurate Author Information on Custom and Standard Object.
• Add Support in deactivating Flows.
• Fixed a crash if fields with certain names were created in instances whose types did not include said fields.
• Added the 'omittedFields' data configuration.
• will now warn when deploying instances of types for which the fetching user did not have permission to read certain fields
• Bugfix: Retrieve Workflow instances on Custom Objects.
• Initial support in Fetch With Changes Detection mode, which allows fetching only instances that were updated since the last fetch and decrease the fetch time significantly.
• Introduced the 'brokenOutgoingReferencesSettings' data configuration section. Use it to control what happens when Salto encounters an invalid reference in a data record.
• Add EclairGeoData, OmniUiCard, OmniDataTransform, OmniIntegrationProcedure, OmniInteractionAccessConfig, OmniInteractionConfig, and OmniScript to default exclude list
• Support in fetching Workflow instances of Custom Objects

jira adapter:

• fix a bug in deploying global Automation using Jira DC
• Now support Fetch of issueView and RequestForm as part of Request Type instances.
• Now support deploy of portal settings.
• Now supporting deploy of SLA.
• For those who enable JSM, SLA nacls will be visible upon your next fetch
• Now support fetch of portalSettings fetch.
• Now supports deployment of portal groups.
• Now supporting fetch and deploy operations for queue.
• Now supports Workflow statuses in JSM.
• Added service Url to issue layouts.
• Now we support deploying of JSM calendars.
• Fixing bug in issue layouts that causes to duplicate elemIDs.
• Added a workaround for a Jira bug that when creating a workflow we somtimes receive an error that the workflow name is already used although it wasn't
• Fixed a bug where workflow transition configuration would not be deployed
• Add important values annotation to types
• Jsm types will be in subfolder under their related project.
• Fixed a bug that caused deployment of Issue Type Schemes to fail in certain conditions
• Now supporting fetch and deploy operations for customerPermissions.
• Automations with several projects will now have a consistent elemID (projects names in the ID are now sorted)
• Supported JSM types will contain reference mapping.
• supporting fetch of RequestType in jira's JSM.
• Fixed a bug that caused project category not to be translated into a reference after project addition
• Fixed a bug that prevented the deployment of some workflow validators
• Changed automation structure to not have projects in case it is a global automation
• Timeout for workflow scheme publish was doubled and added to the configuration
• We now able to fetch issue layouts in jira.
• salto element fix will now clean invalid projects from automation

Zendesk adapter:

• Fix potential crash on large deployments due to memory consumption
• Add the start year of an holiday to the elemID
• Deployments will no longer fail on simultaneously addition and removal of elements with equal idFields values
• Added missing reference to missing organizations in trigger, automation, sla_policy and ticket_field
• Prevent deployment of actions with custom_status_id if the feature is not enabled
• Added gaps to elements positions of triggers, automations and views
• No longer prevents deployment of a new default ticket form if the current default is not changing
• Added convertJsonIdsToReferences config, that allows convert of JSON pairs of 'id' to reference expression
• Fix crash on deployment of a guide instance without a brand
• In elements, in string fields, it is now possible to change ids in links with reference expressions
• Fixed a race condition that caused us to query the users multiple times on deploy
• Added support to fetch custom_object instances
• When using &hash in the article_attachment idFields, if the hash field does not exist it will add to the elemId the string INVALID_HASH
• Fix bug when using the OAuth credentials flow that required providing a domain argument
• Change the path of article attachment static file, the new path will end with /article_attachment/fileName/<hash>_fileName.png instead of /article_attachment/fileName.png
• Add the possibility to use &hash in idFields of article_attachment
• On deployment of custom_field_options - put the value of 'raw_name' inside 'name', because 'name' is actually the parsed value of 'raw_name'
• Hide 'name' fields as they are no longer relevant
• Fix an issue with macro attachment and organization custom_field_options, where preDeploy changes to these types were ignored
• Prevent removal of dynamic_content that is being used by types that blocks its deletion
• Add handleIdenticalAttachmentConflicts flag. when it is true it will look at all attachments with the same elemId and hash and will keep only one.
• Prevent adding a conditional ticket field to a form if the ticket field doesn't exists in the ticket fields list
• Mismatches between environments of the elemIds of groups will be prevented

Okta adapter:

• Fix issue with fetch when environment contains inactive apps with Group Push enabled
• Support fetch and deploy of Group Push
• Improvements to ProfileMapping instances
• Fetch properties push status in ProfileMapping instances
• Support deployments of ProfileMapping
• add alias to Okta elements
• GET calls will not pass the rate limit and will wait for the rate limit to reset before continuing

Salto v0.3.47

Salto Version v0.3.47

New features and bug fixes

Core

• Deploying now supports objects larger than 10MB
• Display the total number of workSpace errors from diagnostics
• Raise total number of ws errors that returns from getDiagnostics
• Add logs to all error casess in summarizeDeployChanges logic
• Add important attribute core annotation _important_values and _self_important_values
• Fix issue where "fetch from" would omit fields that were not in the path index (fields that were recently deployed)
• Fixed a bug where deploy error reportProgress wouldn't be reported for Errors with empty string
• Fix bug where regenerate salto ids would cause deletion of static file

CLI

• Added command: salto element fix

Netsuite adapter:

• Add aliases by default
• Create references in SuiteScripts for paths that don't start with a path prefix and to custom record fields
• Fix crash in data_instances_attributes trying to access "attributes" on null

Salesforce adapter:

• Add a Change Validator that forbids Additions and Deletions of Standard Fields and Objects.
• Solve LwcResources.LwcResource type discrepancy in LightningComponentBundle
• Add the ability to create extra dependencies from the tooling API only for Elements from the current organization namespace.
• Add internal ID to custom fields inside managed package if exists
• Added references between new objects to field permissions
• Add alias to Metadata Instances and CustomObject types by default.

Jira adapter:

• Added support for ScriptRunner's scripted fragments
• Fixed a bug that prevented deployment of permission schemes for some customers
• Issue layouts will not be fetched due to a performance issue for some cusomters
• Fixed a bug that prevented deployment of first instance of a ScriptRunner type
• Removing Issue Layouts
• Fixed a bug with deployments of jqls
• Fixed a bug that caused fetch to fail for custom fields with parentless cascading options
• Fixed deleting an issue type and removing it from the issue type scheme

Zendesk adapter:

• Duplicate id values CV will point to a doc with an explanation
• On begining of fetch, we will attempt to get the account subscription data and log it, only works on Zendesk production environment
• Fix deployment error where removal of a field and relevant conditions from a form at the same time would return an error
• Prevent the failure of deployment of ticket_form when ticket status ticket_field is added to the env
• View restrictions field is not ordered on fetch, removing order changes from being shown on compare
• 'field' fields that are supposed to have ticket_field can now have missing references
• ticket_form will have now missing references for ticket_fields
• Fix warning on ticket_form deployments if the ticket form has custom ticket status, and the feature it not enabled

Okta adapter:

• Improve fetch times
• RoleAssignment instances will be excluded by default, this can be changed by editing the adapter config file
• Fix a bug casing unwanted differences in GroupRule lists

Salto v0.3.46

Salto Version 0.3.46

New features and bug fixes

CLI:

• Improve readability of deploy errors in the CLI.

Core:

• Identify credentials error in fetch, deploy and validateCredentials flows.

Netsuite Adapter:

• Upgrade SDF to rely on a new JAR download URL based on 2023.1.0.
• Users will get an error when trying to deploy a workflow which contains a state with a custom field that has a non-unique scriptid.
• Improve NS change errors.
• Support subdirs of Objects folder in SDF integration.

Salesforce Adapter:

• Resolve some rare cases where deploy would get stuck.
• Deploys that miss required missing dependencies will be blocked.
• Fix crash when deploying profiles along with new custom object types.
• Custom Salto errors will include the original error from Salesforce.
• Improved Salesforce Metadata Deploy size limit error.

Zendesk Adapter:

• Prevent deployment of groups that have the same values in their Id fields.
• When the deploy flag defaultMissingOrgFallback is true, missing referenced organizations will be created on deploy.
• When filtering fetched resources by their name, child instances of omitted resources will be omitted as well.
• When omitting fields with the omitInactive configuration flag, child instances will be omitted as well.
• Allow including/excluding items by additional properties besides name, including title, raw title, key, and type.
• Annotation _alias will be added by default.
• On deployment with enableMissingReference = false, warn on any missing reference that might cause errors with the service.
• It is now possible to exclude tag instances in the fetch from config. When tags are excluded, references to them will not be created, but the referencing instances (e.g. automations and macros) will continue behaving as usual.
• Improve deployment error messages.

Jira Adapter:

• Added support for scripted fields in ScriptRunner.
• Added support for ScriptRunner's Scheduled Jobs and Escalation Services.
• Now support for issue Layout.
• When filtering fetched resources by their name, child instances of omitted resources will be omitted as well.
• ScriptRunner: Transitions ids fields are now turned into references and are updated during deployment.
• Added support for ScirptRunner's behaviors.
• Added support for ScriptRunner Listeners.
• Fixed bug with authentication to Jira DC.
• Paid users will be able to deploy issue types with hierarchy level larger than 1, but will need to change the hierarchy level through the service.
• Free users will be able to modify issue types and change their hierarchy level from 0 to -1 or backwards.
• Added support for ScriptRunner Settings.
• Fixed a bug in ScriptRunner that failed fetches for customers without the Behaviours app.
• Improve deployment error messages.

Okta Adapter:

• When filtering fetched resources by their name, child instances of omitted resources will be omitted as well.
• Added the option to fetch group memberships. To enable this feature, use 'includeGroupMemberships = true' to the fetch config in adapter config file.
• Improve deployment error messages.

Workato Adapter:

• When filtering fetched resources by their name, child instances of omitted resources will be omitted as well.
• The users will be able to add Zendesk connection to serviceConnectionNames (in workato.nacl) and get all Zendesk references in workato recipes.

Zuora Billing Adapter:

• When filtering fetched resources by their name, child instances of omitted resources will be omitted as well.

Expected changes to existing workspaces

Jira Adapter:

• Added support for scripted fields in ScriptRunner.
• Customers with ScriptRunner will have Scheduled Jobs and Escalation Services NaCls.
• Now support for issue Layout.
• ScriptRunner: Transitions ids fields are now turned into references.
• Customers with ScriptRunner will be added Added ScriptRunner's Behaviors NaCls.
• Customers with ScriptRunner enabled will see new ScriptRunner Listeners NaCls.
• Customers with ScriptRunner enabled will now see the ScriptRunner Settings NaCl.

Zendesk Adapter:

• When omitting fields with the omitInactive configuration flag, child instances will be omitted as well (e.g. ticket_field__options instances corresponding to omitted ticket_field__custom_field_options instances).
• Annotation _alias will be added by default.
• It is now possible to exclude tag instances from the fetch config. Therefore, users who only included specific types explicitly might see the tag instances removed and the references converted to strings. To revert to the old behavior, make sure to include tag in the fetch config. (no impact on functionality is expected, since tags are never deployed).

Workato Adapter:

• When using Workato. Zendesk connected recipe will include references to zendesk.

Salto v0.3.45

Salto Version 0.3.45

New features and bug fixes

Core

• Improve stability when loading a workspace

Jira adapter

• Fix bug in deployment of DashboradGadget
• Add references to Filter, Project, and Field from DashboardGadget
• Users will be notified when they are deploying more than 10K options to a custom field
• fix a bug with deploying changes on the default Field Configuration Items

Netsuite adapter:

• Upgrade SDF to rely on a new JAR download URL based on 2023.2.0
• Especially when deploying between 2 environments, users who added a file to the deployment but forgot to add the element referencing the file will get a warning. This may cause warnings for a legitimate, although not typical, action
• file references in suiteScripts that don't start with a path prefix will be added to generated dependencies
• 'classTranslationList' field in data elements and 'currency' field in inventory items will be omitted in preDeploy
• fieldToOmit added to config.deploy similar to the existing logic in config.fetch
• Permission change validator covers permissions which do not appear in NS documentation
• In case users give the same scriptid for the custom fields, the change validator will cache this and cancel the deployment instead of getting exception
• Detect known general SDF errors
• Skip integration objects on SDF folder parsing
• Add alias to definition types

Salesforce Adapter:

• Fixed regression that caused some deploys to fail in various scenarios

Zendesk Adapter:

• Prevent deactivation of ticket_field used as a condition in a form
• Failure of requesting article attachment content will no longer fail the fetch
• order of custom_fields in views is now by title and type fields
• Removal of trigger category with active triggers will be prevented
• Removal of trigger category with inactive triggers will be warned
• Prevent deployment of addition of duplicate routing attribute value

Expected changes to existing workspaces

Jira adapter:

• References to Filter, Project, and Field will be added in DashboardGadget elements

Netsuite adapter:

• file references in suiteScripts that dont start with a path prefix will be added to generated dependencies

Salto v0.3.44

Salto Version 0.3.44

Salesforce Adapter:

• Fixed Data deploy bug when added instance is marked for update.
• Fixed Metadata deploy bug when Instance value contained Salto Element and non deployable value.
• Fixed some invalid go-to-service URLs that were caused by API regression.

Netsuite Adapter:

• Add SOAP retryable error - request aborted error

Jira Adapter:

• Fixed a bug that prevented deployment of non-global field contexts.
• Fixed a bug that prevented the deployment of automations in specific conditions.
• On very specific cases there will be a change in automations of the structure of assignee or reporter fields.
• Changed workflow transitions from a list to a map.

Zendesk Adapter:

• Omit usage_7d from selected_macros in workspace.
• Missing instances in article body will have the correct type.

Core:

• Fixed files in s3_dir_store being flushed twice on each flush of the workspace

Expected changes to existing workspaces

Zendesk Adapter:

• Remove field usage_7d from selected_macros in workspace.
• article_translations with reference expressions in their body will change, the typename will change from plural to singular (eg articles -> article).

Jira Adapter:

• Workflow transitions will be kept in a map from now on. The key will be based on the name of the transition and the from field.

Salto v0.3.43

Salto Version 0.3.43

New features and bug fixes

Core:

• Performance improvements in Fetch From Workspace & Restore

CLI:

• Added -r flag to restore to also restore elements to their original paths

Zendesk Adapter:

• Personal macros will not be fetched by default
• Prevent fetch failure when macro attachment content api call returns with errors. instead, create the attachment without content and add a fetch warning
• Added validator to prevent deployment of macro attachments without content

Jira Adapter:

• Fixed a bug of inconsistent order in elements that contain a list with many objects
• Fixed a bug in change validator for non-global contexts

Salesforce Adapter:

• Support deploying Salesforce Hierarchy CustomFields
• Fixed broken go-to-service URLs
• Support deploying EmailTemplate instances with attachments
• Added the ability to configure aliases of Data Records
• Fixed an issue with deploying new custom object types to environments where multi-currency is enabled
• Improved performance and accuracy of the unknown_users change validator

Netsuite Adapter:

• Added alias to settings instances & bundles

---

Expected changes to existing workspaces

Zendesk Adapter:

• Personal macros will be removed
• Deploy of addition of attachments to an article with change validator errors will now fail

Netsuite Adapter:

• New alias annotation to existing settings instances & bundles
• References to translation collections not in the project will now raise a change error