Managing Strategic Planning with Project Portfolio Management, Agile Development 2.0, and SAFe

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Managing Strategic Planning with Project Portfolio Management, Agile Development 2.0, and SAFe

    This guide provides essential best practices and configuration guidelines to ensure seamless integration of Strategic Planning with Project Portfolio Management (PPM), Agile Development 2.0, and SAFe in ServiceNow. Proper configuration and management of table maps, field maps, and data synchronization are critical to maintaining data consistency across alignment and execution tables.

    Show full answer Show less

    Key Guidelines and Best Practices

    • Do not change filter conditions on table maps after records are interfaced: Changing filters post-integration can cause data inconsistency. If filters must be updated, manually adjust attributes on existing interfaced records accordingly.
    • Configure related field and choice maps when creating a table map: These ensure proper data mapping and synchronization between systems.
    • Avoid modifying table maps or field maps while import jobs are processing: Changes during processing can disrupt data integrity.
    • Use the Converted to field on planning items: This helps identify the original source record for traceability.
    • Set Lookup field and Lookup column values when execution and alignment tables reference different tables: This is necessary for reference or glide list field types in field maps.
    • Address data synchronization failures by checking:
      • Integration error logs on the alignment integration record.
      • Filter conditions on Alignment (import) and Execution (export) tables.
      • Active flags on both the alignment integration and table map.
      • Proper configuration of fields and choices in each table map.
    • Configure alignment planning item records to view the Execution URL field: If missing, use the “Fix execution URL(s) for planning items” action in the Integrations module to update missing URLs automatically.
    • Leverage the new Primary goal field in projects, demands, and epics table maps: This supports integration of the Goal field between alignment and execution tables.
    • Ensure demands associated with projects are synced during project import/export: This maintains consistency between related records.
    • Create custom table maps and supporting business rules when dealing with execution tables outside standard delivered tables (pmportfolio, rmepic, dmndemand, pmproject): Custom business rules are required to handle interfacing correctly for these cases.

    Practical Outcomes for ServiceNow Customers

    By following these guidelines, ServiceNow customers can:

    • Maintain data integrity and avoid inconsistencies when integrating Strategic Planning with PPM, Agile Development 2.0, and SAFe frameworks.
    • Ensure smooth data synchronization and traceability between alignment and execution layers.
    • Effectively manage integration errors and quickly resolve issues using diagnostic checks and automated fixes.
    • Customize data mappings and integrations confidently when extending beyond delivered tables.

    Ensure that Strategic Planning is integrated properly with PPM, Agile Development 2.0, and SAFe with these guidelines.

    • Do not change the filter condition of a table map after the records are interfaced. The already interfaced records might not match with the new filter condition and any change in the filter condition can result in data inconsistency. If you need to change the filter condition, ensure that the relevant attributes on the interfaced records are updated manually to avoid data inconsistency issues.
    • Whenever a table map is created, ensure that the relevant field maps and choice maps are also configured.
    • When an import job for a table map is running (processing), do not modify the table map or its field maps.
    • Using the Converted to field on the planning item form, you can identify the original record from which it was converted.
    • Ensure that the Lookup field and Lookup column values are added whenever the execution and alignment tables are referencing two different tables, while creating a field map for field type of reference or glide list.
    • If there is a data synchronization failure, check if:
      • The Integration error logs related list within that Alignment integration record.
      • The Alignment table filter (for import) and Execution table filter (for export) conditions are met.
      • The Active flag in both the alignment integration and the table map is checked.
      • The appropriate fields and choices are configured for each table map.
    • If you want to view the Execution URL field, configure the alignment planning item record to view it.
    • If the Execution URL field in your synced planning item(s) is blank, navigate to All > Strategic Planning > Integrations and select the required alignment integration. If any of the execution URL is missing, select the Fix execution URL(s) for planning items related link. This runs a job and updates the execution URL field.
      Note:
      The Fix execution URL(s) for planning items related link is only available when the execution URL is missing for any of the planning item.
    • A Primary goal field is introduced to the projects, demands, and epics table maps to support the integration of the Goal field between alignment and execution tables.
    • When you are trying to import or export a project, ensure that the demands (that are a part of that project) are synced.
    • You can create a table map for any execution table. If a table map is not created from one of the delivered tables (pm_portfolio, rm_epic, dmn_demand, pm_project) or does not extend from them, you are required to create a business rule to support the interfacing of the table map records. For more information on creating a business rule, see Create a business rule to apply a custom table map configuration.