Salto v0.4.7

Salto Version 0.4.7

New features and bug fixes

Core

• Small performance improvements by reducing source map calculations

CLI

• Add post deployment summary

Workspace

• Remove nacl files referenced index
• Delete workspace getElementReferencedFiles API
• Reduce asynchronousity in nacl files update

NetSuite adapter

• Fix NS config suggestions when there are config overrides
• Remove the resolveAccountSpecificValues config field.
• Remove deprecated config fields

Salesforce adapter

• Support targeted fetch on specific Custom Objects
• The adapter will use API version 62.0
• Add support for settings types in SFDX.
• Deprecate the extendTriggersMetadata optional feature.
• Deprecate the improveDataBrokenReferences optional feature.
• Add references from BusinessProcess instances to StandardValueSet values. (requires the picklistsAsMaps optional feature)
• Deprecating skipAliases optional feature.
• element_api_version ChangeValidator now supports apex classes
• Severity level of errors found in multi-default change validator changed from 'Warning' to 'Error'

Microsoft Security adapter

• Enforce MS Security OAuth flow to select an account
• Add service url to specific Entra instances.
• Parse scripts in Intune application
• Add missing references under Entra Application.
• Fix Administrative Unit deployment.
• Remove fetch support for crossTenantAccessPolicy.

Jira adapter

• Improve the fetch performance for environments with many fieldConfigurations
• JSM: support assetsObjectFieldConfiguration by default
• Fixed a bug in SLA references

Okta adapter

• Users will be able to modify and remove active group rules.
• The default brand and domain for each account will now be named "Default Brand" and "Default Domain" respectively, to allow deployment of these instances between environments. This will happen in new environments, or in existing ones after regenerating Salto element IDs
• Fix a bug where some types were reported as not supporting deploy actions.
• Fix a bug where multiple "deploy not supported" validation errors are produced for the same change.

Zendesk adapter

• Add service url to the Queue type

Jamf adapter

• Solve the issue of having users' passwords in configuration profile instances, within the payload field

Expected changes to existing workspaces

Netsuite adapter

• The resolveAccountSpecificValues config field will be removed from existing adapter configs.
• The deprecated config fields will be removed from existing adapter configs.

Salesforce adapter

• Expect many changes in existing workspaces due to API version upgrade.
• Add references from Network to EmailTemplate instance under the feature networkReferences in optionalFeatures
• When the feature picklistsAsMaps is enabled, expect new references to be created in existing BusinessProcess instances.

Microsoft Security adapter

• Scripts within Intune apps will now be parsed from a base64-encoded binary blob.
• Entra applications will now include missing references.
• crossTenantAccessPolicy is no longer fetched.

Okta adapter

• After regenerating Salto element IDs, the default brand and domain for each account will be renamed "Default Brand" and "Default Domain" respectively

Zendesk adapter

• Bug fix: inactive workspaces will be removed if omitInactive is set.

Jamf adapter

• Payloads field was omitted from os_x_configuration_profile and in mobile_device_configuration_profile

Upgrading from 0.4.6

Workspace

• The getElementReferencedFiles API has been removed. If you're using it, please update your implementation to use the getElementIncomingReferences API from the lang-server package instead.

NetSuite adapter

• The resolveAccountSpecificValues configuration field was removed. If you're using it, please update your configuration accordingly.
• The deprecated config fields will be removed from existing adapter configs

Salesforce adapter

• The extendTriggersMetadata filter is now deprecated. If you're using it, please update your configuration accordingly.
• The improveDataBrokenReferences optional feature is now deprecated. If you're using it, please update your configuration accordingly.
• The skipAliases optional feature is now deprecated. If you're using it, please update your configuration accordingly.

Jira adapter

• The splitFieldConfiguration configuration field was removed. If you're using it, please update your configuration accordingly.

Salto v0.4.6

Bump to version 0.4.6 (#6820)

# Salto Version 0.4.5

## New features and bug fixes

### Core
- Improved dangling static files removal process.
- Updated logic for returning detailed changes when the primitive type changes entirely.
- Adjusted parameters for `isInitializedFolder` and `initFolder` methods to exclude `workspace`.

### Salesforce adapter
- Fixed incorrect references from WorkflowRule instances to RecordType instances (requires enabling `removeReferenceFromFilterItemToRecordType` feature).
- Addressed an issue with Active Flow Versions' incorrect internal IDs, improving `Go To Service` and `extraDependencies` behavior.
- Enhanced compatibility with more types for changes in SFDX project folders.
- Introduced methods to verify and create SFDX projects in directories.

### Okta adapter
- Added fetch and deploy support for brand-customized sign-in and error pages.
- Supported priority changes for Authorization Server policies and rules.
- Resolved a bug causing issues with priority updates in Authorization Server policy rules.

### Zendesk adapter
- Added a feature to deploy all articles as drafts (`{ fixElements: { deployArticlesAsDraft: true } }`).
- Trigger actions `set_skills` and `add_skills` now prioritize required/optional as per Zendesk API updates.

### Jira adapter
- Restructured workflow transitions, replacing `to` and `from` fields with `links` and `toStatusReference` per Atlassian API updates (Jira Cloud).

### Jamf adapter
- Implemented service URL support.

### Miscellaneous
- Dummy adapter now supports `loadElementsFromFolder` function.

## Expected changes to existing workspaces

### Salesforce adapter
- Enabling `removeReferenceFromFilterItemToRecordType` may remove existing references.
- Updates in `_generated_dependencies` of Flow elements may occur.

### Okta adapter
- NaCL files for customized brand pages will be introduced.
- Priority instances for Authorization Server policies may reflect changes.

### Zendesk adapter
- Articles will omit `draft` and `locale` fields, managed via translations.
- Trigger NaCLs will now reflect priority keys for `set_skills` and `add_skills` actions.

### Jira adapter
- Workflow transitions now reflect `links` and `toStatusReference` fields, aligning with Atlassian's updates.

Salto v0.4.4

Salto Version 0.4.4

New features and bug fixes

Core

• Improve dangling static files removal
• Return a detailed change on the whole primitive type when its primitive was changed
• Change the parameters of isInitializedFolder and initFolder not to include workspace

Netsuite adapter

• Change features config defaults
• Identify email template references in data instances
• Throw a right error on InvalidSuiteAppCredentialsError

Salesforce adapter

• (Bug-fix) Salesforce Adapter creates wrong references to RecordType instances from WorkflowRule instances. Requires the removeReferenceFromFilterItemToRecordType optional feature to be enabled.
• Fixed a bug where Active Flow Versions had wrong internal id which made Go To Service open the latest Flow version instead of the Active one, and the extraDependencies filter would give the dependencies of the latest version and not the active one.
• Added support for more types when calculating changes between SFDX project folders
• Added new methods to check for the existence of an SFDX project in a directory and for creating one.

Okta adapter

• Added fetch and deploy support for brand customized sign-in and error pages.
• Support priority changes for Authorization Server policies
• Fix a bug in priority change for Authorization Server policy rules

Jira adapter

• SALTO-5887: Fix a bug where RequestType field name in JSM is different for some old envs
• Workflow transitions will no longer have the to and from fields, instead we will use links and toStatusReference due to an Atlassian API change (Jira Cloud only).

Zendesk adapter

• Add a flag that will deploy all Zendesk articles as drafts: { fixElements: { deployArticlesAsDraft: true } }
• set_skills or add_skills under Trigger actions will now have a priority of required or optional as per https://developer.zendesk.com/documentation/ticketing/using-the-zendesk-api/setting-skill-priority-with-skills-in-trigger-action/

Jamf adapter

• support service url

Dummy adapter

• Dummy adapter supports loadElementsFromFolder function

Expected changes to existing workspaces

Salesforce adapter

• Enabling the removeReferenceFromFilterItemToRecordType optional feature may result in removal of references.
• You may notice changes in your existing Flows _generated_dependencies.

Okta adapter

• New NaCL files should be added for customized brand pages (error and sign-in pages).
• Instances representing priority order for Authorization Server policies will be added.

Netsuite adapter

• Fields in custom record types that reference email template will replace their field type:

-  unknown custom_custrecord_email_template {
+  netsuite.emailtemplateReference custom_custrecord_email_template {
     scriptid = “custrecord_email_template”

• References to email templates in data instances will replace ASVs:

-  custom_custrecord_email_template = {
-    id = “[ACCOUNT_SPECIFIC_VALUE] (object) (email template name)
-  }
+  custom_custrecord_email_template = netsuite.emailtemplate.instance.custtemailtmpl123

Zendesk adapter

• Article instances will have the fields draft and locale omitted, as they are controlled via their translations.
• Trigger nacls with set_skills or add_skills will now include a priority key if this is received from Zendesk.

Jamf adapter

• support service url

Jira adapter

• Workflow transitions will no longer have the to and from fields, instead we will use links and toStatusReference due to an Atlassian API change (Jira Cloud only).

Salto v0.4.3

Salto Version 0.4.3

New features and bug fixes

Salesforce adapter

• (Bug-fix) Profile layoutAssignments may not result in missing assignments of RecordTypes when requests are being chunked
• (Bug-fix) Salesforce Profiles fetch results in incorrect values when retrieve requests are being chunked

Jira adapter

• Add projectId reference for JSM automation within components

Zendesk adapter

• (Bug-fix) view nacls will contain a missing reference for custom_status instead of unresolved ids
• Article translation body will be moved to a static file - instead of the content inline, there will be a link to the static file.

Okta adapter

• Added a dependency changer between each policy\policyRule to its prior policy\policyRule in order to prevent race conditions that could result in policies being assigned the same priority.

Microsoft Security adapter:

• Support fetch & deploy for Intune Windows-Information-Protection Application policies

Salto v0.4.3

Salto Version 0.4.3

New features and bug fixes

Salesforce adapter

• (Bug-fix) Profile layoutAssignments may not result in missing assignments of RecordTypes when requests are being chunked
• (Bug-fix) Salesforce Profiles fetch results in incorrect values when retrieve requests are being chunked

Jira adapter

• Add projectId reference for JSM automation within components

Zendesk adapter

• (Bug-fix) view nacls will contain a missing reference for custom_status instead of unresolved ids
• Article translation body will be moved to a static file - instead of the content inline, there will be a link to the static file.

Okta adapter

• Added a dependency changer between each policy\policyRule to its prior policy\policyRule in order to prevent race conditions that could result in policies being assigned the same priority.

Microsoft Security adapter:

• Support fetch & deploy for Intune Windows-Information-Protection Application policies

Salto v0.4.1

Salto Version 0.4.1

Core

• Slight performance improvement when loading workspaces without a valid workspace cache
• Fixed issue where fetch in “isolated” mode could potentially drop field attributes in some cases
• fix OOM error when cloning large amount of Fields

CLI

• Added cli command to sync a salto workspace to an adapter format folder

Jira adapter

• Parse additional smart values in automations. To enable this feature add parseAdditionalAutomationExpressions config flag under the fetch section
• Fixed deployment annotations in ScriptRunner for DC
• Check the existence of field context order when adding an option
• Improve memory usage of custom references calculation
• Update for a few filters related to field contexts and options
• Fix deletion of automation label from an Automation
• Update filters related to splitting options from contexts
• Validate that the context order instance reference all of it’s options and validate the default values of the context

Zendesk adapter

• Create fetch warning when failing to get brand logos due to insufficient permissions, instead of failing the entire fetch
• Add support for custom omnichannel routing queues

Netsuite adapter

• Allow users to config the SOAP WSDL version used by SoapClient using the suiteAppClient.wsdlVersion adapter config
• Identify more ASVs, unresolved [ACCOUNT_SPECIFIC_VALUE] values may be resolved

Microsoft Security adapter

• Support fetch & deploy for Device Configurations.
• Support fetch & deploy for Device Configurations - Setting Catalog.
• Support fetch & deploy for Device Configurations.
• Support fetch & deploy for Application Configuration [Managed Devices]
• Support fetch & deploy for Application Configuration [Managed Apps]

Okta adapter

• Fix a bug in the deployment of custom apps when subdomain has changed. Name field will be removed for custom SAML and AUTO_LOGIN applications.
• Fixed a bug where applications with similar names caused a naming collision for their logo file names, resulting in pending changes after fetch / restore. AppLogo file names may change to ensure uniqueness.
• Support deployment of Authorization Server scopes
• Fix a bug in deployment of Authorization Server Policy Rules that references scopes. Reference will be added in Authorization Server Policy Rule that references Auth Scopes

Salesforce adapter

• Improved the progress report of deploy operation.
• Implement PermissionSet/MutingPermissionSet Elements fixer (turned off by default)

Salto v0.4.0

Salto Version 0.4.0

Changed license to be under the Salto Terms of Use

New features and bug fixes

Core

• Fix bug where fetch returns an empty response when the only changes in fetch are modifications to static resources.
• List items comparison will not throw when there's null / undefined in an item.
• Support auto-merge for lists.

Salesforce Adapter

• Improved time of Change-Based fetches (withChangesDetection) for organizations with a large amount of Apex Classes.
• In ID collision errors - a link to the service will now appear if it exists.
• Bugfix: CPQ Rules and Conditions Filter creates invalid TemplateExpressions when no conditions are fetched for Rule.
• Fixed an issue where the profiles Elements fixer resulted in wrong removals from the Profile.
• Fix the "Can not resolve ..." error on Flow deactivation changes.
• Show an error message if the deploy is canceled.
• Removed coordinate fields of flow components that belong to a flow with AUTO_LAYOUT_CANVAS mode.
• ManagedEventSubscription is now excluded by default for new accounts.

Zendesk Adapter

• Add support for custom layouts.
• In ID collision errors - a link to the service will now appear if it exists.
• Support deploying Custom Fields with Options.
• Ticket form restricted_brand_ids are now sorted, as these cannot be updated by users.
• Workspace selected macros restriction ids are now sorted, as these cannot be updated by users.

Netsuite Adapter

• useChangesDetection is no longer supported. Use changed-based fetch.
• Support deploy of changes in nested custom fields in data instances (e.g. custom fields under the subsidiary.mainAddress field).
• Commented-out JS code will not be added as a generated dependency in SuiteScripts.
• Ignore FileCabinet errors on SDF validation.
• Identify ASVs in multiselect field.
• Recognize more fields and types for ASVs type.
• Improve condition formula parsing for ASVs.
• Prevent getting "Invalid login attempt" after a delayed request (e.g. due to concurrency limit).

Jira Adapter

• Moved JSM forms to the new API.
• Fixed a bug with FieldConfiguration deployment in Jira DC.
• Opened enableNewWorkflowAPI config flag by default.
• Fixed a bug that caused duplicate attributes due to an empty string in the context option's key.
• Inside Form type, the jiraField will change from string to reference.
• Validate uniqueness in Project's name and key.
• ObjectTypeOrder instances will no longer have assetSchema field.
• Enable the option to filter objects by state field in the fetch.
• Fix custom fields deletion.
• Fixed a bug where users can not deploy addition of default SLA.
• Support fetching and deploying development field in issue layout.
• Added support for JSM workflow approvals.
• Added support for assignee type in projects.
• Fixed a bug in Jira DC causing components with no lead to fail deployment.
• Fixed a bug that prevented deployment of components with lead ID in DC.
• Fixed a bug that caused some automation deployments to fail.
• Fixed a bug in fieldConfiguration deployment in Jira DC - to enable it you should upgrade Salto's plugin via the marketplace.
• Support Atlassian change in automation's email recipients from group name to group id.
• Check unique names in SLAs and field contexts.
• Fixed a bug caused by circular dependency between root ObjectType, ObjectTypeOrder and ObjectSchema.

Okta Adapter

• Fixed a bug where modifying ApplicationGroupAssignment failed with a 400 HTTP status code.
• Fixed an issue when deploying an AppUserSchema with an undefined custom properties.
• Removed an unnecessary API request when only activating / deactivating an AuthorizationServerPolicy instance without other modifications.
• References to groups will be added to Identity Provider instances with assigned groups.
• Add reference from UserSchema type to Application type.
• Fix a bug in MultifactorEnrollmentPolicy when deployed with Authenticator.
• Add validation to prevent deployment of MultifactorEnrollmentPolicy with disabled Authenticator.
• Add deploy support for IdentityProvider type.
• Add option support in Identity Provider JsonWebKey type (excluded by default for all users).
• Fixed a bug where email domains are dropped after being deleted and recreated, by omitting all currently-deleted email domains in fetch.
• Exclude ProfileMapping type from Salto when the type is not enabled in the Okta account.

Confluence Adapter

• Support excluding space specific types or statuses through user config.
• Support fetch and deploy of groups.
• Fix space deployment.
• Support blog_post modification deployment.
• Fix issue where hidden id fields were written to the nacl when deploying the first instance of a type.
• Stop fetching templates for archived spaces.

Microsoft Security Adapter

• Added a shared adapter for Microsoft Entra and Microsoft Intune.
• Extended fetch coverage and deployment support, and added more references.

JAMF Pro Adapter

• Convert error to Unauthorized error for statuses 401 and 403.

Expected changes to existing workspaces

Salesforce Adapter

• Removed coordinate fields of flow components that belong to a flow with AUTO_LAYOUT_CANVAS mode.

Zendesk Adapter

• In contextual workspaces, the layout_uuid field will be updated to be a reference to a layout.
• Existing custom_object_field__custom_field_options instance will have their name field removed as it should be managed through its raw counterpart (raw_name).
• Ticket form restricted_brand_ids are now sorted, as these cannot be updated by users.
• Workspace selected macros restriction ids are now sorted, as these cannot be updated by users.

Jira Adapter

• Changes will be applied in Form instances:
  The fields issueRequestTypeIds, newIssueIssueTypeIds, newIssueRequestTypeIds will be replaced by recommendedIssueRequestTypeIds, issueCreateIssueTypeIds, issueCreateRequestTypeIds.
• Workflow instances will change their structure and will be called WorkflowConfiguration.
• The empty string inside the options field in CustomFieldContext will now be replaced by '@'.
• Inside Form type, the jiraField will change from string to reference.
• ObjectTypeOrder instances will no longer have assetSchema field.
• One or more fields of type PANEL will be added to the issueLayout type.
• Projects will be added with assignee type.
• Automations will no longer contain their uuid.
• Automations with email group recipients will be references again.

Okta Adapter

• References to groups will be added to Identity Provider instances with assigned groups.
• UserSchema instances with properties sourced by external app will have Application reference added.
• Additional fields will be added to IdentityProvider type.
• Email domains that have validationStatus = "DELETED" will be omitted.

Netsuite Adapter

• Unresolved [ACCOUNT_SPECIFIC_VALUE] values may be resolved.

Salto v0.3.61

Salto Version 0.3.61

New features and bug fixes

General

• With the introduction of Turbocache, when you wish to build, test or lint a specific package, use the --filter argument, e.g.:
  yarn build --filter @salto-io/zendesk-adapter
  yarn test --filter @salto-io/netsuite-adapter
  yarn lint --filter @salto-io/salesforce-adapter

• with this PR, we now support turbocache for both local tests and CircleCI.
  if you need to test a specific package, do (for example):
  yarn test --filter @salto-io/zendesk-adapter
  before the turbocache run, we will check if any source files have been modified in any of the dependencies of the package you are testing (or the entire project, if you run all tests).

VS-Code Extension

• Support for meta types syntax.

Core

• allowEmpty param is removed from transformElement. Alternatively, you may use allowEmptyArrays and allowEmptyObjects.
• Fixed a bug parsing template static files with string interpolations.
• Improved the handling of attribute values in getElementHiddenParts.
• Fixing a bug that occurs when trying to apply a change which modifies an entire base type.
• add filterFunc to applyDetailedChanges.
• Change the API of createDiffChanges to receive an object param, and add it compareOptions, that are used in the elements comparison.

NetSuite adapter

• fix fixElements of form fields that reference objects with appid

Jira adapter

• keep post functions order in DC
• Fixed a bug that caused errors in deployment when an issue layout had a missing parent reference
• Fixed a bug that caused a change validator to fail a deploy operation

Salesforce adapter

• Added pre & post deploy actions that guide users to disable their billing triggers for CPQ Billing Deployments.
• Improved caching of listMetadataObjects: Same type won't be listed twice even when the requests are created concurrently.
• Fixed a bug where deploy of LightningWebComponent failed on Attribute name "default" associated with an element type "property" must be followed by the ' = ' character.
• Renamed the internal and hidden CustomObject and CustomMetadata types to _CustomObject and _CustomMetadata.
• Renamed the internal and hidden CustomObject and CustomMetadata types to _CustomObject and _CustomMetadata.
• Improved the dependencies between CPQ Rules and their conditions to avoid deploy issues due to missing reference.
• Adds meta types to Salesforce types.
• Excluding MutingPermissionSets and PermissionSetGroups by default for new accounts.
  -Aligning MutingPermissionSet instances support with PermissionSets.
• Add references for QuickAction fieldOverrides.
• The adapter will use API 61.0.
  Salesforce Types folder will be hidden by default.
  Improved references between CPQ Custom Rules and their conditions.

Zendesk adapter

• Users can now authenticate to Zendesk with username and API Token

Okta_adapter:

• Bug fix for deployment of priority of MultifactorEnrollmentPolicyRule
• Fix bug in pagination for User type
• Active Application instances can now be removed and do not require manual deactivation first.
• Improve fetch time when including group memberships

Jamf adapter

• support mac_application fetch and deploy
• fix deploying references of site and category
• Support deployment of scripts list on policy instance

Microsoft Entra:

• Expand user-facing errors to include more informative messages when requests fail.

Expected changes to existing workspaces

Jamf adapter

• support mac_application fetch and deploy
• fix deploying references of site and category
• Support deployment of scripts list on policy instance

Jira adapter

• for DC users the order of post functions in workflow will change
• prevent deploying portal groups with a non-unique name field

Salesforce adapter

• Nearly all types will get meta types when the optional feature is enabled. This will lead to a change on the whole type which will remove the annotations definitions.
• Existing MutingPermissionSet instances will have their structure changed.
• Existing QuickAction instances may have changes from strings to References.
• Existing workspaces will have major changes to their existing nacls.

Salto v0.3.60

Salto Version 0.3.60

New features and bug fixes

Core

• Added the ability to override definitions with the DEFINITION_OVERRIDES env var

NetSuite adapter

• Fix FileCabinet fetchTarget and remove folders correctly before querying files
• Fix "unresolved reference" error in SDF deploy

Jira adapter

• Fixed a bug in cascading options when working with the new beta
• Fixed a potential circular dependency when deploying a JSM project
• Might improve the fetch, by making earlier Atlassian API calls async

Salesforce adapter

• Bugfix: Salesforce CustomMetadata Records deploy fail when attempting to delete field values
• Fixed a bug where Custom Events were misidentified as Standard Objects and could not be deployed.
• retry on some more kinds of errors
• Fixed a bug where we didn't include the correct dependencies for the provided fetch targets.
• Fixed an issue when we created FLS CV message on added fields of CustomMetadata types, in case their object was added.
• Fixed a bug where elements in a successful deployment got an error with the message: Element was not deployed because other elements had errors and the 'rollbackOnError' option is enabled (or not set).

Zendesk adapter

• Add validation for duplicate case insensitive dynamic content item names
• Add validation for duplicate dynamic content item placeholders
• Fix fetch content of article attachments content

Confluence adapter

• new ability to manage pages only for specific spaces (these space can be defined under fetch configuration in the adapter config)
• Support displayName on group and user references

Jamf adapter

• Omit selfServiceIcon on policy instance upon fetch
• Change validate credential url to one that we support
• Add support in site deployment
• Fix api-role deployment
• Support deploying Additions of Custom QuoteTerms and Conditions when SBQQ triggers are enabled.

Expected changes to existing workspaces

Jamf adapter

• Omit selfServiceIcon on policy instance upon fetch
• Change validate credential url to one that we support
• Add support in site deployment
• Fix api-role deployment

Confluence adapter

• new ability to manage pages only for specific spaces (these space can be defined under fetch configuration in the adapter config)
• Support displayName on group and user references

Salto v0.3.59

Salto Version 0.3.59

New features and bug fixes

Core

• Element members (field, annotations or values) are added in the same location consistently instead of being appended
• Add ability to filter out elements while fetching in the new infra
• Added support for type <name> is object type definition syntax
• Fix issue where plan would go into infinite loop on specific cases of circular dependencies
• Ignore conflicts caused by different line separators
• Fixed a bug where custom references did not recalculate on outdated reference indexes

Workspace

• getElementOutgoingReferences will now additionally return the sourceScope for each reference.
• Implemented getElementIncomingReferenceInfos that returns additional information on the incoming reference (The reference type and the sourceType)

NetSuite adapter

• Add missing data instances reference names
• Replace recordRefList field type with List<netsuite.recordRef> field type
• Resolve ASV references of the taxSchedule field
• Keep elemID of data elements when identifier is renamed
• Fix custom record types quick fetch
• Fix deployment of custom records that contains fields of type Date/Time
• Remove unresolved NetSuite references in forms for a smooth deployment
• Fetch and Deploy Custom Record instances of locked Custom Record Types (use adapter config fetch.addLockedCustomRecordTypes=true)
• Fix MAX_STRING_LENGTH error while extracting references in SuiteScripts
• Fix SuiteQL query of over 100K items
• Improve FileCabinet files query by excluding excluded file extensions
• Fix merge error on custom record type addition in the apply-patch flow
• Query referenced ASV only
• Upgrade SDF version to 1.9.0-salto-2 so it'll be based on 2024.1 API version

Jira adapter

• Resolved an issue where the application could encounter an 'undefined' error due to an empty categories array in the queue categories response
• Fixed a bug where Object Schemas, Queues, and Request Types would bring partial results for big environments
• Fix handling of requestType field and trigger components in automations to support various formats and proper processing
• Improved the fetch performance for JSM
• Added support for global objectSchema statuses
• Update the counting of the options in field-context
• Add alias to Priority
• Fixed warnings on requestType field in Automation
• Added retry on 502 errors on automations
• Prevent deployment of workflows with transition rules that are dependent on missing Jira apps. This is only for the new version of Workflows by Jira (enabled by the enableNewWorkflowAPI flag)
• Added a feature flag under config.deploy called ignoreMissingExtensions (defaults to false). When enabled, workflow transition rules of Jira apps that aren't installed in the target environment will be removed
• Added a configuration for automation page size
• Omission of ruleHome and schemaVersion fields in Automations
• Improved the change validator message for invalid issue layouts
• Deployment of object types will not cause circular dependency
• Fixed a bug that caused fetches to fail when an Issue Type Screen Scheme has no Issue Type Mappings or when the fetch did not include an Issue Type Screen Scheme of a project

Salesforce adapter

• Will now validate custom fields' Data Owner property
• Using strong custom references for managed elements
• CPQ Billing - automatically-generated fields in the 'RevenueRecognitionTreatment' and 'FinancePeriod' will no longer be fetched
• Circular dependency between CPQ ProductRule instances with 'Custom' ConditionsMet value and ErrorCondition instances are handled correctly
• All 'Unique ID' fields of CPQ Billing objects are now discarded
• Salesforce Profiles custom references will be available by default
• Will now show an error when attempting to deploy CPQ Billing records with StartDateTime in the past
• will no longer show an error when using changed-based fetch to fetch records that refer to unchanged records
• Add the ability to always regenerate salto Ids for Salesforce Data Instances by setting data.regenerateSaltoIds to true
• Fixed bug in Salesforce profiles element fixer which caused all field permissions to be dropped

Okta adapter

• Added deploy support for Domain instances
• Fixed the deployment issue for default access policy rules by ensuring the priority is set correctly to 99
• Fix a bug causing ApplicationGroupAssignment instances not to be nested under the parent application in the files tree
• Fix a bug causing fetch to hit the account's rate limit
• Fixed a bug in deployment of several policies and policyRules so we can deploy them
• Fixed missing reference bug in ObjectTypeAttribute in the additionalValue field
• Support additions of app user schema
• Fix a bug in fetch causing all fetch to include invalid config event
• Add support in fetching users in Okta. The type is excluded by default
• Fix a bug in deployment of OIDC application causing applications with empty scopes to fail
• Support users deployments

Zendesk adapter

• Add references to user segment ids in article
• Order workspace macro_ids and selected_macros
• Fix sorting for agent conditions in ticket forms, to eliminate order diffs between envs
• Fix deployment of articles

Confluence adapter

• Fix fetch for large amount of pages
• Fix pagination on types supported by Confluence old API
• Fix homepage deployment
• Support displayName on group and user references

Microsoft Entra adapter

• Basic fetch + partial deploy is ready to use

PagerDuty adapter

• Basic fetch + partial deploy is ready to use

Jamf adapter

• Basic fetch + partial deploy is ready to use

Dummy adapter

• Add configCreator with various options for testing purposes. The input won't affect the created config

Expected changes to existing workspaces

NetSuite adapter

• The value of restrictToAccountingBookList in account instances will have the correct reference names, instead of "unknown object"
• RecordRefList field type will be replaced with List<netsuite.recordRef> field type, in types and instances
• ASV references of the taxSchedule field will change the type in them: from object to taxSchedule
• In data types, the internalId field will be the serviceid field, instead of another field that was the serviceid
• When enabled in adapter config (fetch.addLockedCustomRecordTypes=true), custom records of locked custom record types will be fetched and added /CustomRecords/<lock_custom_record_type_scriptid>
• For existing Salto Workspaces, you should reinstall the NetSuite account 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, for existing Salto Workspaces, you should delete the ~/.suitecloud-sdk/credentials file.

Okta adapter

• ApplicationGroupAssignment element files will be nested under the parent application
• Users might encounter changes in the additionalValue field within the ObjectTypeAttribute instances, changing from a missing reference to an actual reference

Salesforce adapter

• All 'Unique ID' fields of CPQ Billing objects will be removed from the workspace