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

Salto v0.3.42

Salto Version 0.3.42

New features and bug fixes

Core

• Fixed issue where static files would sometimes cause elements to be in the deploy plan when only their path changed

Zendesk adapter:

• Fixed bug where deployment of an article with more than 20 attachments did not work
• Prevent illegal changes to standard fields
• app_installation instances will now have references to the corresponding app_owned instances
• Prevent deployment of automations with conditions equal to another automation
• On removal of an automation that is default in Zendesk, the user will be warned that it is not possible on a production environment
• Support missing references to dynamic content items
• Added the option to default omit all inactive instances using the typeDefaults config

Jira adapter:

• Fixed a bug that prevented fetching more than 200 statuses
• Added validation that prevents the user from adding more than one global context to custom fields
• Support deploying custom fields with more than 10K options

Netsuite adapter:

• Fixed open-in-app for some instances
• Support loading files without their attributes in SDF integration
• Added alias annotation to all elements
• Bundle field will be added to elements which are part of a bundle
• sysInfo now contains the env types (PRODUCTION, SANDBOX, BETA, INTERNAL)
• Return Salto Errors on deploy
• Timeout added to soap requests
• Support deletion in partial fetch
• Support deletion of standard instances, custom types and custom records. No support for file cabinet

Salesforce adapter:

• Added an adapter fetch configuration that controls reference generation for profiles
• Profile instances now contain more accurate data and will not include data about excluded types
• Improved stability when fetching certain types
• The adapter will use API version 58
• Support additions of SBAA Approval Rule instances with Custom conditions met
• Support retrieve of unmanaged instances for orgs with namespace defined
• Can now manage history tracking of all standard objects
• Support retrieve of unmanaged instances for orgs with namespace defined

Workato adapter:

• Add support for cross-service references to jira

Expected changes to existing workspaces

Workato adapter:

• In recipe__code instances with Jira blocks, projectKey and IssueType will appear instead of project_issuetype even if dynamicPickListSelction does not exist

Salesforce adapter:

• Data in Profile records may be removed if it refers to objects that are excluded from fetch
• Existing Workspaces of Salesforce Orgs that have a namespace defined may encounter addition of instances that were not retrieved before
• The historyTrackedFields annotation may be added to some standard object types

Zendesk adapter:

• References in nested arrays under the actions field of instances will be converted to reference expressions
• Added references to missing dynamic content items

Salto v0.3.41

New features and bug fixes

Core:

• Change fetch to only update changed elements in the state, instead of overriding all the elements
• Fix parser issue where single line strings that contained unicode newline characters would cause a parse error
• Expand validateCredentials API to return accountType and isProduction.
• Support static file path changes will as a change in Fetch

Jira adapter:

• Add support for global looped transition in Workflow's diagram
• Add support for new API to deploy circular workflow transitions
• Change Automation scope (projects field) to be sorted
• Fix a bug in scriptRunner that prevented deployment of notification post functions without users
• Fix a bug in scriptRunner, sometimes FIELD_LINK_TYPE was not parsed corretly
• Fix a bug that prevented workflow modification deployment in some cases
• Fix a bug that prevented the deployment of active workflows
• Fix a type mismatch in automations
• Improve fetch times (pagination requests will be called simultaneously)
• Change how missing references are created, and add a warning on fetch

Netsuite adapter:

• Increase SDF default timeout to 10 min
• Skip querying bundle-able fields if SuiteBundles feature is disabled

Okta adapter:

• Support fetch of 'EmailDomain' instances
• Support multibrand customizations
• Fix bug where fetch sometimes failed due to 410 error code

Salesforce adapter:

• Fix a bug when attempting to deploy new Data Record instances.
• Fix typo in CPQ default config
• Stop generating references in profile fields
• Support more dependencies from formula fields
• Support deploying additions of Data Instances that reference the same type
• Validate additional fields for unknown users
• Use a different API to fetch custom objects
• Remove some fields of OrganizationSettings

Zendesk adapter:

• Add a warning when activating a feature in account settings that this might be a paid feature
• Add workaround to a zendesk API limitation that inline article attachments are not deleted properly
• Fix bug that prevented the deploy of two articles that reference each other
• Support deploying triggers, macros and automations with action 'deflection', if the feature is activated in the service
• Change path for article attachment static files

Expected changes to existing workspaces

Code:

• Some static files might move to a different directory

Jira adapter:

• Workflows will have a new field called diagramGlobalLoopedTransition that represents a global transition location from any status to itself.
• When there are missing references, a new missing reference will appear whose purpose is to highlight the fact that there is a problem

Okta adapter:

• Changes to Brand, BrandTheme, BrandLogo and Domain instances due to recent changes in Okta
• 'EmailDomain' instances will be added

Salesforce adapter:

• References in fields of profiles will be replaced with the field's original content.
• Changing the API used for fetching custom objects will result in several changes across all custom object types, including additional data as well as changes to existing fields.

Zendesk adapter:

• Certain attachments may be deleted. Previously, these deleted attachments continued to appear in Salto, despite being removed from the Zendesk UI due to zendesk API limitation. This issue is now fixed by adding a workaround.
• Article attachment static files will move to a different location

Salto v0.3.40

Salto Version v0.3.40

New features and bug fixes

Core:

• Pass adapter operations context to loadElementsFromFolder
• Support adding alias to ObjectTypes
• On partial deploy failures, only add element IDs of elements that failed to deploy to errors.
• Unicode line terminators will no longer throw parse errors.
• Restrict account name to be equal to the adapter name in calculate-patch.
• Clarify unresolved reference validator message
• Change the change validator message to include only the first 20 chars of the value
• Receive ElemIDs in deploy errors related to specific elements
• Add a validation for deploy plans that warns when removing an element with incoming references

CLI:

• Post-deploy actions of failed changes will no longer be shown to the user (except for Salesforce CPQ failures).

Parser:

• Update the parse result with caught errors
• Fix escaped Unicode letters parsing

Adapter Utils:

• Remove deploy.ts and deploy.test.ts

Okta adapter:

• Fix a bug in include and exclude for Okta types
• Added option to fetch and deploy app logos, brand theme logo and brand theme icon.
• On 401 error, the user will get fetch warning instead of fetch failure
• Fixed bug with appUserSchema that allows to change application status while modify appUserSchema.
• Added change validator that validates that app user schema will not be deployed when its associated app is inactive.
• Fix a bug causing non existing differences in AppUserSchema instances when comparing environments
• Fix a bug in built-in applications fetch

Netsuite adapter:

• Saved search query matches date format to user preferences
• system_notes and saved_searches use date from configRecords
• Fix group changes chunks for data instances additions/deletions
• Enable excluding types with too many instances
• Fix reportdefinition's "flags" field type
• Now we support Json files in file cabinet. fetch, deploy and preview
• Invalid permission levels on customeroles will be caught in a change validator and get a ChangeError.

Salesforce adapter:

• Correct createable and updateable annotation values for Salesforce System Fields.
• Improved modelling of History and Feed History Tracking on Standard and Custom Objects.
• Changed the default config file of CPQ to rely on SF IDs instead of value-based IDs.
• Change deploy errors from Error type to SaltoError or SaltoElementError
• Fetch and deploy operations will be retried if they receive an UNABLE_TO_LOCK_ROW error

Jira adapter:

• improve deployment performance when deploying many instances
• Fixed a bug that prevented deployment of automations with user conditions of "is in group"/"Is in role"
• Fixed a bug causing all automation to be deployed with global scope
• Prevent removing of a dynamic_content_item_variant that is set as default, without having another variant set as default
• Improved fetch performance
• On 401 error, the user will get fetch warning
• Properties in any depths in gadgets will be converted from map to list
• Fixed 'getFullName' of undefined when a string value in a workflow scheme was not converted to a reference
• fix a bug with workflow diagram initial transition source
• Change dashboard gadget properties to a list, since the keys there might cause syntax errors in the nacl
• Check that custom statuses are enabled when updating zendesk.ticket_form instances that include custom_statuses under agent_conditions or end_user_conditions.
• add display name to user errors with visible id.

Zendesk adapter:

• change path for article attachment static files
• On 401 error, the user will get fetch warning instead of fetch failure
• fix error when deleting a dynamic_content_item_variant with missing locale
• fix deployment of ticket form with ticket status that is not present in the account
• fix bug where the deploy of a ticket_form with custom_statuses when custom_statuses is disabled would delete all statuses in the form

Workato adapter:

• On 401 error, the user will get fetch warning instead of fetch failure

Zuora adapter:

• On 401 error, the user will get fetch warning

Stripe adapter:

• On 401 error, the user will get fetch warning

Expected changes to existing workspaces

Salesforce adapter:

• Changes to the values of the annotations createable and updateable of System Fields in existing nacls.
• The annotation historyTrackedFields will be added to existing custom objects with history tracking enabled.
• The annotation feedHistoryTrackedFields will be added to existing custom objects with feed history tracking enabled.
• The annotation trackHistory will be removed from all custom fields
• The annotation trackFeedHistory will be removed from all custom fields
• addNamespacePrefixToFullName fetch config flag now default to true
• More elements might be fetched from namespaces
• Existing Data Records nacls will have a new _alias annotation.

Jira Adapter:

• In automations with user condition and "is in group"/"Is in role" the reference to the group/role will be in the value field instead of the id field
• Recently created automations with a non-global scope will be added scope in the projects field
• workflows have a new field called diagramInitialEntry that contains the location coordinates of the initial transition source in the workflow diagram
• Properties in dashboard gadgets will be converted from maps to lists

Okta adapter:

• Element Ids for AppUserSchema instances will change
• Built-in Application will be added on the next fetch

Workato Adapter:

• Fix bug where an uninitialized recipe (null code) could cause other recipes to not be parsed correctly, and caused recipe__code instances to not be created correctly

Netsuite Adapter:

• id field will be added in the unitsType, mainAddress and state fields
• Some custom fields (entity custom field, item custom field and crm (event) custom field) were missing from type definitions and will now appear in the relevant types.
• Running the permissions_generator script first the first time will add the generated file to existing envs.
• The field type of the "flags" field in "reportdefinition" type will be changed to "reportdefinition_flags":

type netsuite.reportdefinition {
  ...
  netsuite.reportdefinition_flags flags {
  }
}