Salto v0.3.58

Salto Version v0.3.58

New features and bug fixes

Core

• Fix issue where pending changes appear in multi-line string when the unicode U+200D is the last character.

NetSuite adapter

• Adding missing permissions to roles and custom record types. This allows deploying roles and custom record types with cross referencing permissions.

Jira adapter

• When attempting to delete a workflow referenced by a workflow scheme (whether active or inactive) an error will be emitted. Note, this works only when using the new Workflow API.
• Fixed fetch error for missing issueTypeIcon.
• Added support for conditionGroups in Workflow v2 API.
• Added a change validator to prevent issue layout deployments that will fail.
• Added logs to better understand rate limits.
• Optimized error logging for JSM form fetching to reduce noise: now logging a single error per account for project-wide fetch failures and a unified error for all forms with missing titles.
• Added a retry when automation rules fetchs fail with 504.
• Fixed a JSM Forms bug where users without forms received a permission error.
• Added a reference from WorkflowConfiguration (new Workflow API) action to Resolution and Priority.
• Added a dependency changer for issueLayouts.

Okta adapter

• Fixed a bug which caused the file path of the default access policy to change on the second fetch.
• Changed important value for groups from "source" to "source.id".
• Added support for addition and removal of BrandTheme.
• Users can now remove appUserSchema along with removing the parent application.

Salesforce adapter

• References from custom object instances will now be resolved correctly in partial fetch.
• Use custom (weak) references for installed packages.
• Added the feature omitStandardFieldsNonDeployableValues that omits non deployable values from standard Picklist fields. These changes will fix misalignments between envs and some deploy issues (e.g. duplicate refTo when attempting to deploy valid changes to Standard Picklist Fields).
• Use custom (weak) references for permission sets.

Google Workspace adapter

• Added a new elements fixer for groups which changes the group domain to match the current env.

Zendesk adapter

• Two app installations with the same position in a workspace will retain their set position.
• Content in dynamic content item variants is no longer an indexed important value.
• Make sorting of conditions in Ticket Forms more consistent.
• Fix a bug with fetching some article attachments with complex names.
• Added support for deploying Zendesk Guide Themes.

Confluence adapter

• Added a change validator for uniqueness of page titles under a space.
• Added a change validator for uniqueness of space keys.
• Added support for deployment of custom space settings.

Expected changes to existing workspaces

NetSuite adapter

• On the next fetch, permissions may be added to some roles and custom record type.

Salesforce adapter

• The explicit references to the InstalledPackage will be removed from the _generated_dependencies annotations for all managed elements.
• The valueSet and referenceTo annotation will be removed from all Standard Picklist Fields.
• All references will be removed from permission sets.

Salto v0.3.57

New features and bug fixes

Core:

• Solves the bug that inserts empty lines into NaCl files when elements are removed.
• Modified the deletion for s3 dir store.

Jira Adapter:

• Stop fetching requestsType that has no requestForm or issueView.
• The fields 'workspaceId', 'schemaLabel', 'objectTypeLabel', 'serviceDesk' are going to be removed from all sub-components.
• The bug where deploy fails when a user has enableJSM = true but no JSM in the service is solved.
• Fixed an issue that caused some users to fail fetch in the issue layouts filter
• Fixed a bug that caused failed fetches for some customers due to changes in issue layouts filter

Salesforce Adapter:

• Adds a new elements fixer that removes broken references from profiles. Disabled by default.
• Fixed a bug where attempting to deploy modifications to a Profile with loginFlows failed.

Zendesk Adapter:

• Fix issues on deploy of some values containing reference expressions
• Allow adding dynamic content items whose placeholders and titles are different
• Reorder values in routing attribute

NetSuite Adapter:

• SDF Loader shouldn't set attributes from the existing instance

Confluence Adapter:

• Add aliases
• Sort permissions on spaces
• Support deployment of space with its homepage
• Fully support restrictions on page deployment
• Support linking templates to existing labels
• Fix deployment of templates inside spaces
• Add support for deploying page restrictions

Okta Adapter:

• New instances responsible for policies priorities were added.

Expected changes to existing workspaces

Jira Adapter:

• Stop fetching requestsType that has no requestForm or issueView
• The fields 'workspaceId', 'schemaLabel', 'objectTypeLabel', 'serviceDesk' are going to be removed from all sub-components.

Confluence Adapter:

• Add aliases
• Sort permissions on spaces
• Support deployment of space with its homepage
• Fully support restrictions on page deployment

Okta Adapter:

• New instances responsible for policies priorities were added.

Zendesk Adapter:

• Reorder values in routing attribute

Salto v0.3.56

New features and bug fixes

Core

• Added support for deletion in S3 dir store

Salesforce Adapter:

• Added a new change validator which checks for flows with an unsupported API version

Zendesk Adapter:

• Active apps inside workspace will now be ordered by position

Jira Adapter:

• Added change validator for maximum description length of a FieldConfiguration, limiting to a maximum of 255 characters
• Added change validator for maximum description length of a FieldConfiguration item, limiting to a maximum of 1000 characters
• Fixed a bug that prevented fetching some of the issue layouts
• Added important values
• Fixed a bug in automation that could cause fetch to fail
• Fixed bug by adding references from objectTypeAttribute to statuses, objectSchemaStatuses and groups
• Improved the duplicate id Warning messages text
• objectTypes will have no field called objectCount

Okta Adapter

• Fixed bug in signOn policy rule
• Brand subtypes (BrandTheme, BrandLogo, FavIcon) NaCl files are now nested under their respective Brand
• New instances responsible for policy rules priorities were added
• Fix issue that would cause false pending changes to remain after deploy
• Deleting active NetworkZone is no longer allowed, Salto will now deactivate NetworkZone when trying to delete it

Confluence Adapter:

• Change structure of permissions objects array (on space instance)
• Support deployment of space permissions
• Improve folder structure for pages
• Templates body will be template expression to support references inside the body
• Throw original error when trying to modify page with illegal version number

Google Workspace Adapter:

• Improve folder structure for org units

Intercom adapter:

• First version (public API + read only) is ready to use

Expected changes to existing workspaces

Confluence Adapter:

• Changed structure of permissions objects array (on space instance)
• Changed folder structure for pages
• Templates body will change to template expression

Google Workspace Adapter:

• Change folder structure for org units

Jira Adapter:

• InobjectTypeAttribute the field TypeValueMulti changed from string to referenceExpression
• objectTypes will have no field called objectCount

Okta Adapter:

• Brand subtypes (BrandTheme, BrandLogo, FavIcon) NaCl files are now nested under their respective Brand
• New instances responsible for policy rules priorities will be added

Salto v0.3.55

Salto Version v0.3.55

New features and bug fixes

Core

• Stop creating additionalProperties field upon fetch
• Save reference to a type in additional_properties annotation
• Keep additional properties annotation from swagger and stop creating a field additionalProperties
• addAlias function is no longer supports secondInterationsTypes parameter, instead it builds a dependencies graph

Salesforce adapter:

• Retrying SFDC requests on "security policies took too long to evaluate".
• Retrying SFDC requests on disconnect/reset before headers.
• Do not suggest to exclude types with many instances that are under allowReferenceTo.
• Automatically retrying requests which fail with a 406 status. We are seeing these errors in the wild and they are always resolved by retrying.
• Fetch with delta now works for data records of types listed in allowReferenceTo
• Support for Go To Service for Auto Response Rules elements.
• Better handling of internal Salesforce errors.
• The Translations type is now excluded from fetches in new workspaces.
• Add Change Validator that forbids changes on fields of Task and Event.
• DiscoveryAIModel metadata type is excluded in new workspaces
• Implemented a Change Validator that notifies users that the adapter will enable the FLS to certain Profiles on addition of new CustomField or CustomObject

NetSuite adapter:

• Fixed change validator messages that wrongly contained element names
• Fix elements will now remove permissions with unresolved references
• Do not classify testing accounts as production

Zendesk adapter:

• Add reference to skills in trigger actions
• Stop showing Article Label ordering in deployment changesets
• Add a new validator that emits errors when custom statuses are disabled for the account but used in view conditions.
• Enable deployment of __NULL__ as user
• Add validation that an automation order isn't empty.
• Enable modification of default_locale in articles, categories and sections in the Zendesk guide
• Fix bug where non-"Dynamic content item" strings were being parsed as dynamic content and creating broken references
• Added a config flag which allows omitting the Ticket_status_custom_status ticket field from Ticket Forms on fetch
• Fixed a bug where there were duplicate usernames from instance fields

Okta adapter:

• When deploying Device Assurance Policies with dynamic OS constraints, verify the dynamic OS feature is enabled in the target account
• Allow filtering instances using fetch criteria by type, status, and group names. For example, to exclude all inactive apps, use:

  okta = {
    fetch = {
      ...
      exclude = [
        {
          type = "Application"
          criteria = {
            status = "INACTIVE"
          }
        }
      ]
    }
  }
  

• Add the option to deploy group membership changes for existing users. To enable this feature, add fetch.includeGroupMemberships to your adapter configuration file
• Fix an issue with deployment of default authentication policies in certain cases. To resolve, run next fetch with regenerate elemIDs
• Added support for addition and removal of Brand elements
• Fix bug in deployment of Access Policy Rules with required field set
• In new environments, ProfileMapping properties object will not be fetch by default, and can be included by turning includeProfileMappingProperties flag to true. Existing envs will not be affected.
• ProfileMapping now supports removal action in deployment.

Confluence adapter:

• First version is ready to use

Google Workspace adapter:

• First version is ready to use

Jira adapter:

• Add assets component in Automation.
• Now support fetching and deploying issue type icons.
• Fixed duplication error that arose from a bad response for Calendar instances.
• Now support fetch and deploy of objectType icons.
• Fixed error throwing in gqlPost for requestForm.
• ObjectSchemaDefaultReferenceType can be deployed.
• Team-managed boards will not be fetched
• Team-managed projects will not be deployable
• Fixed a bug that caused a validation error when changing the deploy config fields: taskMaxRetries and taskRetryDelay
• Fixed a bug that could cause partial success for deployments

Expected changes to existing workspaces

Jira adapter:

• For automation nacls: serviceDesk field will be removed and requestType field will be converted from string to reference expression.
• Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Notification Events, Workflows and maybe more)
• Users will see new fields in their issueType nacls named avatar.
• New nacls of type ObjectTypeIcon will appear in the users next fetch.
• Forms nacls portalRequestTypeIds field will be changed from numbers to reference expression.
• Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Notification Events, Workflows and maybe more)
• objectSchema nacls will have new field called properties
• Team-managed boards will be removed from users' environments

Okta Adapter:

• Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Users, GroupRule, PasswordPolicyRule and maybe more)
• The members list in GroupMembership instances will be sorted
• When running fetch with regenerate elemIDs, elemID for the default access policy will change
• Instances with additionalProperties map field will be flatten upon fetch (types to be affected: Users, GroupRule, PasswordPolicyRule and maybe more)

Zuora billing Adapter:

• Instances with additionalProperties map field will be flatten upon fetch

Stripe Adapter:

• Instances with additionalProperties map field will be flatten upon fetch

Salto v0.3.54

Salto Version 0.3.54

New features and bug fixes

Core:

• Dependencies of change groups that have low-severity errors will now be deployed
• Created DetailedChangeWithBaseChange and return it in PlanItem & FetchChange

Adapter Utils:

• Changed transformValues function, so if a value doesn't have a corresponding field in the provided type, we will try to get a type from _additional_properties annotation

Workspace:

• Moved parser to a different package

Jira Adapter:

• Added at least an empty type for any deployable instance
• Fixed a bug when deploying a ducktype instance for the first time, the target environment lacks the corresponding type
• Added flag called enableJsmPremium that replaces enableJsmExperimental
• Omitted Id fields in SLA subTypes.
• Changed SLA so whenever there are subgoals fields - the calendar field will change from id to referenceExpression
• Fixed a bug that occurred when attempting to delete a root objectType and its corresponding objectSchema
• Fixed circular dependency error between objectTypeAttribute and objectType.
• Changed folder structure to:

  ....|** attributes (folder)
  ....|** childObjectType1 (folder)
  ....|** childObjectType2 (folder)
  ....|** objectType1.nacl
  ....|\_\_objectType1_childOrder.nacl
  

• Added aliases to Jira Statuses based on the instance name
• Fixed bug in default attribute CV.
• Fixed issue with fetches that includes ScriptRunner, will end with a fetch error on a fetch error. Also, in case the reason is the ScriptRunner's Survey, the user will be provided with the relevant instructions
• Imporoved fetch performance for issue layouts
• Fixed bug when project instance is undefined
• Fixed an issue with jsmPermissionsValidator
• Fixed automationToAssetsValidator validator in jira to warn when customer doesn't have assets support

NetSuite Adapter:

• Utilize NS concurrency limit by having fairness between the inner concurrency limiters
• Fix fetching file cabinet elements with fetchTarget
• Added excludeBundles config, All elements from listed bundles Ids will be excluded.
• Changed the default behavior of fetching the SuiteQL tables for ASV resolving
• Run SuiteQL queries concurrently
• Limit SuiteQL tables query to 100K records
• Added config suggestion on skipping SuiteQL tables
• Added config option to SuiteQL queries limitation: suiteAppClient.maxRecordsPerSuiteQLTable
• Added generic ASV warning to workflows
• Remove important values from Settings types
• Bundle field in elements will be added as an important value
• Enabled the "fetch bundles" and "resolve account specific values" features by default
• Aligned inactive fields
• Resolve account specific values in data elements in fetch & deploy (behind fetch.resolveAccountSpecificValue)
• Add fetch.skipResolvingAccountSpecificValuesToTypes config to skip some SuiteQL table queries, in case that they take too much time.
• bundle elements will be renamed from <bundleId> to bundle_<bundleId>
• Fix undefined internalIdsMap bug in workflow ASV resolving
• Added more account specific values resolving in workflows
• Increased global concurrency limit in NS APIs

Okta Adapter:

• Moved Application group assignments to their own instance.
• Moved GroupPush and GroupPushRule types to be nested under the parent Application type in the element tree
• Moved AppLogo and AppUserSchema types to be nested under Application type in the element tree

Salesforce Adapter:

• Changed the adatper to use API Version 60.
• Show info/warning messages from successfully deployed components
• Added warning when attempting to deploy undeployable types
• Added warning when attempting to modify the list of supported currencies
• Added the ability to configure which Profiles should have visibility to newly created CustomObjects and CustomFields.
• Added warning when attempting to add instances without their types
• Added important values to Salesforce Metadata Types.
• Fixed deploy of new CPQ PriceRule records with 'Custom' ConditionMet value that reference new PriceCondition records
• Fixed types to be deployed before their data records were needed
• Fixed an edge case in Data Deploy where we didn't pass mandatory fields for update operation in case
  of Data Deploy Group with references within the same group.
• Improved mapping of deploy errors to elements
• Added Deploy Warning when attempting to deploy Data Instance with fields that do not exist on the CustomObject type.
• Changed deploying data instances with fields that are not creatable (for addition) or updateable (for modification) by the fetching user, so the fields will now be deleted from the workspace and a warning will be issued
• Fixed Quick Metadata Deploy.

Zendesk Adapter:

• Fixed idFields mechanism for newly created fields
• Removed custom headers from zendesk webhook after deployment
• Fixed a bug where '==' was caught as part of a reference name
• Added support for deploy of locales
• Fixed race condition when creating new variants for a dynamic_content_item
• Changed deploy to fail when Zendesk returns errors when changing workspaces
• Stopped missing references from being created for tags
• Fixed bug of getting Service error while removing trigger_category and changing trigger to be depend on other category simultaneously
• Fixed references to organizations starting with non alphanumeric characters, e.g. ⭐⭐ My Org ⭐⭐
• Fixed fetch of attachments with non english characters
• Fixed deploy when changing User Segment in Article to Everyone
• Fixed raw_title deployment issue and hide the title field in views
• Added CV for User Field in order to prevent deploying changes to type and key fields
• Added Change Validator error instead of crashing when a locale is unresolved while checking for translations
• Changed Workspace fields to have MissingRefs instead of dangling IDs
• Prevenet deploying a change to a view that has a condition with a reference to a deactivated ticket form
• Removed the outdated field in the Dynamic Content Item and Dynamic Content Item Variant types.
• Prevent removal of groups where one of the group's members has it set as default.

User Notifications

Jira Adapter:

• Added a new flag called enableJsmPremium that replaces enableJsmExperimental
• In SLA, whenever there are subgoals fields - The calendar field will change from id to referenceExpression.
• New Folder structure:

  ....|** attributes (folder)
  ....|** childObjectType1 (folder)
  ....|** childObjectType2 (folder)
  ....|** objectType1.nacl
  ....|\_\_objectType1_childOrder.nacl
  

• New empty objectTypes will be added
• Fixed an issue with the elemId of trusted-users group in Jira. If the elemId for the trusted-users group contains uuid, fetch with regenerate salto ids to resolve the issue.

Okta Adapter:

• Application group assignment configurations will no longer be part of Application instances, and will have their own instances.
• On the next fetch, GroupPush and GroupPushRule types will now be nested under the parent Application type in the element tree
• Changed the file name of the app logo to be in camelCase format instead of nacl case format.
• The value of appLogo will change. The fields 'fileName' and 'content' will be updated.

NetSuite Adapter:

• The _important_values annotation will be removed from the companyInformation type
• Added Bundles help article to CV
• Added ASV help article link to CVs
• bundle instances will be fetched
• bundle field will be added to instances that are part of a bundle
• ACCOUNT_SPECIFIC_VALUE will be resolved in workflows & data elements, on fetch & deploy
• All isinactive/inactive fields will be replaced with "isInactive" field - in types, instances, and important values
• In case that fetch.resolveAccountSpecificValue is true in the adapter config, ACCOUNT_SPECIFIC_VALUE values will be resolved to the form of [ACCOUNT_SPECIFIC_VALUE] (<type>) (<name>)
• Field values that are of the type custom_status_#### will be converted to references to the relevant custom status.

Salesforce Adapter:

• Upon your next fetch, expect changes to existing Metadata Types nacls.
• API upgrade to version 60, expect to see many changes to types in existing Workspaces

Zendesk Adapter:

• title field in views is now hidden
• Add check in Article Attachment CV to prevent throws when content is not a static file
• Remove the outdated field in the Dynamic Content Item and Dynamic Content Item Variant types.

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 under fetch -> 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 from ticket_field_ids list in ticket_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 and favourite 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 the CustomFields 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 and favourite 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 each CustomField.
• You may encounter changes in Metadata Elements _extra_dependencies.

Salto v0.3.52

Salto Version 0.3.52

New features and bug fixes

Zendesk Adapter

• Handle socket hang up errors. added the flag unassociatedAttachmentChunkSize under client to control the size of the chunks.
• Add default timeout for requests.

Jira Adapter:

• Now support deploy of order of assetsObjectTypes.
• Projects path are going to be changed to Projects -> {projects Type} ->...
• Added a fetch warning when form is untitled.

Netsuite Adapter:

• Add workflow condition warning when there are parameters with ACCOUNT_SPECIFIC_VALUES.

Salesforce Adapter:

• Data Deploy Errors will be linked to the failed Elements.
• Fixed a bug where we failed to resolve some internal ids of managed Elements.
• Salesforce partial fetch will now support deletions.
• Fixed a bug where data deploy group errors were falsely masked.

Okta Adapter:

• Validation error when user tries to add group push with groupId and application relation that already exists in the target environment.

Core:

• Change the missing dependency error to include a link to a "learn more" page.
• Added support for storing state static files in S3.

User Notifications

Jira Adapter:

• Projects path are going to be changed to Projects -> {projects Type} ->...

Salto v0.3.51

Salto Version 0.3.51

New features and bug fixes

Zendesk Adapter

• Remove merge errors on collision of elemIds
• Allow fetch without converting user Ids, either by configuration of resolveUserIDs = false in the adapter nacl, or if the users query is forbidden
• Inactive instances will be omitted by default

Jira Adapter:

• Support deployment of Asset Schema
• Support deployment of Asset Object Type
• Fix bug in deployment of Issue layout
• Change Forms elemId
• Automation elemIds can now be configured by the user
• Board type is now excluded when interfacing with the Jira Service Desk (JSM) server.
• Fix an issue with maps in Form type
• Notfiy user when trying to deploy a JSM linked Automation and JSM is not enabled in the adapter config
• Add validator to verify Board have at least one column before deployment
• Resolve bug in deployment of NotificationScheme type
• Allow fetching untitled Form
• Support deployment of Assets Attributes

Netsuite Adapter:

• Change default excluding in the adapter config
• Add important values (with adapter config addImportantValues=true)

Salesforce Adapter:

• Improved the coverage of resolving extra dependencies between Metadata components. This is a beta feature that requires the optional feature extraDependenciesV2

Core:

• New optional argument to loadWorkspace with ignoreFileChange. Using this parameter can lead to unexpected behavior if there was a NaCl change in the workspace. Use this only if you're sure there was no NaCl file update in the workspace.
• Fixed issue where loadWorkspace would have degraded performance when static file modification times changed

CLI:

• Added the option to store state file content in S3 instead of storing it locally, see command salto workspace set-state-provider

User Notifications

Jira Adapter:

• To change the current elemId for Form, perform a fetch with --regenerate-salto-ids flag. This will change the forms elemId, which may cause some disruptions
• Changes in Form structure

Zendesk Adapter:

• Inactive instances will be omitted

Salesforce Adapter:

• Using the beta feature extraDependenciesV2, may result in _extra_dependencies changes on existing NaCls.

Netsuite_Adapter:

• The _important_values annotation will be added to all types (custom record types will also have _self_important_values)

Salto v0.3.50

Salto Version 0.3.50

New features and bug fixes

Zendesk Adapter

• Move the replacement of fallback user emails also for custom object fields to happen before the deploy in order to reduce incorrect user errors (partial successes).
• Avoid crashing when resolving an article_body template expression with an unresolved reference
• Move the replacement of fallback user emails to happen before the deploy in order to reduce incorrect user errors (partial successes).

Jira Adapter:

• Now supporting metadata of fields in issueLayout, issueView and requestForm.
• Now support fetch of assets object types.
• Now supporting fetch of assets attributes.

Salesforce Adapter:

• improved validation of saltoManagementSettings configuration
• Lookup fields in records of custom objects that reference instances of metadata types are now handled correctly.
• Add deploy support in CPQ Custom Approval Rule and Conditions for accounts that use the old Salto ID Settings (non Id based).

Core:

• Removed code that would migrate very old state files to the "new" format - this would only affect workspaces that were not used for over 10 months

User Notifications

Jira adapter:

• Under issueLayout, issueView and requestForm, there will be more fields upon your next fetch.

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
         }
      },
    ]
  }
}