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