When Questetra releases a new version, System Administrators can select the timing (update date) for applying the new version to each workflow platform. This article explains the update mechanism, version notation format, annual update policy, and release-related schedules for System Administrators.
◆ Selecting an Update Schedule (Rapid / Scheduled)
For each workflow platform, you can choose between an [Rapid Update] or [Scheduled Update] schedule.
- Rapid Update: The workflow platform is updated on the release date of Questetra’s new version, allowing you to use new features right away.
- Scheduled Update (Default): The update is applied approximately 1 month (4 to 5 weeks) after the Rapid Update. This provides a preparation period to gear up for the new version deployment.
If you wish to pre-test new versions, you can subscribe to two workflow platforms: set the production environment to [Scheduled Update] and the sandbox/testing environment to [Rapid Update]. This setup enables you to thoroughly verify the impact of new features, specification changes, and your custom automated processes before applying them to production.
◆ Questetra Versions and Notation Format
Questetra versions are expressed in the format X.Y.Z. Each variable (X / Y / Z) carries the following meaning. The new versions eligible for selecting an update schedule refer to releases that include specification changes requiring prior modifications to App settings or code (where X / Y is updated).
| Category | App Archive | Workflow App | REST API Client |
|---|---|---|---|
| X: Major Version | Archives from older generations can no longer be imported | Case behavior may change unless App settings are modified in advance | Behavior may change unless code is updated in advance |
| Y: Minor Version | No effect | Same as above | Same as above |
| Z: Patch Version | No effect | Behavior of active Cases and released Apps remains unchanged | Behavior remains unchanged |
Major and minor version updates may require prior setup adjustments. Patch version updates do not require prior action.
- App Archives support up to the 3 most recent generations of X (X-1 / X-2 / X-3); archives from versions prior to that cannot be imported. (e.g., Ver. 15 supports archives from Ver. 12 / 13 / 14).
- Patch versions (Z) may include updates that detect configuration flaws in an App and display them as App Setting Errors. While this does not affect active Cases or already-released Apps, the errors must be resolved before that App is next released.
- Z=0 (X.Y.0) is applied only to [Rapid Update] environments. [Scheduled Update] environments will skip X.Y.0 and apply X.Y.1 approximately 1 month later (e.g., On the April 2026 release date, Ver. 18.0.0 is applied to Rapid Update environments while Ver. 17.2.3 is applied to Scheduled Update environments; approximately 1 month later, Ver. 18.0.1 is applied to Scheduled environments).
Note that when referring to a new version, the “.Z” representing the patch version is sometimes omitted.
◆ Annual Update Policy
Questetra releases a version every month. Major version updates (X) occur once a year (in April). Other months generally consist of patch version updates (Z), unless specification changes requiring advance App configuration or code changes are included, in which case a minor version (Y) is released.
The recent version history is shown below. On the release date of a new version (X.Y.0), different versions are applied depending on whether an environment is set to [Rapid Update] or [Scheduled Update]. The labels (Major) and (Minor) in the table indicate when major or minor version updates occur in that environment. For [Scheduled Update] environments, even though the applied version number carries a patch digit, that maintenance window corresponds to their major or minor upgrade step.
| Release Date | Rapid Update Environment | Scheduled Update Environment |
|---|---|---|
| 2025-04-21 | Ver. 17.0.0 (Major) | Ver. 16.2.2 |
| 2025-06-09 | Ver. 17.0.1 | Ver. 17.0.1 (Major) |
| 2025-07-14 | Ver. 17.0.2 | Ver. 17.0.2 |
| 2025-08-18 | Ver. 17.1.0 (Minor) | Ver. 17.0.3 |
| 2025-10-06 | Ver. 17.1.1 | Ver. 17.1.1 (Minor) |
| 2025-11-17 | Ver. 17.1.2 | Ver. 17.1.2 |
| 2025-12-29 | Ver. 17.2.0 (Minor) | Ver. 17.1.3 |
| 2026-02-09 | Ver. 17.2.1 | Ver. 17.2.1 (Minor) |
| 2026-02-18 | Ver. 17.2.2 | Ver. 17.2.2 |
| 2026-04-27 | Ver. 18.0.0 (Major) | Ver. 17.2.3 |
| 2026-06-15 | Ver. 18.0.1 | Ver. 18.0.1 (Major) |
| 2026-07-13 | Ver. 18.0.2 | Ver. 18.0.2 |
| 2026-08-17 | Ver. 18.0.3 | Ver. 18.0.3 |
◆ Schedule for New Version Releases
At Questetra, announcements, new version releases, update tasks, and system maintenance are generally conducted on Mondays (JST). Although the exact timing for applying a new version varies by workflow platform, service-downtime maintenance operations will take place across all workflow platforms.
- 1 Week Prior to New Version Release Date
- Notification of the new version and service maintenance downtime (published via the Support Site under Version Info & Scheduled Downtime, and emailed to platform System Administrators).
- New Version Release Date
- Release date of the new version. Only workflow platforms configured for [Rapid Update] will be updated to the new version (Ver. X.Y).
- Workflow platforms set to [Scheduled Update] and “Trial” will also undergo service maintenance (downtime).
- Approximately 1 Month (4-5 weeks) After New Version Release Date
- Workflow platforms set to [ScheduledUpdate] and “Trial” are updated to the new version (notification sent 1 week prior to the update date).
- Workflow platforms configured for [Rapid Update] will also undergo service maintenance (downtime).
When a patch version is released, an announcement is made 1 week prior to the release date, and all target workflow platforms are updated on that release date.
