Skip to content

Salto v0.3.54
Compare
Choose a tag to compare
@saltoio saltoio released this 10 Mar 13:36
· 1374 commits to main since this release
v0.3.54
2973ba7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

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.
Assets 6
Loading