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

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