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

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 in ServiceNow Zurich release. It focuses on maintaining data consistency and synchronization during interfacing and managing records between alignment and execution tables.

    Show full answer Show less

    Key Guidelines for Integration

    • Filter Conditions: Avoid changing filter conditions on table maps after records are interfaced to prevent data inconsistency. If changes are necessary, manually update relevant attributes on existing records.
    • Table, Field, and Choice Maps: Always configure field and choice maps when creating a table map. Do not modify table maps or their field maps during an active import job.
    • Reference Fields: When alignment and execution tables reference different tables, ensure Lookup field and Lookup column values are included in field maps for reference or glide list fields.
    • Data Synchronization Checks: In case of synchronization failures, verify integration error logs, filter conditions on alignment and execution tables, active flags on alignment integration and table maps, and correct field/choice map configurations.
    • Execution URL Management: To view or fix missing Execution URL fields on synced planning items, configure alignment planning item records accordingly and use the “Fix execution URL(s) for planning items” job accessible from the alignment integration record.
    • Primary Goal Field: Introduced on projects, demands, and epics table maps to integrate the Goal field between alignment and execution tables effectively.
    • Demand Synchronization: When importing or exporting projects, ensure associated demands are also synced to maintain consistency.
    • Custom Table Maps: Table maps created for execution tables outside the delivered core tables (pmportfolio, rmepic, dmndemand, pmproject) require a business rule to support record interfacing.

    Practical Benefits for ServiceNow Customers

    • Maintains data integrity and consistency across strategic planning, project portfolio, agile, and SAFe workflows.
    • Provides clear steps to troubleshoot synchronization issues and manage execution URLs effectively.
    • Ensures alignment between strategic goals and execution records through enhanced field mapping.
    • Supports extensibility with custom table maps by defining necessary business rules for seamless integration.

    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.