Articles in this section

See more

What is New in LYNX: March / April 2026

  • Updated
Follow

LYNX

AI Board - URL collaboration

The AI Board provides a centralized, AI-powered view of planning and operational data, enabling users to identify trends, assess performance, and make informed planning decisions. It is now accessible via a direct URL, allowing users to view it in a standard web interface rather than exclusively through the AI Board environment. This enhancement supports easier sharing and more efficient collaboration across teams.

Access to data within the AI Board continues to be governed by existing Lynx user permissions. Users can only view information they are authorized to access. As a result, the same URL may display different data for different users, since all AI-generated outputs are dynamically filtered based on individual roles and permissions.

 

Important:
Sharing a URL does not grant additional access or override existing permissions. It only provides access within the boundaries of the user’s assigned rights.

This approach ensures adherence to role-based access control policies, safeguards sensitive operational data, and maintains consistent, secure data governance.

De-buffered Mode while using Just in Time Scheduling

In Just-in-Time (JIT) scheduling, enabling De-buffered Mode in combination with the “Show task in early schedule position” option can introduce visible gaps between the project timeline and the reference (green) line. This occurs because JIT scheduling, aligned with Critical Chain Project Management (CCPM) principles, prevents tasks from starting earlier than necessary.

As a result, JIT scheduling takes precedence and effectively overrides the early positioning option. While this behavior supports optimal execution efficiency, it can make timeline presentations less intuitive for project managers who need to communicate current project progress.

To address this, we introduce an updated De-buffered Mode behavior designed to provide a more practical and presentation-friendly scheduling view.

When De-buffered Mode is enabled:

  • Projects are scheduled as soon as possible (ASAP)
  • This behavior is triggered only when:
    • The project status is set to Released, and
    • De-buffered Mode is actively enabled in the project view

This enhancement provides several key benefits:

  • Reduced idle time between activities
  • Improved resource utilization
  • Avoidance of premature task scheduling
  • Stronger alignment between planning and execution

Overall, the updated behavior balances CCPM principles with the practical needs of project visualization and communication

 

“Start No Earlier Than” Constraint 

The “Start No Earlier Than” constraint allows users to define the earliest possible start date for a task, ensuring that it cannot be scheduled before that point, even if capacity is available. In Lynx, applying this constraint moves the task forward in time when necessary, along with any dependent tasks. At the same time, the task is not fixed to a single position, as the system continues to optimize its placement after the defined date.

In earlier versions, it was identified that the behavior of this constraint could be improved. Specifically, the scheduling logic for buffer consumption focused primarily on the number of days consumed relative to the total buffer length. As a result, the buffer could appear significantly consumed or escalate to red, even in situations where there was no actual negative impact on the project timeline. This created a misleading impression of delay or risk, while in reality the project remained on track.

By enabling the “Fill leading gaps” option, Lynx takes into account the available slack before the constraint. The system recognizes when there is sufficient time to absorb delays without impacting the critical chain. As a result, buffer consumption is calculated more accurately, providing a more complete and balanced view. In such cases, Lynx offers a more holistic representation of buffer consumption. For example, even though the task was completed on day 14, the project buffer (PB) remains at 0%.

This improvement offers a clearer and more reliable view of project status, helping users better understand the true impact of constraints and reducing confusion caused by previously overstated buffer usage.

 

It is important to note that when the “Start No Earlier Than” constraint is applied in combination with a Deadline, it can lead to projects being scheduled in multiple layers. In such scenarios, the system must reconcile two opposing constraints: one that prevents a project from starting too early, and another that enforces completion by a fixed date. Conflicts between “Start No Earlier Than” and multiple Deadline constraints can prevent Lynx from determining an optimal schedule, potentially causing fragmented timelines or unintended shifts despite recent improvements. Therefore, it is recommended to avoid combining these constraints, as this may reduce scheduling clarity and impact project progress.

If you need to apply the “Start No Earlier Than” constraint, a useful approach is to temporarily stop the project, add the constraint, reschedule, and then release the project again so that Lynx can recalculate and reflect the changes properly.

 

Reporting: History Command

A new command for accessing project history in reporting has been introduced and will be available in the next Lynx update.

You can use the following commands:

  • Released + History projects
    command:projects(released, history);
  • All + History projects
    command:projects(all, history);

These commands enable users to include historical project data directly within reporting, providing better visibility into past performance and project evolution.

 

LYNX-X

Mac version Lynx-X on the AppStore

The Lynx-X application is available for macOS via the Apple App Store, giving Mac users an easy and direct way to use Lynx-X. Developed by A-dato B.V., Lynx-X is the next-generation version of Lynx, bringing key features together in one place. Users can manage projects, view portfolios, work with cards (TameFlow board), and track their own activities within a single application. The app is free to download and works on Mac, making it the main desktop option for macOS users, since the traditional Lynx Scheduler is not available on Mac. For those who prefer not to install an app, Lynx can also be accessed through a web browser.

 

REST API Updates

Updated Standards

The following updates have been implemented to enhance consistency, extensibility, and alignment with modern API design standards:

  • The default value of the status field has been changed from None to NotStarted.
  • Custom property values are now represented as objects rather than single primitive values, enabling support for multiple data types.
  • All error responses now conform to a standardized response format as defined in the API specification.
  • DELETE operations now raise an exception upon failure, replacing the previous approach of returning a response containing "failed: true".
  • DateTime values are now consistently returned as string representations.
  • PATCH operations now return a single resource object instead of an array.
  • The TaskType field has been refactored from an integer to a string-based enumeration.
  • The field previously named "Custom Fields" has been standardized to CustomFields for naming consistency.
  • The ObjectType field now leverages default values for schema generation.

Swagger / OpenAPI Changes

The API documentation and schema definitions have been updated to improve clarity, maintainability, and compliance with OpenAPI standards:

  • Swagger documentation now includes explicit schema definitions for custom properties.
  • Deletion endpoints are now versioned and documented accordingly within Swagger.
  • The security schema has been revised to align with standard OpenAPI conventions.
  • The Rights, Roles, and UserRoles entities are now defined using $ref references and are designated as read-only.
  • The DateTime type is now defined via a $ref reference, ensuring consistency across the API schema.

For more details, please refer to the attached article A-dato REST API Changelog – Support Center.

 

Other Improvements & Fixes

  • Enhanced external dependency messages to include the number of days a dependency is early or late, enabling better assessment of timing deviations and their impact on project planning. 
  • Ensured that added columns are saved within the project view 
  • Fixed the auto-schedule tag 
  • Fixed the auto-update task report 
  • Fixed an issue related to the "Project managers can release projects" setting in Space Properties; Project Managers are now correctly restricted from modifying Start/End dates in the Project Portfolio view. 
  • Fixed an issue where events were not properly processed by the client after login via the new login dialog. 
  • Fixed the Activate Account button to have longer expirary date.
  • Implemented inclusion of Netto Availability for resources in the GetResourceAvailability function used in the report 
  • Improved the delivery of server events, resulting in more timely and reliable system responsiveness. 
  • Introduced enhanced CC “fill gaps” behavior to improve scheduling continuity and resource utilization. 
  • Resolved an issue in the Dependencies tab, ensuring that dependencies are correctly displayed within their designated fields for improved visibility and consistency. 
  • Resolved an issue where projects could be scheduled before the green line, ensuring correct sequencing.

Related articles

Comments

0 comments

Please sign in to leave a comment.