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 guidance ensures proper integration of Strategic Planning with Project Portfolio Management (PPM), Agile Development 2.0, and SAFe within ServiceNow. It provides best practices to maintain data consistency and synchronization across strategic planning and execution tables, facilitating smooth interfacing and accurate alignment of planning items.

    Show full answer Show less

    Best Practices for Integration

    • Do not change table map filter conditions after interfacing: Altering filters post-interfacing can cause data inconsistencies. If changes are necessary, manually update relevant attributes on interfaced records.
    • Configure related maps fully: When creating a table map, also configure all associated field maps and choice maps to ensure comprehensive data mapping.
    • Avoid modifying maps during import jobs: Do not change table or field maps while an import job is running to prevent synchronization issues.
    • Use the 'Converted to' field: Identify the original records from which planning items were converted for traceability.
    • Properly configure lookup fields and columns: Especially when execution and alignment tables reference different tables, ensure lookup field and column values are specified in field maps for reference or glide list types.

    Troubleshooting Data Synchronization

    If data synchronization fails, verify the following:

    • Check integration error logs in the Alignment integration record.
    • Ensure alignment and execution table filters for import/export are correctly set.
    • Confirm the Active flag is enabled in both alignment integration and table maps.
    • Verify that all necessary fields and choice maps are configured for each table map.

    Additional Configuration and Features

    • Execution URL field visibility: Configure the alignment planning item record to view the Execution URL. Use the "Fix execution URL(s) for planning items" link in the Strategic Planning Integrations module to populate missing execution URLs automatically.
    • Primary goal field support: Projects, demands, and epics table maps now include a Primary goal field to integrate Goal information between alignment and execution tables.
    • Demand synchronization: When importing or exporting projects, ensure that associated demands are also synced to maintain data integrity.
    • Custom table map business rules: For table maps not based on delivered tables (pmportfolio, rmepic, dmndemand, pmproject) or their extensions, create a business rule to support record interfacing.

    Practical Impact for ServiceNow Customers

    By following these guidelines, customers can confidently integrate strategic planning with PPM, Agile Development 2.0, and SAFe, ensuring consistent data flow and alignment between planning and execution layers. This enables more accurate portfolio management, better tracking of planning items, and reduces errors caused by data inconsistencies during synchronization processes.

    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 for custom table map configuration.