Gitana Releases

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.88 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-88.html

With this upgrade:

• MongoDB 4.0 or above is required
• You will need to perform a cold restart of your API cluster.

Enhancements

Auto Translation

• The f:auto-translate feature now processes auto-created translated nodes using background asynchronous tasks, allowing the on-request operation to complete more quickly while translations are fetched, populated and automatically created in the background.

Database Guardian

• Added database guardian thread that automatically monitors analyzed queries to detect inefficient queries and hotspots.
• Automatic optimization of slow query hotspots on a per repository/branch basis.
• Automatic circuit breaking and quarantining of client / API keys that induce overload of DB usage due to inefficient queries – resulting in higher net performance of the system by guarding against overallocated DB connections and cursors.

Events

• Faster event handling for associated nodes and associated node attachments.

Find

• Faster and more accurate implementations for node find operations that act as a composite of layered calls into Elastic Search, the path index and MongoDB.

Index Auto-Optimizer

• Default maximum for composite key size has been raised to 10.
• Improved analysis of existing indexes that now takes into account bad locator strings while rebuilding candidate indexes.

Query Optimization

• Incoming queries are run through an optimizer ahead of passing through to the underlying database, allowing for optimization of the query structure to best accomodate the underlying facilities and strengths of MongoDB and the DSL.

Single Sign On

• Added the ability to enable/disable the requirements for SAML 2.0 assertions and response to be signed. In the SAML 2.0 specification, both assertions and the overall response payload are specified to be digitally signed. However, some custom SAML 2.0 implementations by customers do not this. As such, we’ve added these configuration options to support customer migration with the understanding that customers will implement this in due course.

Third-Party Libraries

• Upgrades to third-party lirbaries adn dependencies to address critical-level common vulnerabilities and exposures.

User Interface

• Faster rendering and performance throughout the UI and the Alpaca forms engine.
• Faster modals, pickers and popups.

Bug Fixes

Associations

• Fix so that committing nodes have their association source and target verified ahead of commit. This was done previously but failed for some cases. The new implementation is robust and certain to validate.

Command Line Client

• Fix so that the upgrade command provides better error handling.

Inline Links

• Fix so that inline links parser handles unresolved references gracefully.
• Fix so that inline links parser handles more syntatic references (such as mailto:) while parsing HTML.

Merge Results

• Several fixes to ensure that internal merge result cursors are properly closed at runtime to prevent potential memory leaks.

Mongo Lock Provider

• The MongoDB lock provider now uses the same configuration settings as the general MongoDB facility.

Transfer

• Fix so that very large exports work as intended by reducing heap overhead.

User Interface

• Fix so that pickers gracefully handle null data for min/max items validation.
• Fix so that the Tagged Documents page properly apply pagination information while browsing.
• Fix so that Content Items and Documents pages utilize the faster and more efficient find API.
• Fix so that Analyzed Queries list page truncates JSON blocks after 1024 characters for improved display.
• Fix so that Dataloaders consistently apply Chain() to retrieved objects ahead of render.
• Fix so that the table Alpaca field element renders consistently as intended.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.87 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-87.html

With this upgrade:

• MongoDB 4.0 or above is required
• You will need to perform a cold restart of your API cluster.

New Features

Amazon ECS

• Adjusted the default Amazon Elastic Container Service settings to support multiple retries and improved timeouts so as to more effective handle Amazon API throttling and 429s when running a large number of parallel ECS container tasks.

Automatic Query Optimization

• Indexes for branch collections are now automatically analyzed and maintained so as to optimize for query performance. This new facility works hand-in-hand with query analysis to compute and apply indexes that address queries that perform slowly.

Containers

• Images have been upgraded to Fedora 41 and OpenJDK 21. All libraries and dependencies have been updated to support the latest security patches for these respective packages.

Enhancements

ACL Checks

• Faster Access Control checks that leverage some backported code improvements from Cloud CMS 4.0.

Actions

• The syncNode action now supports the contentIncludeRelatingAssociations flag (using to populate contentIncludeRelatingAssociations on the transfer export during the copy).

Branches

• Tenant logs are now updated to reflect information when branches are created and updated.

Caches

• Added org.gitana.platform.services.node.mongoViewService.repositoryCollectionsMaxSize setting to control max size of repository collections cache (defaults to 2500).

Cluster

• Faster and more efficient distributed lock service for the API cluster. This has been refactored to use a database-driven lock facility. This further reduces our reliance on Hazelcast for these IO-intensive operations and provides a significant performance improvement.
• Atomic values are now stored within the DB and no longer require Hazelcast for persistence.

Datastore Configuration

• Added safety check code to guardrail the datastore configuration service. This helps protect against potential overwrites of any datastore configuration documents.

Hazelcast

• Enhanced the Out of Memory Handler to provide improved logging prior to exit.

GraphQL

• GraphQL now supports a _paths subobject which can be used to look up nodes by path. For more information, see https://gitana.io/documentation/gitana/3.2/guide/guide/graphql.html#paths.
• Optimized data fetchers for faster performance.

Non Cyclicity

• Optimized the f:non-cyclic feature to assert non-cyclicity of the content graph on commit.

Path-Based Find and GraphQL

• The Find API has been enhanced to support path-based lookup. You can now path a combination of Query, Search and Path information to the Find API to perform the aggregated lookup. For more information and examples, see https://gitana.io/documentation/gitana/3.2/guide/guide/find.html#find-in-folder and https://gitana.io/documentation/gitana/3.2/guide/guide/find.html#example-#3.
• GraphQL now supports retrieval of path information within a query.

Performance

• Optimized code paths for query and find operations to better utilize indexes and perform feature DB calls.
• Introduced the internal use of MongoDB $aggregation for optimize code for path-based lookup for file/folders and GraphQL.
• Faster response times and better heap management for all query and find operations.
• Improved usage of internal pagination to reduce the number of MongoDB count operations for faster performance.
• Quicker incremental building on branch tip views on transaction commit via use of bulk operations.
• Faster file folder event handling during transaction write.
• Relator association event handlers now execute much faster during transaction assembly.
• Faster node resolvers that no longer rely on branchService checks.

Search

• The background worker that indexes branches now utilizes pagination and a from token to improve performance for large sets of data.

Single-Sign On (SSO)

• Execution of Group Mapping rules has now been moved out of the UI container and into the API container allowing for faster user/group synchronization on login.
• Updated to the latest SAML and security libraries.
• Certificates are required (no longer optional) for encryption of SAML Assertions.
• Added SSO configuration options to let you assert the digest/hash for the full document and/or the assertions.
• Added SSO configuration option to let you specify the hashing algorithm of the digest/hash (SHA-1, SHA-256 or SHA-512).

Startup

• Faster API container startup time. Refactor of node cache so that node cache initialization step is no longer required.

Transfer Export

• Added a transfer export configuration flag tipModeLockBranch which can be optionally applied to take out a write lock during the export of content off of a branch. This is useful for cases where concurrent threads might be running that modify the branch during export. In these cases, the concurrent changes might produce an incorrect export or cause the exporter to fail. Setting this flag will cause the exporting branch to take out a write lock and will prevent other users from writing to that branch until the export completes. By default, this flag is set to false.
• Added a project setting tipModeLockBranchOnExport which can be optionally applied so that all exports from any branches within the project will automatically have the transfer export configuration flag tipModeLockBranch set. This ensures that all exports of any content from within the project will be done with a branch-level write lock taken out. By default, this flag is set to false.
• Faster export of content with lower memory footprint. This has a significant impact on large exports.
• Added a transfer export configuration flag contentIncludeRelatingAssociations which specifies whether to include non-exported nodes that have associations that relate them to the currently exporting node.

User Interface

• Updated to all the latest dependencies and library versions.
• Removed old libraries (such as Dust.js) which are no longer being utilized.
• Added DDOS safeguards including automatic blacklisting and blocked URI checks.
• Removed custom indexes page (these are now auto-managed by the product on a per-branch basis).

Bug Fixes

Analyzed Queries

• Fix so that cursor timeout defaults are properly applied when performing a count operation across all code paths. This had been causing some analyzed queries to misreport their findings.

Associations

• Fix so that internally paginated result sets are more accurate when running in the context of a large transaction. This impacts cases where some rules where not being tripped for large transactions. It has a more notable impact on complex content models with deeply nested relators.

General

• Fix for cases where some cached nodes were being cast to incorrect types upon deserialization from cache.
• Fix for spatial find operations around node so that arguments map as intended.
• Fix so that teams clean up properly in cases where some teamable types fail to instantiate fully.
• Fix for an NPE potentially being thrown while handing exceptions that fell out of one shot optimized queries.
• Fix so that late grantAuthority() calls during import don’t cause an overall failure post transaction due to the transaction collection not being found.

Paginated Iterators

• Fix so that any calls relying on paginated query iteration using a fromKey now perform proper comparison of result set size with limit instead of using total rows.

References

• Fix so that node reference resolution properly throws a ReferenceResolutionException for cases where a branch’s tip view is not available (or has been archived).

Tags

• Fix so that tags work and merge as expected during branch merge and release commit.

Transactions

• Fix so that the order of nodes is guaranteed within a multi-level transaction. This improves accuracy and ensures consistency of result set ordering.

Transfer Export

• Fix so that exported nodes are reloaded durign tip mode exports to ensure references are established against the tip changeset.
• Fix so that references are not errantly calculated if concurrent changes are made to the exporting branch between the time of job submission and the time of job execution start.

Tree

• Fix for tree path expansion by properly detecting empty paths element.

User Interface

• Fix so that data tables now work properly for edge cases where an API call was being made in an event handler immediately after rendering.
• Fix so that login redirects take you back to your originally intended URL after login.
• Fix so that pickers now properly validate maxItems/minItems and revalidate on call to setValue().
• Fix so that user registration email requests fall back properly for cases where the user already exists.
• Fix so that I18N locales display consistently throughout the UI (common code path).

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.86 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://www.gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-86.html

New Features

Container Routes

• Added support for container management routes for internal use in triggering container lifecycle event handlers. This enables support for preHook calls within Kubernetes, ECS and other container management facilities to inform the API container that it is about to shutdown. As a result, the API container is able to gracefully
  able to reschedule running jobs onto other cluster members and gracefully release system resources ahead of container termination.

For more information, see:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/maintenance/container-hooks.html

Enhancements

Activities

• The Activities collection within MongoDB is now capped to 50MB to optimize query performance and reduced total storage requirements.

Amazon ECS

• Improved support for Amazon ECS by introducing new ECS-specific properties for cluster, family and serviceName.
• Added new AWS global properties for hostHeader, connectionTimeoutseconds and connectionRetries.
• For more information, see:
  https://gitana.io/documentation/gitana/3.2/guide/guide/docker/configuration/api-server.html#discovery-services
  https://gitana.io/documentation/gitana/3.2/guide/guide/docker/container-frameworks/ecs.html#cluster-configuration

Command Line Tool

• Added a new operation for branch repair (incorrectAttachments) which identifies and repairs any attachments in a branch that may have the wrong MIME type or an invalid stream pointer.
• Added support for HTTP/HTTPS proxies.
• Increased the timeout for administrator API calls.

Dictionary Service

• Faster dictionary compilation with tracking of total iterations and force fail states to limit the total number of iterations (and prevent timeouts).

GraphQL

• The underlying GraphQL service now uses a standalone executor services to cap the number of threads participating in data and batch loaders (16 by default).

Jobs

• Faster performance and lower memory overhead for job dispatcher and background job execution.
• Improvement to job kill, interrupt and pause mechanisms to allow for faster and more efficent release of thread resources.

Libaries / Dependencies

• Update to the latest dependencies including the latest version of PDFBox, Apache Tika, Jackson and Log4j2 with all security vulnerability patches applied.

MIME type detection

• Improved detection of MIME types for input streams, incorporating new strategies and libraries for marker byte detection.

Performance

• Faster startup time with quicker node and branch cache initialization.
• Reduced memory usage for internal Hazelcast caches used to manage graph state.

Permissions / Authorities / Teams

• Faster access control checks for permissions, authorities and teams.
• Improved utilization of MongoDB queries to more efficiently look up multi-level ACLs.
• Refactor of role service to provide faster and more acccurate location of inherited roles.

Releases

• Releases now track their execution within a release job allowing for improved logging and error capture.

SDK

• Updated Amazon ECS examples to include JVM flags and usage of new configuration options.

User Interface

• Server-side network settings have been optimized to improve network performance.
• Server-side code paths have been refactored to reduce the usage of distributed locks to improve request throughput.
• A dictionary definition and content type cache has been added that reduces the number of network calls and improves the speed of page loads.
• The branch cache now works across multiple projects and branches in multiple windows at the same time.
• Data loaders now work much faster by taking advantage of the new dataloader features in the API.
• Adjusted the way that 401 responses are handled to more accurately detect an invalid_token response.
• The Content Types page now includes automatic filtering out of system types.
• UI Templates now load much faster.
• The Create New Data List Item dialog now works similar to the Create Content Instance dialog.
• Removed the Safe Repair button from the Platform Tools page as this functionality is now invoked via the Command Line Tool.

Workflow

• Added index for workflow title to optimize sorting performance.

Bug Fixes

Branches

• Fix to ensure that branch collections (tip and deletions) clean up as intended when branches are deleted.

Data Loader

• Fix so that the _dataloader flag can be provided either via request parameter or via request object.

Indexing

• Fix so that calls which perform index creation and deletion within MongoDB wait until the operation completes before proceeding.

Merges

• Fix to merge processing that prevents nodes that are not relevant to the merge from creating conflicts for certain cases.
• Fix to merge processing so that order sorting is computed properly and retained during execution.

MIME types

• Fix so that mimetype detection for image/svg+xml works as intended for some edge cases.

Tags

• Fix for tags events in layered transactions so that tags commit more efficently and without conflict.

Transfer

• Fix so that single-changeset transactional commits do not fire inner after handlers for inner, nested transactions.

User Interface

• Fix so that remote config is loaded correcftly for all page flows and click paths.
• Fix so that the publishing content types page no longer errantly sets values onto the project.
• Fix so that the Node Picker’s up/down/remove buttons no longer show up for properties of type object.
• Fix so that the reset password authentication flow properly displays errors messages for 500 response types.
• Fix so that the Advanced Search property filter evaluates definition properties correctly.

Web Hooks

• Fix so that web hooks do not fire multiple times on import.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.85 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://www.gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-85.html

Enhancements

Container

• Improvements to graceful termination of container due to out-of-memory exceptions. These are now pre-emptively detected and the running container is allowed to gracefully sigterm/shutdown more quickly. This solves for some edge cases where the JVM could potentially run out of memory ahead of the Kubernetes or ECS agent determining there was an OOM or memory limit tripped.

Find

• Improve find methods so as to reduce the number of DB operations and/or Elastic Search queries needed to support the ordered concatenation of result sets. The result is faster and more efficient find operations. The impact is particularly notable for increasingly larger result sets.

GraphQL

• Optimize the GraphQL Node ID batch loader to utilize paginated reads while reducing counts and excess field loading.

Jobs

• Additional configuration options for all job types, allowing per-job customization of concurrency (both globally and per-platform for multi-tenant support) along with any additional properties. These new configuration options are loaded at system startup and can also be modififed and adjusted at runtime.
• Adjusted the default configuration settings for typical jobs to provide for better job flow, reducing bottlenecks and improving out-of-the-box job execution throughput.
• Added and improved service methods for pause, resume and bounce, allowing jobs to easily bounce from one container to another within the cluster, to ease the intended restart or forced migration of jobs due to containers being brought offline or crashing. This allows jobs to transition between servers, as needed, while executing or in the event of intended or unintended container downtime.

Locks

• Refactored and improved support for local and distributed, cluster-wide locks so as to better take advantage of Hazelcast CP subsystem and reentrant locks. More rigid and dutiful handling of timeouts and retries.

Performance

• Reduce the number of internal query calls that perform count operations so as to reduce drag on the database in several places. This results in faster operations and faster API throughput.

Query

• Improvements to method that retrieves node IDs for a given query so that it is paginated and performance optimized.

Scripts

• Each rule and/or behavior script now has access to the platformId for the repository, branch and node against which the script executes.
• The platformId is now automatically applied to any platform-bearing actions that are spawned via the actions root-scoped object within an executing script. This ensures that any spawned child actions have access to the same platform ID for jobs reporting purposes.

Tags

• The merge and transfer export/import system now matches nodes on tag values (in addition to _doc, QName and path) allowing tags to seamlessly merge between branches and upon release, publish or import.

User Interface

• The application internal caches are now managed within IndexedDB to increase storage and improve performance while clicking through the editorial interface.

Bug Fixes

Dictionary

• Fix so that dictionary event handlers are invoked properly on transaction commit. This ensures that all add and remove events trigger for all cases, keeping the dictionary state lock-step with the branch tip content for all creates, updates and deletes.

General

• Fix so that thread local variables clean up in the correct order for an edge case that resulted in additional, errant logging when authenticating.
• Fix so that behavior bindings running in parallel are better protected against concurrent updates to the bindings map.

GraphQL

• Fix so that GraphQL cache state is properly updated on branch commit for cases where nodes are deleted.

Inline Links

• Fix so certain null values do not prevent inline links from being parsed and populated.

Jobs

• Fix so that job kill operations work more consistently across the cluster.

Multi-Factor Authentication

• Fix so that the trusted authenticator (using TOTP algorithm) works consistently for cases where the generated code may have lapses for up to N time periods).

Policy / Scripts

• Fix so that dynamic policy models are correcly populated on a per-invocation basis ahead of firing through into the script service. This ensures that the model that the executing script sees is as accurate as possible.

Search

• Fix so that malformed search queries are detected earlier and thrown outright, preventing them from being processed by downstream search engines.

Transfer

• Fix so that the import sequence counter uses an incremental identifier that no longer based on insertion time so as to prevent non-deterministic ordering.

User Interface

• Fix so that session storage is always cleared on logout.
• Fix so that the MFA login process shows an informative message for cases where back-end API server communication fails.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.84 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://www.gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-84.html

New Features

New Serializers

• A new distributed data grid serializer engine has been introduced that uses the Kryo engine to run much faster, use less memory and greatly reduce the need for cold restarts of the cluster. These serializers run within Hazelcast and allow for the Hazelcast cluster to remain up during some upgrades that would have previously required a cold restart. Upon upgrade, these new serializers run automatically and customers will see a noticeable performance improvement and lower memory usage.

Container Services and Examples

• A new mechanism for configuring and managing clusters of Gitana containers (API, UI, Antivirus and others). This facility makes it easier to deploy secure and complex, production-quality infrastructures using container ochestration frameworks including Kubernetes and Amazon ECS. See Setting up Gitana on-premise with Kubernetes and Setting up Gitana on-premise with ECS for more information.

Tools

• An administrative tools facility that provides cluster administrators with a comprehensive set of tools for working with public and private keys, securely encrypting configuration properties and easily configuring aspects of their cluster.

Enhancements

Amazon OpenSearch

• Improved support for Amazon OpenSearch (as an alternative to Elastic Search). Supported versions up to AWS OpenSearch 2.11 along with improved documentation, configuration settings and driver integration to support HTTPS, AWS role-based access and bulk indexing operations.

Amazon DocumentDB

• Improved support for Amazon DocumentDB (as an alternative to MongoDB). Supported versions up to AWS DocumentDB 5.0.0 along with improved documentation, configuration settings and driver integration to support TLS/SSL, AWS role-based access and authentication.

API

• The x-cloudcms-request-id header is now checked to determine whether an upstream request ID can be found and utilized. If not found, this ID is generated as before. The request ID is logged to all audit records, log entries, ingress services and more.
• Added API method for bulk updating nodes with HTTP PUT.
• Added support for reading from separate source and target repository branches when using the startCopyFrom API method

Archives

• Added more indexes to the vault archives collection to assist with faster queries and pagination.

Branches

• The dictionary services were refactored to use less memory, offer faster compilation and improved validation accuracy on a per-branch and transactional basis. Heap usage is much lower and incremental compiles are very quick, allowing for much higher throughput and quicker turnaround of requests.
• Faster branch merges due to optimized queries for computing merge points in branch lineage histories.

Dependencies

• Update to base image including OS dependencies, JDK 17, LibreOffice, ImageMagick, Hazelcast, H2 and other runtime components.

Images

• Update to latest ImageMagick 7.x libraries with improved, faster support for conversions and transformations.

JavaScript Driver

• Added support for bulk updating of nodes.
• Added support for deletion of workflows.
• Added support for optional generic types and interfaces.
• Improved support for error handling with 5xx non-JSON responses.

Query Performance

• Fine-tuned a number of queries within the service layer to reduce the number of long-running queries. Large queries are split into smaller, cursored queries that reduce the drag on the database by utilizing partitioned result sets.
• Improved query optimization to detect further cases where inefficient queries can be restructured for faster database execution.

Bug Fixes

Attachments

• Fix so that attachment retrieval errors do not errantly send JSON to the output stream.

Copy / Transfer

• Fix so that node cache invalidates properly for some edge cases during Project Copy.
• Fix so that Project Copy defaults to using server-side copy of binary attachments.

Forms

• Fix to rendering function for Alpaca markdown field to make it more extensible.

Java Driver

• Fix to the killJob() function so that it works as intended.

JavaScript Driver

• Fix so that vault references are computed correctly.

Jobs

• Fix a bug so that job records may be marked as killed upon receiving cluster messages even when the corresponding execution thread is not found.

Modules

• Fix so that modules load their action configs consistently for cases where browser cache may affect how modules are required into pages on non-initial visits/clicks.

Network

• Fix to improve the handling of socket timeouts for cases where long keep-alives where allowing sockets to remain active for longer than intended.

Search

• Fix so that wildcard deletion of search indexes is supported within the API (using an alternate means) for cases where wildcard support is disabled at the Elastic Search cluster-level.

SSO

• Fix so that the identifier field is properly picked up from configuration for cases where non-standard or custom values are applied.

UI

• Fix so that pagination works as intended for deployment strategy listings.
• Fix so that user default project settings are applied properly on initial session render.
• Fix to allow form picker to be disabled.
• Fix so that the Copy Project UI action utilizes default attachment configs.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.83 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://www.gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-83.html

Enhancements

Branches

• Branch merge operations now use less memory and run more quickly, allowing for larger merges to execute without incurring a large impact to allocated heap memory.

Command Line Client

• Removed commands related to repository compression as those facilities are being moved out into MongoDB-level scripts.
• Additional commands for delete branch and delete snapshot.

Dictionary

• Reduction in runtime memory requirements for storing compiled dictionary state per branch, resulting in less heap allocation.

Indexing

• Improvements to default MongoDB collection indexes that result in much faster query performance.

Java Driver

• The Cluster.waitForJobCompletion() method will now re-attempt to read the job if an unexpected error occurs (potentially due to a network issue). Upon a second failure, null will be returned.

JavaScript Driver (v1)

• The cluster.waitForJobCompletion() method now provides a trap handler.
• The logic for domain ID extraction within extractPrincipalIdentifiers() is now more precise.

JavaScript Driver (v2)

• Updates to dependency libraries, latest version of Axios.

Multilingual Feature

• Improved the error logging for the multilingual feature so that the Node ID is included in the report.

Python Driver

• Added new methods for CRUD operations around deployment targets.

Query

• Added query optimization pre-parsing stage to automatically optimize some common queries for faster performance.

Relator Properties

• Relator associations now resolve much more quickly with code paths that have been optimized to be much faster.

Transactions

• Branch transactions now run much more efficiently and utilize less heap memory. They automatically passivate state to disk to allow for much larger transsaction sizes to run with lower memory requirements.

User Interface

• Faster performance and lower latency with the introduction of a faster reverse HTTP proxy. This offers better socket handling and greater throughput for customers.
• DNS caching has been improved to lower latency further by reducing the number of DNS calls during routing.
• All internal HTTP communication has been refactored fully to use the Axios client.

Bug Fixes

API

• Fix so that thread locals bound during the request are released via the fallback servlet listener as intended.
• Fix so that retrieval of node version history from an archived branch works by forgoing the inclusion of attachment information if the branch view is not ready.

Branch Changes

• Fix so that the accuracy of branch differences for cases where the source node was deleted is correct.
• Fix so that branch changes are invalidated (instead of rebuilt) if the branch is archived.

Copy / Deploy

• Fix so that Copy and Deploy jobs are more resilient by having them default to pulling down the full binary as part of the payload (avoiding the “preserve archive output directory” optimization).

Dictionary

• Fix for a subtle case where the compiled flag could be prematurely set for some compiled associations.

Merge

• Fix so that patch paths are always correctly normalized into path format ahead of calculating index adjustments during merges of array properties.

Transfer

• Fix so that Transfer Import jobs correctly handle the import of Node Lists.
• Fix so that branch reloads are handled more gracefully, preventing early errant termination of transfer workers.

User Interface

• Fix so the pagination of team members works as intended within the Administration Console.
• Fix so that direct JSON edits to documents refreshes the screen as intended.
• Fix so that the workflow task, documents and instance screens show more information. New fields are shown by default, such as purpose.
• Fix so that the PDF viewer consistently formats the filename of retrieved and saved documents.
• Fix so that static files are served back with the proper MIME type (resolving issue with errant .appcache file detection).
• Fix so branch custom indexing pages to remove pagination and filter box.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.82 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-82.html

Enhancements

Command Line

• Added a command to support querying of archives from a vault.
• Added more options to the branch repair command.

MongoDB Configuration

• Added support for configuration of Read Concern defaults. For more information, see: https://gitana.io/documentation/docker/configuration/api-server.html#replicated-read-only-mode
• Added support for configuration of Replica Set Secondary Read Preference Tags. For more information, see: https://gitana.io/documentation/docker/configuration/api-server.html#read-preference-tags
• Added support for configuration of Secondary Read Preference Staleness. For more information, see: https://gitana.io/documentation/docker/configuration/api-server.html#secondary-read-preference-staleness

Projects

• Added a checkbox on project creation which allows for project creation to perform server-side binary copies. This supports smaller archives where archives do not contain all of the binaries but instead utiliz the copyAttachments feature to copy those binaries into place (via a server-side copy) upon import.

Replicated Read Only (Preview)

• Added experimental replicated read-only features to support runtime environments running on read-only MongoDB secondary members. These environments run in real-time on data that is replicated behind the scenes via MongoDB to read-only secondaries. To learn about these features, please see: https://gitana.io/documentation/docker/configuration/api-server.html#replicated-read-only-mode

Bug Fixes

ActiveMQ

• Fix so that connections are constrained via default configuration to a more reasonable level and cleaned up properly, preventing possible leaks under heavy load.

Amazon S3

• Fix to prevent the underlying transfer manager from padding queued streams for cases where multiple parts were being aggregated in parallel.

Branches

• Fix so that directly unarchiving a branch will clean up for an edge case where a branch might be marked as archived even if a release is not.

Download Streaming

• Fix so that downloads work as intended for cases where partial HTTP range requests are utilized and a buffer length was being miscalculated and incorrectly asserted.

IBM Cloud Object Storage

• Fix so that IBM COS Stores clean up buckets upon teardown (if configured to do so).

Merge

• Fix so that merge works correct for complex cases where nested array elements overlapped in such a way that patch element uniqueness was being incorrectly calculated.

User Interface

• Fix so that UI dashlets properly load and utilize their dynamic configuration as intended.
• Fix so that authenticated user ID is maintained properly within UI session for all cases.
• Fix so that locales are consistently parsed and compared according to a single convention.
• Fix so that the “Add Translation” flow and population of the content editorial dropdown works as intended.
• Fix so that the Manage Project Locales page performs input validation upon entry.
• Fix so that the Content Instances page properly loads dynamic configuration as expected.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.81 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-81.html

New Features

Supported Stack

• Added support for MongoDB 5.0.14
• Added support for MongoDB 6.0.4

Enhancements

Command Line Client

• Added support for new transfer command flags - includeAssociationType, exportAssociationType and associationMaxDepth.

Definitions

• Improved the performance of branch definitions query and also enhance the accuracy by moving more pagination into the DB.

Dependencies

• Updated to the latest thirdparty dependencies for Log4j, Jackson, Tika, and PDFBox among other libraries.

Transfer

• Added support for the optionalAssociationsIncludeTypes flag on export to allow for explicit declaration of any association types to be crawled when exporting. Support for this has been added to the command line client allowing for increasing detailed imports and exports of projects, branches, nodes and everything else.
• Adjusted the includeBinaries and includeAttachments flags so that they default to false.

User Interface

• Added a selection box to the project export wizard allowing for specification of whether the user wants to export binaries/attachments.

Bug Fixes

Activities

• Fix so that the default sorting within the UI works as intended for large collections of activities.
• Added new indexes to the Activities collection to support sort by timestamp and content type.

Admin Console

• Fix for a bug where trailing slashes within internal URLs would cause menu and breadcrumb links to fail to dispatch.

Definitions

• Fix for a bug whereby definitions could sometimes come back from the definitions query method with missing properties due to a JSON serialization issue.

User Interface

• Fix so that the content types page dispatches correctly for certain cases where composite tokens were being used in the route.
• Fix so that local and session storage state encodes properly for all cases.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.80 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-80.html

Enhancements

Branch Merging

• Improvements to the branch merge algorithm to enhance its ability to stitch together disparate sets of changes with a more complex changeset history. Solves for a number of cases that have to with nested sub-objects and subarrays being reordered and optimizes the number of resulting operations that need to be performed to normalize the different changeset histories.

Command Line Client

• Added new commands for CRUD operations with stacks as well the assignment of data stores to stacks.
• Improved command line support for switches with special characters.
• Enhanced the --authcode switch to work for more cases (allows for a pre-acquired MFA verification code to be supplied).

MFA

• Added more logging when an MFA provider’s verification call fails to help administrators diagnose provider configuration issues.

Project Creation

• Improved the Project Creation facility so that it uses a background job that is now optimized to consume as little of the job queue as possible. This also eliminates an errant timeout issue which arose in the past when creating jobs from large archives.

User Interface

• Faster user interface with fewer HTTP calls and more caching.
• Improved the experience of working with Document Translations. Added a button to the edit document translations bar to make it easier to quickly add a new translation for the current document. Page routing now includes locale information so that the current translation is not lost on refresh or navigation.
• Added the ability for the Content Types page to group content types hierarchically (such as /Components/Web). Supports expansion and selection of groups as well as content types. Content Type grouping can be defined under Content Definition > Paths.
• Project Managers can now precisely specify the fields to be filtered on when using the Content Types or Documents page. Fields can be specified under Manage Project > Settings.

Bug Fixes

ActiveMQ

• Fix to reduce tehe maximum size of the Active MQ client thread pool. This lowers the overhead associated with additional threads being allocated into the JVM to support ActiveMQ message dispatching.

Elastic Search

• Fix to reduce heap allocation per iteration by reducing the driver default scroll batch size.
• Fix to pagination to correct for a miscalculation of each iteration’s batch size for cases where limit is being applied.

GraphQL

• Fix to prevent concurrent modification exceptions by introducing a thread lock when collection sets of paths.

Internationalization

• Fix to prevent an exception from being raised for some permissible cases where a master node’s translation cannot be found.

Jobs

• Fix to ensure that platformId is assigned to spawned child jobs during project import to improve the facility of tracking and monitoring child job activities.

Merge

• Fix to ensure that the Auto Merge Conflict resolution settings for Releases are considered and applied during dry run merges.

Multi-Factor Authentication

• Fix to correct for some cases where users of code-based authenticators could be prompted multiple times for verification code entry.

Property Mapping

• Fix to prevent an exception from being raised for certain cases where a prior transaction did not occur.

SSO

• Fix to correct a bug whereby a route lock could be taken out but not released in a timely fashion during SSO login.

Transfer

• Fix to ensure that project exports will work consistently for cases where those exports contain multiple branches and one or more of those branches are in an archived state.
• Fix to perform faster upload and download of large archives so as to prevent HTTP timeout of middle tier proxies (with low timeout settings).

User Interface

• Fix so that the re-ordering or transition of items in an array or object does not errantly reset the full field value for cases where the schema of the underlying container object is dynamically faulted via a network connection.
• Fix so that list-based controls do not briefly lose their CSS and visually flicker on click.
• Fix so that modal popups no longer scroll the page upon completion or working with certain internal fields.
• Fix to some CSS and image elements for the dark theme.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.79 release.

Upgrade Considerations

Please review the upgrade considerations provided here:
https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-79.html

New Features

ARM-64 Support

• With this release, we are proud to announce official support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x86-64. For more information, please see: https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-79.html#support-for-arm-64

Word Count (f:word-count)

• Added the f:word-count feature that, when applied, automatically counts the number of words per text property (and across all text properties) for the given node. For more information, see: https://gitana.io/documentation/features/word-count.html

Reading Level (f:reading-level)

• Added the f:reading-level feature that, when applied, automatically evaluates the reading level per text property (and across all text properties) for the given node using the Flesch-Kincaid scoring algorithm. For more information, see: https://gitana.io/documentation/features/reading-level.html

Enhancements

Analyzed Queries

• Analyzed Queries now include project ID as a filter option.

Authorities / Permissions

• Enhanced the diagnostics page for authorities and permissions to provide a more detailed explanation about why a principal might or might not be granted a specific permission or authority against a resource.
• Faster team-permission checks for node query, find and search API calls.

Branches

• Added a Branch Repair operation to automatically detect and fix duplicated QNames within a branch.
• Added a Branch Repair operation to automatically detect and fix invalid QNames assignments within a branch.
• Branch Repair utilizes bulk commits more effectively for faster operation.
• Improvements to Branch Merge logic to be more efficient and less memory intensive.

GraphQL

• Improvements to GraphQL service-level caching and request handling to be faster and use less heap.

MongoDB

• Adjusted the default for mongodb.default.connectionsPerHost to 100.
• Adjusted the default for mongodb.default.waitQueueMultiplier to 2.

Preview

• Preview generation is now faster and less memory intensive with a stronger preference given to deferment to background jobs (instead of transformation on the live request).
• Improvements to the underlying transformer libraries to provide faster and improved support for Office documents types and images with a particular emphasis on fast transformatons for large Excel/Spreadsheet documents.

Third Party Dependencies

• Latest updates and security patches applied for Log4j, OpenOffice, Spring Framework, Spring Security and many other third-party libraries.

Search / Indexing

• Added the elasticsearch.condor.connectionRequestTimeoutMs setting to allow on-premise users to calibrate the timeout so as to help prevent the Elastic Search connection manager from queueing up threads for cases where the Elastic Search endpoint is slow to respond or requests are otherwise timing out.
• Elastic Search indexes now build in the background and swap into place gracefully with zero downtime even for cases where 1 or more documents may have failed to index (these errors are reported in the logs but the resulting index is retained).

Transfer

• Linked Relator Associations are now ignored on export for certain cases so as to reduce the overall manifest size on export.
• Added a configuration option on toggle the forced export of relator associations for given related nodes.
• Node transfer exports now use a paginated query handler to make the lookup of associations more efficient (to address a potential database-level timeout issue).

User Interface

• Improvements to the /proxy route to allow for faster streaming of static assets, attachments and preview images.
• Removed the none options for Rule Conditions.
• Removed the Reindex Platform Datastore tool from the tools page (this functionality is available via the command line client).
• The Analyzed Queries page now includes a time column and provides a Project Picker field for filtering by project.
• Improvements to the Merge Conflicts page to reduce the number of API calls and simplify the user interface flow when retrying merges after resolving conflicts.
• Updated the use of picker fields throughout the UI, including consistent use of Team pickers, Project pickers and more.
• Improved the way that socket.io is utilized and the rendering of awareness icons.

Bug Fixes

Authorities / Permissions

• Fix so that team policies work as intended for complex cases where multiple teams may define overlapping revokes and grants.

Branch / Merge

• Fix so that merges complete successfully for a specific edge case that involved the resolved target node being in a deleted state.

File/Folder Service

• Fix so that the merge of a document that has had its title changed will properly updates its path within the target branch for cases where the filename is not explicitly set but is being derived from the title itself.

Find

• Fix so that pagination is properly applied to find calls for certain cases involving specific field selection.

GraphQL

• Fix so that GraphQL no longer throws branch initialization errors for certain cases where a branch is being faulted into memory in a distributed, multi-server configuration.

Publishing

• Fixed a bug where Branch Deployment Handlers were not properly registering themselves as a dependent of the Deployment Commit Handler job which resulted in some publishing jobs completing but marking themselves as having failed.

Transfer

• Fix so that domain principal importers work properly for cases where an older export might not include a full set of membership information.
• Fix so that associations do not overwrite on import for certain cases involving child association types.

User Interface

• Fix so that the UI server properly configures itself for Redis 4 support across all services (supporting multiple servers in the cluster but also multiple cores on a single machine).
• Fix so that the Jobs page uses proper display colors and filters as intended when switching between Projet and Platform contexts.
• Fix so that UI Wizards can no longer errantly duplicate cards when a user hits the back button multiple times in a very short interval.
• Fix so that the Analyzed Queries page now paginates as intended.
• Fix so that actions on the Document Versions page work as intended for all cases.
• Fix so that the Avatar and Attachments fields no longer force regeneration of preview images (allowing for cache to be used more efficiently).
• Fix so that the Platform and Project Activities dashlets properly reflect the target Branch.
• Fix so that form buttons and toggles are disabled when a document is locked for concurrent live editing.
• Fix so that lists render more accurately and reflect pagination information correctly for certain edge cases.
• Fix so that the Branch/Release selector is more legible and reflects the intended background color for cases where branches/workspaces have custom colors applied.

Versions

• Fix so that node version information is returned properly for older nodes that no longer conform to tip schema.