Salto v0.3.53
Salto Version 0.3.53
New features and bug fixes
Zendesk Adapter
- Add deploy support for Guide Themes.
- Add Zendesk Guide Themes for fetch only, opt in by adding the brands to fetch the themes for in the config flag
themesForBrands
underfetch -> guide
. So your config under guide might look like this{ fetch: { guide: { brands: ['.*'], themesForBrands: ['.*'] } } }
. This allows users to differentiate between regular guide elements and the guide themes to fetch. - Fix deployment error when modifying and adding an attachment to the same translation.
- Changed custom_object_field_option to use nacl case.
- Fixed a bug where the removal of a missing
ticket_field
by editing fromticket_field_ids
list inticket_form
would fail the deploy
Jira Adapter:
- The JQL for queues will no longer include an unnecessary 'project = ' at the beginning.
- For automation with component from type "hasAttachment", its boolean value will be store in "hasAttachmentsValue" field.
- When trying to deploy with invalid credentials, user will get unauthorized error.
- Fix workspace error after fetch on automation instance that has component with type "jira.issue.delete.link".
- Fix OOM issue on big fieldConfiguration by removing field references from nacl.
- Add new instance element that holds for each objectType who its label attribute.
- Add new Change Validator that prevents deletion of assets label attribute.
- Add CRUD Support for Jira Workflows.
- Support deploy of first JSM project.
- Now columns in queues will be weak references.
- Added a Change Validator that prevents addition of JSM project when JSM is disabled in the service.
- Modify jql in queue to not include undesired Project template expression.
- Fixed a bug when trying to remove Project with IssueLayout
- Basic CRUD support for Assets in Automations.
- Fix bug of deployment partial success when missing fields where removed because they do not exist in the target env.
- The 'Board' type is now excluded when interfacing with no jira software projects.
- Add Alias on JSM Instances.
- Add
Go To Service
support for JSM Types. - Queues Instances will have two new field -
canBeHidden
that sets the team priority andfavourite
that sets the star character.
Netsuite Adapter:
- Add Netsuite Simple Configuration.
- Important Values feature is enabled by default.
- Fix custom record types with segments partial fetch
- Netsuite too many instances type exclusion description will now contain the type name.
- Fix item types limiter exclusion.
- Upgrade SDF version to 1.8.0-salto-1 so it'll be based on 2023.2 API version.
- Fix custom record type fields type in NS loadElementsFromFolder (apply-patch)
- Add support in Analytics (Workbooks and Datasets). For the limitations and capabilities refer to: #4892
Salesforce Adapter:
- Improved mapping of Metadata Deploy Errors.
- Add Salesforce Post Deploy Retrieve Zip Artifact for metadata deploys with the option
performRetrieve
enabled. - Added the optional feature
extraCustomFieldInformation
that extends the annotations of theCustomFields
when enabled. - Improved Salesforce Deploy Group Names.
- Add Change Validator on data instances values of unknown fields.
- Fixed a bug where MetadataRelationship CustomFields with controlling field couldn't be deployed.
- Will now be more explicit about metadata types that did not deploy because they were in a deploy group along with types that failed to deploy because of an error.
- If no explicit configuration is provided, Salto will now use exponential backoff when retrying deployment of custom object instances.
- The improved implementation of the
Tooling Extra Dependencies
is enabled by default. This will improve IA of Metadata Components.
Okta Adapter:
- Add the ability to setup a reminder to change tenant specific values (such as URLs or subdomains) when deploying applications. To use it, enable the feature
appUrls
in your validators config. - Add the option to omit users from elements when users are missing from the target environement.
- Accounts with Okta Classic Engine will no longer get warnings when fetching Okta Identity Engine types fails.
- Add config option to enable fetching only users referenced by other elements. This will be enabled by default and is more efficient for bigger accounts.
- Add Change Validator to verify app groups assignments are not modified in inactive apps
Core:
- Fix merge error on field type change in apply patch/
- Improved performance for calculating plan / env diff when the diff is filtered
- Added the optional capability to write deploy artifacts.
User Notifications
Jira:
- The JQL for queues will no longer include an unnecessary 'project = ' at the beginning.
- Automation with component from type "hasAttachment", will have a new field named "hasAttachmentsValue" that will contain the boolean value
- linkTypes field inside a component from type "jira.issue.delete.link", will be rename to "deleteLinkTypes"
- Fix reading system from undefined when deploying RequestTypeLayout
- the properties of requestForm instances will be a list in which each entry will contain key and value.
- Add new instance element that holds for each objectType who its label attribute.
projectId
field will be removed from IssueLayout instances- Queues nacls will have two new field -
canBeHidden
that sets the team priority andfavourite
that sets the star character.
Okta:
- In AccessPolicy, ProfileEnrollment Policy and IDP policy instances, 'priority' field will be omitted.
- In password policy rules with more then one method used for password reset, the list of methods will be sorted.
Netsuite:
- The
_important_values
will be added to all types, and the_self_important_values
will be added to all custom record types. - 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.
Salesforce:
- When enabling the feature
extraCustomFieldInformation
, expect to see new values on eachCustomField
. - You may encounter changes in Metadata Elements
_extra_dependencies
.