Salto v0.3.38

Salto Version v0.3.38

New features and bug fixes

Core:

• Fixed issue where dump a Missing Static File to NaCl would create invalid syntax
• Add calculatePatch to the core api. It gets a workspace and two path directories with external service format (ie. SFDX) content, calculates the diff between them, translates them to Changes and returns "FetchResult" to be applied to the Workspace
• Added author information index that maps element ids to author information (changedBy & changedAt)
• Added getElementAuthorInformation function to workspace API
• Fixed a bug where no error would be returned when there is an invalid character in the NaCl (e.g., ')
• Omit dependency errors for elements whose parent already failed due to dependency error

CLI:

• Rename the fetch-diff command to apply-patch
• Go back to packaging the cli with node version 14.15 because that is the version being tested in unit tests

Netsuite adapter:

• Update field scriptid validation to apply only on custom fields
• Elements that have circular dependency will not be listed explicitly in deploy.xml to avoid circular dependency error
• Increase timeouts limit for HTTP requests
• HTTP requests' timeout limit can be configured through the adapter's configuration file
• FIELD_VALUE field in reportdefinition type is changed to from string to unknown type
• Open in app is supported for reportdefinition and financiallayout types
• Changes to assignment of inactive parent to a data element will be omitted with indicative error message
• Limit the filecabinet size and exclude large folders according to the size defined in the adapter's configuration file
• All files referenced in SDF will be added as dependencies in the manifest

Salesforce adapter:

• AnimationRule.recordTypeName references now work as expected
• Data instances with empty Salto ID will be omitted with indicative fetch warning
• Addition, Removal and Modification Changes of Instances of type InstalledPackage will be omitted with indicative error message

Jira adapter:

• Fixed a bug that caused null values to fail the fetch
• Fixed a bug in context options
• Added support for custom field references inside ScriptRunner's scripts in cloud and DC

Zendesk adapter:

• Fix sort of ticket form conditions

Expected changes to existing workspaces

Netsuite adapter:

• FIELD_VALUE field in reportdefinition type is changed to from string to unknown type

Salto v0.3.37

Salto Version v0.3.37

New features and bug fixes

CLI:

• When passing -cd flag on fetch operation a ‘withChangeDetection’ will passed to core with the value ‘true’ default value is false

Netsuite adapter:

• Fix date format for future dates validation in saved searches
• Throw indicative error on missing SuiteBundler feature in SuiteApp FileCabinet fetch
• Add validation for script id when adding new elements
• Paths excluded in the adapter config will be filtered out before creating the file cabinet query and will not be queried
• validate unique title field in saved search instances, financial layout instances and custom record types during deployment.
• Add internal id as a hidden field to savedsearch.
• deploy.xml will no longer be ordered according to reference level
• Removed unnecessary queries to Netsuite from the service url filter.

Salesforce Adapter:

• Add ChangeValidator for addition or modification of DataCategoryGroup, since metadata changes may be destructive
• Add missing workflow references to EntitlementProcess
• Elements from Managed Installed Packages will have generated dependency to the InstalledPackage they come from.
• Fixed issue where deploying changes to global value sets would sometimes not be considered successful even if the change was successful

Jira Adapter:

• Fixed a bug where circular workflow transitions prevented deployment
• Fixed a bug that failed fetches of non-admin users
• Improve the structure of the permissions settings instance, and rename the type from Permissions_permissions to Permissions
• Fix bug where in some cases not all instances would be returned during fetch, when a full page of project-scoped items was returned.
• Fixed a bug where a permission issue when fetching a dashboard would fail the entire fetch

Zendesk Adapter:

• Fixed deploy crashing with a modification of an instance with removal of a reference that contains an unresolved reference
• Fix fetch error for one category in a brand and no articles
• Fix bug where deploying the first instance of its kind might result in merge errors, for environments with Guide enabled but without Guide elements
• Fix bug in the deployment of custom_role modification (specifically modifications in roles that cannot be fully edited such as light_agent)
• Add change validator to validate that it is not possible to add instance when its associated brand has help center disabled.
• Fix bug where restrictions were not removed from macros that already had restrictions defined

Expected changes to existing workspaces

Salesforce adapter:

• New references may be added to instances of type EntitlementProcess
• The annotation _generated_dependencies will be added or modified to Elements from Managed Installed Packages.

Netsuite adapter:

• The saved search type will now have an internal id as a hidden annotation.

Jira adapter:

• Improve the structure of the permissions settings instance, and rename the type from Permissions_permissions to Permissions
• Fix bug where in some cases not all instances would be returned during fetch

Salto v0.3.36

Salto Version 0.3.36

New features and bug fixes

Core:

• fixed bug with partial fetches removing entries from path index.
• Fixed a bug that caused duplicate elements to be written to the NaCls

Jira Adapter:

• add support in deployment of assigning Project Category to a Project
• Fixed a fetch error when there is a screen with no tabs
• Add alias to jira elements
• Fixed field contexts validator to not return errors about elements in the plan
• Fixed a bug that when we fail to fetch a certain dashboard layout value the entire fetch would fail

Netsuite adapter:

• Remove index field from some maps in entryForm, transactionForm & workflow instances
• reportDefinitions and financialLayouts will be fetched by default and no longer need to be specified explicitly in the config
• references from suitescripts will now be included as a generated dependency in salto
• Improve parse-report-types filter
• Handle undefined values in report types
• Support omitting settings/data values with fieldsToOmit
• Add/warn about additional changes for SDF objects only
• Avoid array spread in suitescript generated dependncies

Salesforce Adapter:

• Account.Name field will now be of type salesforce.Text
• Fix rare issue of fetch failing to return some elements due to merge errors
• The annotation _restriction will be removed from Picklist and MultiPicklist CustomFields.
• Missing InstalledPackage instances will be fetched.

Zendesk Adapter:

• It is now possible to filter the fetched resources by their name.
• sort additional zendesk fields to ignore order difference
• Fix a bug causing unresolved organization IDs in views when resolveOrganizationIDs is enabled
• Added support for side conversations

Workato Adapter:

• It is now possible to filter the fetched resources by their name.

Zuora Billing adapter:

• It is now possible to filter the fetched resources by their name.

Stripe adapter:

• It is now possible to filter the fetched resources by their name.

Okta adapter:

• It is now possible to filter the fetched resources by their name.

Expected changes to existing workspaces

Jira Adapter:

• Some additional projects and issue types of field contexts might be fetched (only if there a field contexts with more than 50 issue types or projects)
• moved instances that are part of their parent instance into a folder located in their parent instance location.

Okta Adapter:

• moved instances that are part of their parent instance into a folder located in their parent instance location.

NetSuite Adapter:

• reportDefinitions and financialLayouts nacls will be added to the WS/Env
• Improve NetSuite quickFetch changed-objects queries
• Change field name in reportdefinition_criteria_values to FIELD_VALUE
• Omit dates from non "CUSTOM" report definition criteria

Salesforce adapter:

• The annotation _restriction will be removed from Picklist and MultiPicklist CustomFields.
• The activateRSS value will be removed from existing InstalledPackage instances.
• You may encounter new InstalledPackage instances that were not fetched before.
• Added references to MilestoneType on EntitlementProcess instances
• Add references to table and field in DuplicateRuleFilterItem
• HomePageComponent.links will now correctly refer to the appropriate CustomPageWebLink records
• Instance elements in namespace will automatically add the namespace to the instance's fullName if addNamespacePrefix flag is set

Zendesk Adapter:

• for type dynamic_content_item the variants array will change its order
• for type macro the restriction.ids array will change its order
• for type ticket_form the arrays child_fields , agent_conditions and end_user_conditions will change their order
• If resolveOrganizationIDs flag is enabled, organization IDs in views will be replaced with organization names
• In case a notification_webhook action of a trigger or an automation, is fetched in a bad format, the user will be warned on the deploy

Upgrading from 0.3.35

Jira Adapter:

• the following types DashboardGadgets, ProjectComponents, SecurityLevel and FieldConfigurationItems changed their location in the file tree, if you have an existing environment without pending changes you can delete the records directory and run salto restore in order to reposition all of the nacls correctly after the next fetch.

Salto v0.3.35

Salto Version 0.3.35

New features and bug fixes

Jira Adapter:

• Workflow post-function will not lose their order on fetch

Salesforce Adapter:

• Fixed go to service on instances of type Layout, RecordType, WebLink, ValidationRule, LightningPage, FieldSet, and PathAssistant

Expected changes to existing workspaces

Jira Adpter:

• The workflow's post functions will have a different order from now (according to the order in the service)

Salto v0.3.34

Salto Version 0.3.34

New features and bug fixes

Salesforce Adapter:

• Stack-traces for Apex Test failures will no longer show as [object Object]

• Picklist and MultiPicklist field values will be restricted to their value sets.

• Unknown picklist value changes will be skipped.

• Modification of Elements from managed installed package won't be blocked, and instead an informative warning message will be created.

• New Change Validator that errors on addition or removal of standard objects and fields.

  Bug fixes:

• PermissionSet instances deployment bugfix.

• CustomMetadata types deployment bugfix.

Netsuite Adapter:

• Calculate only changedAt & changedBy indexes in full fetch, and the rest on partial fetch only.
• Improve deployment of FileCabinet instances using SuiteApp.

Jira Adapter:

• Allow excluding a specific field type from the workspace.

Zendesk Adapter:

• Add alias to Zendesk Elements.
• Ensure the fetching user's locale is set to en-US.

Stripe Adapter:

• The types folder will be hidden by default.

Okta Adapter:

• The types folder will be hidden by default.

Zuora Billing Adapter:

• The types folder will be hidden by default. Standard and custom object definitions will still be visible.

Core:

• Add a new index that will hold top level elements current paths.
• Add alias to core and instance annotation.

Workspace:

• Add alias index.

Expected changes to exist workspaces

Salesforce Adapter:

• The core annotation _restriction will be added to existing Picklist and MultiPicklist fields.
• The annotation pluralLabel will be added to CustomMetadata types upon your next fetch.

Stripe Adapter:

• The types folder will be hidden by default.

Okta Adapter:

• The types folder will be hidden by default.

Zuora Billing Adapter:

• The types folder will be hidden by default. Standard and custom object definitions will still be visible.

What's Changed

• SALTO-3643: zendesk ensure the fetching user's locale is set to en us by @edenhassid in #4074
• SALTO-3766 Use elementSource in remove_sdf_elements by @dantal4 in #4088
• SALTO-3588, SALTO-3726: Deploy policy and policy rule types by @shir-reifenberg in #4075
• SALTO-3766 improve convert-lists-to-maps preDeploy filter by @dantal4 in #4087
• SALTO-3512 add change validator for addition and removal of standard … by @benisraeladi in #4076
• SALTO-3668: Support references for script runner fields by @IdoZakk in #4038
• SALTO-3733 - Salesforce: Fix identification of invalid references in formulas by @tomsellek in #4068
• INCIDENT-3754: Add more logs when uploading files to S3 by @alonstern in #4091
• SALTO-3660, SALTO-3661: add alias to core and instance annotation, add alias index by @edenhassid in #4011
• SALTO-3794: CustomMetadata type deployment bugfix by @tamtamirr in #4080
• SALTO-3663: deploy warning when modifying managed Elements in Salesforce by @tamtamirr in #3985
• SALTO-3822: Allow excluding by field type in Jira by @alonstern in #4094
• SALTO-7487 fix hash calculation for quick deploy by @Uri-Bar in #4090
• Remove redundant log in NS by @dantal4 in #4098
• SALTO-3766 improve suiteapp-file-cabinet deploy by @dantal4 in #4079
• SALTO-3825 - CLI: Deprecation message is shown when using the account command by @tomsellek in #4097
• SALTO-3479: Restrict picklist values by @tamtamirr in #3912
• SALTO-3127: Salesforce unknown picklist values Change Validator by @tamtamirr in #3907
• add logs on sdf errors by @dantal4 in #4099
• Allow passing envName to getReferenceSourcesIndex/getReferenceTargetsIndex by @dantal4 in #4100
• SALTO-3819: Add counters to remote map by @tomsellek in #4093
• SALTO-3766 improve elementsSourceIndexes by @dantal4 in #4089
• ns client refactor by @dantal4 in #4102
• SALTO-3826: Salesforce Package CV bugfix by @tamtamirr in #4105
• SALTO-3830 Add updateable to scriptRunner's added fields by @IdoZakk in #4103
• SALTO-3788/top level element path index by @guyhamo in #4066
• Bump webpack from 5.75.0 to 5.76.0 by @dependabot in #4106
• Remove unused argument in NS client validation by @dantal4 in #4109
• SALTO-3842: Fix ElemID.fromFullName for builtin type IDs by @ori-moisis in #4111
• INCIDENT-3687: problem fix, start node changed to top level element by @Shulik95 in #4114
• SALTO-3479: Bugfix by @tamtamirr in #4116
• SALTO-3832: change log.error to log.warn in audit_log by @edenhassid in #4115
• SALTO-3662: add zendesk alias by @edenhassid in #4029
• SALTO-3405 - test failure stack trace can be string or object by @benisraeladi in #4095
• SALTO-3857/missing items bug by @guyhamo in #4122
• SALTO-3713: Hide Okta, Zuora and Stripe types by default by @shir-reifenberg in #4110
• SALTO-3847: PermissionSet instances deployment bugfix by @tamtamirr in #4123
• SALTO-3858: unknown picklist values Change Validator bugfix by @tamtamirr in #4125
• SALTO-3743: Hide name for custom applications in Okta by @shir-reifenberg in #4104
• SALTO-3016 skip NS validation when there are only file cabinet instances by @dantal4 in #4126
• Skip changed file cabinet objects query when no files/folders are included by @dantal4 in #4121
• Bump to version 0.3.34 by @tamtamirr in #4127

Full Changelog: v0.3.33...v0.3.34

Salto v0.3.33

What's New in Version 0.3.33

What's New

Core:

• Performance improvements in processing time after fetching elements
• Support quick fetch when not selecting fetch target
• Fix filterInvalidChanges (in plan)
• Allow adapters to expose a fetchWithChangeDetection function that only fetches changes since the last fetch

Netsuite Adapter:

• Objects in the deploy.xml will be ordered according to their reference level
• Fix SDF deploy errors identification
• Add SDF missing feature regex
• Add missing features to manifest.xml as optional first
• In the adapter config, features are included as optional by default. In order to include a required feature add the ":required" suffix to it.
• Add support for french fetch errors
• Netsuite Fetches will not be "quick" fetches by default, but only if quick fetch was requested. Partial fetch as first fetch is not supported
• Add SDF french support
• Implement fetchWithChangeDetection to allow fetching only changes since the last fetch
• Improve parse-report-types filter
• ignore changed at values from the future.
• change-validator messages in case of a failure in removing an SDF element are different
• Skip convert-lists for file-cabinet instances
• Add specific error for sdf instance removal with missing internalId
• Do not run convert-lists filter on report types

Salesforce Adapter:

• Improved pre-deploy validation of account settings
• Improved validation of WorkflowAlerts recipients
• Change validator for SBAA ApprovalRule now returns an error upon failure
• Change of wording when deploying flows
• The Adapter will be using API version 57.0.
• Added missing references in ComponentInstanceProperty and QuickAction
• Salesforce: Improved handling of references in formulas

Jira Adapter:

• Fixed failure in getting the current user in some cases
• Fixed a bug where the fetch would fail when a holder is missing from a security level
• Deploy plan will become faster thanks to a change in the way we handle users' data
• Fixed bug where missing permissions to view other users will fail deploy/fetch

Zendesk Adapter:

• Remove changed_by from instances where it is not received by the audit_log
• Increase the default max concurrent requests
• zendesk fix get of article attachment content
• move includeAuditDetails flag to only control the addition of changed_by
• Fixed an issue when deploying a ticket_form_order with an unresolved reference in its lists
• in channel, name will no longer be in nacl case
• fix long fetch for environments with a large amount of attachments

Expected changes to existing workspaces

Salesforce adapter:
Upon your next fetch, a new Organization settings type will be created under 'salesforce/Objects/Organization/*' and its instance will be created under 'salesforce/Records/Organization/OrganizationSettings.nacl'

---

Salto v0.3.32

What's New in Version 0.3.32

What's New
Core:

• Change validator messages of undeployable values are now attached to the value instead of to the entrire instance
• Allow adapters to expose a 'fetchWithChangeDetection' function that only fetches changes since the last fetch

Jira Adapter:

• Added a change validator to block removal of issue type from a scheme if that issue type is being used in assigned projects.
• Added a change validator to block removal of schemes that are in use by proejects
• Added a change validator to block deployment of issue types with non unique names.
• Added a change validator to block workflow modification to projects with issues
• Added missing references in the default values of custom field context for the following types: select list (multiple), group picker (single and multiple) and project picker.
• Block Issue type scheme changes in active projects.
• Data center: add change validator to block deployment of project changes to priority schemes when the project has issues.
• Updated multiple change validator error messages.

Netsuite Adapter:

• Throw on SDF deploy error in other languages
• 'Changed at' annotations will no longer be able to be from the future.
• Implemented 'fetchWithChangeDetection' to allow fetching only changes since the last fetch
• Do not remove additional SOAP types
• Return only added elements in getReferencedElements
• client_validation.ts manifest error message updated address locked elements
• When choosing partial fetch, a list of supported types will be shown, allowing autocomplete and easy configuration

Zendesk Adapter:

• When a user field is changed (added/modified), there will be a validation that the user has permissions for its field, and a warning will be raised if he does not
• Added 'change at' and 'change by' annotations

• On addition and modification changes of instances that contains a reference to organizations, validate that the organization exists

• Addded missing reference in sla_policy for types: ticket_field__custom_field_options, user_field__custom_field_options and organization_field__custom_field_options

Salesforce Adapter:

• More dependencies are now extracted from formula fields
• More indicative fetch warning when data instances are omitted due to empty names.

User notifications
Jira adapter:

• The default value of custom fields from the following types: select list (multiple), group picker (single and multiple) and project picker will convert to a reference expression.

Zendesk Adapter:

• Added missing reference in sla_policy for types: ticket_field__custom_field_options, user_field__custom_field_options and organization_field__custom_field_options

Bug Fixes

Jira Adapter:

• Fixed an issue where excluding a FieldConfiguration would not exclude its items
• Fixed cases in some change validators that failed on missing fields in instances.
• Bug fix for failing deployments over workflow schemes with no items.

Zendesk Adapter:

• Fix issue in the validation of Guide translations that could cause failures in deployments.

Workspace:

• Fix field parents resolving

Salto v0.3.31

What's New in Version 0.3.31

What's New

Core

• Remove redundant field changes based on adapter's change groups
• Add a dependency when reference target is a modified non-element value
• Changed all documentation links to new Help Center at help.salto.io
• Improved state file serialization and compression to support larger workspaces.

Salesforce adapter

• Added the ability to skip changes that attempt to delete all the layouts of a specific Object.
• DuplicateRule instances that are not in sequential order will be skipped from the deploy plan.
• Added an informational message on any alteration of data
• Fetch that fails on INVALID_QUERY_FILTER_OPERATOR will suggest to exclude the problematic instances.
• Better support in organizations that have Multi Currency enabled.
• Picklist and MultiPicklist field values will be restricted to their value sets.
• Fixed a bug that didn't allow installing packages using the adapter's deploy (of InstalledPackage instance)
• Fix default market email template exclusion.

Netsuite adapter

• Fix NS SOAP reference error on deploy
• Move transformations from client to filters
• NS client now uses a dependency graph to remove all dependencies instead of validating iteratively
• Missing manifest features are added and re-deployed instead of failing deployment
• Adding the additional/required/parent changes in the first preDeploy filter to run.
• Now have the ability to delete custom record types and instances of standard types_
• Users will no longer receive confusing warning in the SDF error messages regarding these audit fields
• Extract field errors on NS client validation

Jira adapter

• User account ids in custom fields of multi user picker will now be added display names
• Add a change validator to notify the user if a change in workflow schemes will require status migration, and if it does, explain the user his options to deal with it.
• Fixed deployment of a user filter in default values
• Added defaultMissingUserFallback option to Jira adapter configuration for smoother handling of missing Jira users
• Fixed a bug which could cause duplicate workflows in case of a deployment error
• Fixed cases when the error message from the service would not be presented to the user
• Free plan users in cloud can now deploy a project without deleting the permission scheme
• Increased references coverage in JQLs

Zendesk adapter

• Add resolveOrganizationIDs fetch config option, when set to true references to organization IDs will be replaced with organization names
• Support address instance ids now also contain details from the email address, to reduce the chance of conflicting ids in cases where multiple addresses were given the same name
• Add the option to define fallback username for elements with references to missing users.
• Users will not be able to deploy any changes that includes the change of the default group
• Zendesk support templating for custom fields user and organization
• Deploy attempts on webhooks that were created by an external app, will be validated before deploy and the user will be warned about potential issues (or denied the deploy if his change is not possible)
• References to organization ids will be replaced with organization names
• guide:
  • New elements that will be created, and have no idFields - will not have '__' suffix

user notifications:
Core

• Due to a change in the state file's compression algorithm, it will not be possible to open state files created starting from this version with older Salto versions. The newer version supports both the old and the new formats.

Salesforce adapter

• For organizations with Multi Currency enabled: You may see the field CurrencyIsoCode on some of your data instances, that was previously hidden.
• The annotation _restricted will be added to existing Picklist and MultiPicklist fields.
• The field activateRSS will be added to your existing InstalledPackage instances.

jira adapter

• User account ids in custom fields of multi user picker will now be added display names
• After the next fetch, values in JQLs might be converted to references

Zendesk adapter

• References to organizations will be replaced with organization IDs, to revert this change edit the fetch config options in the config file and set resolveOrganizationIDs = true
• support_address instance elem IDs will change to a better format (name + email), which is more likely to be unique, when fetching new environments / re-fetching existing environments with regenerate Salto IDs. no impact is expected on existing environments.
• placeholders that looked like this:
  {{ticket.organization.custom_fields.<key>}} , {{ticket.organization.custom_fields.<key>.title}}, {{ticket.requester.custom_fields.<key>}}, {{ticket.requester.custom_fields.<key>.title}}
  will now have a reference expression instead of the <key>.
• Webhooks that are installed by an app, and contains installation_id in their nacl will see a new reference
  expression instead of a numeric id
• References to organization ids will be replaced with organization names

Bug Fixes

• Fixed bug preventing building Salto project on Windows systems.

Salto v0.3.30

Salto Version 0.3.30

New featurs and bug fixes

---

Release Notes:

Workspace:

• Support deserialization of fields

CLI:

• Cleaner help view when subcommand has multi-line description
• In salto account add salesforce, clarified the "Sandbox" option by changing it to "Is Sandbox/Scratch Org" because they are both considered as test orgs.

Core:

• Return ChangeWithDetails[] in diff & restore
• return ChangeWithDetails iterable on PlanItem.changes()

Infra:

• OSS release build will no longer contain dev dependencies.

Zendesk-adapter:

• Add missing reference for ticket_field, user_field, and organization_field in routing attribute value
• Support deploy of custom statuses
• Zendesk emails in support_address will include a reference expression to the brand subdomain.
• Users will be notified when trying to deploy an element with users that are missing from the target environment
• Fix special characters throwing warnings in some zendesk types
• Users will be notified when trying to deploy a macro with side conversation actions if the feature is disabled in the target account.
• Add account_features settings element
• Add fetch warning instead of failing on 403
• Notify users when custom role removal is not possible due to association to existing user agents before deploy
• Check availability of subdomain before creation of brand
• Fix deployment of a view that contains custom_statuse_id.
• Fix deployment error of ticket form when required_on_statuses has both statuses and custom_statuses fields
• Switch to new curser based pagination
• Present deploy errors in a reader-friendly way

Netsuite-adapter:

• Encountering a manifest validation error due to objects which do not appear in target account will not fail deployment, the elements will be removed to allow deployment of all other elements
• Netsuite server validation will be called on the change elements that passed all previous validations
• Omit CustomRecordType's "permissions" field by default for new WSs
• ReportDefinition and financialLayout types are now supported, will not be fetched by default.
• A warning message will be show on each change elements that contains unselected references. these references will be selected by salto deploy and will be part of the deployment
• In case of a change error on an element, only referrer with required reference on this element will be removed from the deploy set

Jira-adapter:

• Some unnecessary fields were removed from Project Role's users
• Added edit permissions to filters
• Fixed a failure in updating project with contexts
• Fixed an issue that a board without configuration would cause the fetch to fail
• Fixed a bug where a new contexts of existing fields would be written not under the field folder
• Add fetch warning instead of failing on 403
• Added change validator for when setting a default type in an issue type scheme that is not present in the types of the scheme
• Fixed creating a shared permission of a project role
• Fixed a bug when deploying a new group with an element that has a reference to it
• Additional Jira's elements with Account ID will contain in addition display name
• Add a reference between dashboard pie gadgets to the statistic type field they have in their properties.
• Added validation for workflow scheme name uniqueness on deploy
• Fixed a bug where modifying a screen would return 500 sometimes
• Added a change validator to prevent deploying a screen scheme without a default screen
• Fixed a bug where a deployment of a workflow scheme without items would not change the items in the service
• Fixed a bug where the dashboard layout validator would throw an error if the dashboard does not have gadgets
• Fixed a race condition issue when removing issue types from an issue type scheme
• In Jira cloud, instances will now be fetched in English regardless of the user language preferences
• In Jira DC mode, a fetch warning will be raised if data was pulled in a language that is not US English

Salesforce-adapter:

• Support deployment of MetadataRelationship fields.
• Deploy failure with errorMessage is now propagated to the user
• Fetch won't fail on timeout on large elements. Instead, it will skip them and suggest to exclude them from future runs.
• Improved validation of FolderShare instances
• Add the ability to quick deploy a recent validation in SF
• Improved validation of AnimationRule instances
• Some user references are now validated against Salesforce and will fail to deploy if they refer to non-existing users
• User friendly error message for HTTP_ERROR_502, REQUEST_LIMIT_EXCEEDED, INVALID_GRANT and ENOTFOUND.
• User friendly error for deployment of schedulable ApexClass.
• Fixed a bug where relatedLists of Layout instances missed picklist values.
• SF fetch stability improvement.
• CheckOnly change Validator are now configurable via config overrides
• CustomMetadata records instances will be of their correct type.
• Add support off deploying flows as inactive

Workato-adapter:

• Update to support new API Client token-based authentication

---

User Notifications:

Zendesk-adapter:

• Add missing reference for ticket_field, user_field, and organization_field in routing attribute value
• The instance default_custom_statuses will be added. It contains the default status for each of the status categories.
• zendesk emails in support_address will include a reference expression to the brand subdomain.
• In workspace instances, internal user ids in conditions will be replaced with email addresses
• In ticket_field instances of type 'lookup' and target type of 'ticket', internal user ids will be replaces with email addresses
• Add account_features settings element

Jira-adapter:

• Project Roles that contained user information will change to better represent the users
• Edit permissions will be added to Jira's NaCls (when available)
• Filters will now contain also Edit Permissions
• Costumers with automations in Jira might get change notification when doing fetch for the first time
• The following list fields are now being sorted on fetch to avoid file changes noise
  dashboard.gadgets
  workflow.Transition.properties
  workflow.statuses.properties
  projectRole.actors
• Add a reference between dashboard pie gadgets to the statistic type field they have in their properties.
• After the next fetch, the entire workspace will be fetched in English. This will create a diff for workspaces that were fetched in other languages before

Salesforce-adapter:

• Modifications on Layout.field.relatedLists.
• Major changes in the structure and path of CustomMetadata instances.

Salto v0.3.29

Salto Version 0.3.29

New features and bug fixes

---

Release Notes:

Salesforce-adapter:

• Reduce fieldPermission size on fetch
• Support fetching of instances within nested folders
• Add reference to CustomLabel in flow's inputAssignments
• Stabilize salesforce fetch on sporadic failures
• Added missing references to custom fields in CPQ instances.

Zendesk-adapter:

• When connecting a new zendesk account via CLI, user can provide custom domain that would replace zendesk domain
• validate macro actions do not point to deactivated fields

NetSuite:

• Upgrade NetSuite SDF version to 2022.2.1
• Add links to relevant docs in some NS Change Validators
• Fix bug in suiteapp file cabinet where folder parent id is unknown
• Support complex file cabinet regexes
• Increase coverage of fields to transform from lists to maps
• Remove index field from unordered mapped lists

Okta adapter:

• The types folder will be hidden by default

Jira adapter:

• The types folder will be hidden by default

Zuora adapter:

• The system types folder will be hidden by default. Standard and custom object definitions will still be visible.
• When some requests for a specific type return 404, only omit them instead of omitting the response for the entire type

Stripe adapter:

• The types folder will be hidden by default

---

User Notifications:

Salesforce:

• Profiles and PermissionSets will be modified after the next fetch
• Add reference to CustomLabel in flow's inputAssignments

Netsuite Adapter:

• Netsuite Adapter: For existing Salto Workspaces, you should reinstall the NetSuite service by creating a temporary Salto Workspace and calling salto service add netsuite --no-login.
  This will download the new SDF version that will be used globally for all WSs. The temporary Salto Workspace can be deleted.
  In addition, as part of SDF requirements, Java 17 is required.
• More lists are going to be transformed to maps
• index field will be removed from maps that the original list is unordered

Okta adapter:

• The types folder will be hidden by default

Jira adapter:

• The types folder will be hidden by default

Zuora adapter:

• The system types folder will be hidden by default. Standard and custom object definitions will still be visible.
• In some accounts, this may bring back WorkflowExport, Workflow and Task instances that were previously omitted

Stripe adapter:

• The types folder will be hidden by default