> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/release-notes/release-notes/2025.12-servoy-cloud-external.md).

# 2025.12 (Servoy Cloud) - External

## Setup ServoyCloud pipeline from Servoy IDE

ServoyCloud now allows you to **create a delivery pipeline directly from the Servoy Developer IDE** for your existing Servoy solution. This simplifies the process of connecting your local development to ServoyCloud. This will create an application with a pipeline for the current Servoy solution.

{% hint style="info" %}
**Pre-requisites**

An existing **ServoyCloud namespace** is required. If you have not set up your free ServoyCloud namespace yet, see [namespace setup](/reference/servoy-cloud/cloud-control-center/home/setup-namespace.md).
{% endhint %}

To setup pipeline from Servoy IDE:

* Right click on the Servoy solution name
* Go to `Export Solution` -> `Setup pipeline`
* Complete wizard by filling in the required details
* Your pipeline will be ready to access and manage in Servoy Cloud Control Center

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2FnxWenQ6F5TzT7vxV7749%2Fsetup_pipeline.gif?alt=media&amp;token=e5c1bb3e-584e-43b4-b359-6474b5579d2c" alt=""><figcaption><p>Servoy Cloud Pipeline Setup Wizard from Servoy IDE</p></figcaption></figure>

***

## ServoyCloud Login & User Management

* **Login templates** - Login templates can now be configured per solution.

{% hint style="warning" %}
User access and permissions to solutions may need review since login templates are now solution-based.

To check access to solution:

* User Management -> Desired user -> Solutions
  {% endhint %}

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2F368fF43An2qd45T5n5Np%2Flogin_template.gif?alt=media&amp;token=2c419bec-aead-4c8b-821b-cafc517c2b1c" alt=""><figcaption><p>Configure ServoyCloud Login Template</p></figcaption></figure>

* **Users** - Added display of linked tenants, ability to add/remove users from solutions, primary solution flag, and force password reset option.
* **Login history** - Login history now includes tenant name, login status, and failed login errors.
* **Permissions** - Selected tenant is now included in user permissions as `servoyCloud$tenant$TENANT_NAME`
* **User Management Settings** - Added configuration options for custom SMTP and SSO user creation behavior. See example below.

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2F2dWkkTCetcbdOUVnJ7hr%2Fimage.png?alt=media&amp;token=7e1216a1-25f9-450b-8943-17b3f67efc63" alt=""><figcaption><p>Example of custom SMTP and user creation settings for Servoy Cloud Login</p></figcaption></figure>

### **New tenant features**

* **Tenant description** - Added support for describing tenants.
* **Tenant lock/unlock** - Added ability to lock tenants to prevent linked users from logging in.
* **Auto-link users** - Added support to automatically link users to tenants based on domain names.

***

## Ticket Commits View with Diff dialog

### **View commit diffs**

The commits tab now shows more repository details, including repository name, branch, and other key information.

Clicking on a commit's title or subject opens a diff dialog, allowing you to review the changes introduced by that commit.

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2FC0kzQeLekRVLneghxJ0s%2Fticket_commits.gif?alt=media&amp;token=bc02b267-d4ca-46f3-8b8a-4407db0ae852" alt=""><figcaption><p>Commit diff view from Project Management > Tickets > Commits</p></figcaption></figure>

### **Clear repository commit history**

If commit data is missing or outdated, you can clear the repository's commit history, which triggers a fresh sync to fetch the latest data.

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2FXCjS7ZCP9OafMzvucbkr%2Fticket_commits.gif?alt=media&amp;token=03a924a5-f90b-4665-9a1b-479c2f0e2b17" alt=""><figcaption><p>Clear repository commit history feature</p></figcaption></figure>

***

## Manage Batch Processors

Added support to start, stop, enable, or disable batch processors defined in the servoy properties file.

To access this view, go to Environments -> Batch processors

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2FmUMv3xayr1zBZ3GLDvv1%2Fimage.png?alt=media&amp;token=0c453ca6-f606-4d65-9e17-8759a87cc4e9" alt=""><figcaption><p>Manage batch processors view</p></figcaption></figure>

***

## **Restore environment to previous build**

Added support to restore an environment to a previous successful build. These builds are marked as `REVERTED`.

To access this feature, go to Environments and click on the `Restore icon` to begin with the wizard.

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2FCxZhWFdVx22srXryOdaT%2Fenv_version.gif?alt=media&amp;token=92022c01-6a14-48c1-8556-19fd008c2d51" alt=""><figcaption><p>Restore environment to a previous build</p></figcaption></figure>

## Pipeline and build packages

### **Updated build configuration history**

Configuration changes of build package details now display a comparison view showing old and new values.

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2F1upmflNggnPHJXrqWvEP%2Fimage.png?alt=media&amp;token=27ef3951-2641-4f83-b5a1-04b2608fce9f" alt=""><figcaption><p>New configuration comparison view in build package details</p></figcaption></figure>

### **Build commits aggregation**

Commits from failed builds are now aggregated into the first successful or reverted build for improved tracking.

<figure><img src="https://3933488479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjpWd52BKwABWxF2lScUK%2Fuploads%2FHWZnQQCJkxJHCJW8mwNR%2Fimage.png?alt=media&amp;token=8da7a189-1827-446b-86dc-4cda781c7cb2" alt=""><figcaption><p>Aggregate commit count from previous failed builds to current successful or reverted build</p></figcaption></figure>

***

## Search & Shortcuts

* **Global search shortcut** - Added a keyboard shortcut `CTRL + SHIFT + F` to focus the search field throughout ServoyCloud.
* **Create new ticket shortcut** - Added a keyboard shortcut to quickly create a new ticket.
  * macOS - `CTRL + N`
  * Windows - `ALT + N`

***

## Other fixes and improvements

### Fixes

* Fixed commits linked to tickets not displaying correctly
* Fixed active users not being shown due to a temporary issue
* Fixed restoring a database from another environment
* Fixed daily build count
  * Now includes successful and failed user-triggered builds (including E2E and unit test failures)
  * Fixed issue where the daily build count was not refreshing
* ServoyCloud Login issues
  * Fixed OAuth login issues
  * Fixed "Remember me" checkbox not being saved in some login flows
* Fixed chart loading performance issues
* Fixed repository list issues when creating an application (templates, SCM, and mirrored repositories are now correctly supported)
* Fixed side navigation menu not correctly selecting items when navigating through nested forms
* Fixed issue where users could not update their profile details
* Fixed sprint name displaying a UUID when the sprint was closed but the ticket was still open
* Fixed search input being cleared after navigating away from a detail page
* Fixed display issue where the current mobile build package showed an in-progress build instead of the last completed one

### Improvements

* **Pipeline**
  * Improved error handling for failed builds with unknown failure reasons
  * Enhanced build trigger information to indicate whether builds were triggered by backend, user, or SCM
  * JAVA 25 support - Added JAVA 25 as an option in pipeline job configuration.
  * E2E/Unit test report navigation - Easy access to E2E and unit test reports from failed build package details.
* **Log Activity**
  * Added support to sync environment E2E logs, displaying hostname accordingly.
* **Database View**
  * Improved performance when handling a large number of databases
  * Added nullable flag display in the database structure view
  * Fixed issue where database tables were not displayed; views and materialized views are now included
* **Project Management**
  * **Active sprints view** - Added "Create ticket" button and option to disable automatic ticket assignment.
  * **Ticket filtering by reporter** - Added support to filter tickets by reporter.
  * **Ticket email notifications**
    * Fixed excessive email notifications
    * Ticket emails now include the ticket title in the subject
* **ServoyCloud Login**
  * Improved UX for users being created or invited. They are now redirected to the primary login solution instead of being redirected to Servoy Cloud.
* **Charts / UI / Performance:**
  * Fixed chart loading performance
  * Improved table navigation by making rows clickable instead of relying on action dots when only a detail screen is available.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.servoy.com/release-notes/release-notes/2025.12-servoy-cloud-external.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.