Client side planning console

concept australia Updated Sep 8, 2026 2 min read client-side-planning-console.md
Raw file servicenow.com

Build your project structure quickly on the client side (browser) without saving details to the server for each interaction. This prevents time lags after you perform actions in the planning console and improves scheduling performance.

For example, when a project manager changes dates on a project task in the planning console, the system must re-calculate dates for dependent tasks and the project. This re-calculation can cause time lag if each interaction is saved to the server. Similarly, when a new task or a dependency is created, there can be a time lag before the new dates are displayed. This occurs if they are saved on the server side each time.

When client side planning is enabled, the changes such as re-calculation of dates aren't posted to the server immediately. All the changes in planning console are kept on client side until the user explicitly saves the changes to be committed to the server.

Exceptions

There are a few actions for which you must save your changes immediately to the server side before proceeding such as:

  • Create baseline
  • Copy project
  • Copy partial project
  • Add child tasks
  • Add external dependency
  • Edit Assigned to
  • Edit Additional Assignees

In addition, if you enable custom business rules on any of the columns, those columns are also part of exceptions.

Parent Topic:Using Planning console - Legacy

Related topics

Open the project planning console

Planning console tasks

Gantt chart

Create a parent-child relationship on the planning console

Predecessor dependencies in the planning console

Custom columns in the planning console

Create a dependency from the planning console

Using Planning console - Legacy

Search documentation
Search document titles and file paths on the australia branch