Planning Console Admin GuideIssue Overview The Planning Console is the visual Gantt Chart representation of a Project entity, to illustrate a schedule timeline in an efficient manner. This article is a working guide for administrators in charge of configuring and managing the planning console. In order to open a Planning Console from a Project, follow the steps below: Navigate to: Project > Projects > AllOpen a Project recordGo under Related LinksOpen the Planning Console Related Action Column Metadata and Configuration The column definitions are stored as part of the following tables: Table DescriptionPM_CONSOLEThis holds console column definition for a tablePM_CONSOLE_DISPLAY_COLUMNColumn Definitions that are shown in Gantt GridPM_CONSOLE_TABLETable Entities where to load the Data formPM_CONSOLE_COLUMNActual Column mapping between in the tables for display columnPM_CONSOLE_COLUMN_ADVANCEDAdvanced Column Definition Like Dot walk / Aggregation In order to access the standard OOB Project Configurations for PM_PROJECT, follow the steps below: Navigate to Project Administration > Settings > Planning Console (pm_console)Filter for Table = pm_project AND Context = defaultThere should be one record matching these criteria, this is the Project’s Planning Console Configuration. Default Seeded Columns in Project’s Planning Console Configuration: Label Order Width JSON Column Type Fire BR on Save WBS 100 50 wbs String FALSE Short description 200 300 short_description String FALSE Dependency 300 100 dependencies Decoration FALSE State 400 75 state Choice TRUE Planned start date 500 100 planned_start_date Date Time FALSE Planned end date 600 100 planned_end_date Date Time FALSE Planned duration 700 75 planned_duration Duration FALSE Percent complete 800 75 percent_complete Percent Complete TRUE Actual start date 900 100 actual_start_date Date Time TRUE Actual end date 1000 100 actual_end_date Date Time TRUE Actual duration 1100 75 actual_duration Duration FALSE Assigned to 1200 120 assigned_to Reference FALSE Additional Assignees 1300 120 additional_assignee_list List FALSE Original start date 1400 75 original_start_date Date Time FALSE Original end date 1500 75 original_end_date Date Time FALSE The Date fields are required to draw the Gantt Timeline. It is suggested to validate the Type of each column definitions too. Fire BR on Save: when checked for a particular column, the Save option will trigger the Update Business Rule. However not all business rules in the parent task will be triggered as they are saved with Workflow – false. The above-mentioned Planning Console Configuration is rendered as part of Metadata. Frequently Asked Questions How to add a new column to a Planning Console Open the Planning Console Column configuration for the entity (say Project)Create a new Display Column with Type equivalent to DB Column TypeCreate new Columns under the Display Columns for each Planning Console Table(s) to render from. How to include/add a new table to a Planning Console when having another child table (like Project Task) where you want get those tasks included in the Planning Console (under the Project) Check if the Table extends Planned Task Table.If No, we will not be able to render as it requires Planned Start Date, Planned End Date and Planned Duration Columns.If Yes, Table extends Planned Task Table Open the Planning Console Column configuration for the entity (say Project)Create a Table and Provide the relation columnFor Each of the Display Column(s), Create a Column definition for the same. How to use Project Planning for a different department with data seclusion. Refer Teampsace(s). Please note currently we have a limit of max 5 Teamspaces. Are Teamspaces charged separately? No. It is advisable to create individual project(s) than one main project and all sub projects underneath. Unable to view data in the Planning Console Contact SN support to debug the Planning Console Gantt Data.It is advisable to check the correctness of a project through the Project Diagnosis Tool related link in the Project form.Check if the Column Configuration are correctly defined. No duplicatesCheck the Column Configuration Types are correctly matching. Unable to view the columns Make sure the column configuration is correctly seeded. Unable to edit the column Check if the column is editable in column configuration. ACLs are not getting honoured Access rules are evaluated at the time of page submission.Make sure the Row Level and Column Level ACLs are defined correctly. Use of the Planning Console on custom tables There is a planning console seeded for project entities, and also for the planned task entities but read-only and not editable. ServiceNow does not encourage using custom tables on Planning Console, try to use Teamspaces instead. In order to use the planning console for custom tables, the practices below need to be followed: Table Naming convention Convention should have same prefix in the parent and child table Example: u_extended_project and u_extended_project_task. Create a App Configuration under the PM_APP_CONFIG Seed the Project and Project Task Table to above mentioned tables Create the Planning Console Column Configuration for these tables.Customization of the following Script Includes are required as default fallback to Planned Task PlanningConsoleProcessor MetadataPermissionsGanttData