Scheduled Script Execution form

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 3 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 Scheduled Script Execution form

    The Scheduled Script Execution form in ServiceNow's Strategic Portfolio Management facilitates automated data migration and management tasks related to goals, strategies, and work items. This functionality is crucial for transitioning legacy data into the Goal Framework, ensuring a seamless integration within Strategic Planning.

    Show full answer Show less

    Key Features

    • Migrate Goal Data: Transfers existing goal records from the Goal table to the Goal Framework tables, maintaining the original sysid and establishing relationships with work items.
    • Migrate Strategy Data: Moves strategy records from various tables into the Strategic Priority table while preserving sysid integrity.
    • Migrate Goal-Strategy M2M Data: Handles cloning of goals when multiple strategies are mapped, creating a hierarchical structure of parent and sub-goals.
    • Migrate Strategy Work Item Relationships: Establishes relationships between strategies and work items, generating dummy goals when necessary to ensure data completeness.
    • Migrate Goal Relationships for Assigned Entities: Updates the Assigned entity type and Assigned entity fields on the Goal form based on existing legacy relationships, accommodating non-standard entities.

    Key Outcomes

    By utilizing the Scheduled Script Execution form, customers can expect streamlined data migration processes, improved goal management, and enhanced visibility into strategic alignment. This automation ensures that all relevant relationships and data structures are maintained, enabling more effective portfolio planning and oversight.

    Scheduled Jobs are automated pieces of work that can be performed at a specific time or on a recurring schedule.

    Migrate Goal, Strategy, and Work item data to the Goal Framework and related Planning item tables

    Use the Migrate Goal, Strategy, and Work item data to the Goal Framework and related Planning item tables job to migrate the existing goals data to the Goal Framework tables.

    Table 1. Scheduled Script Execution form
    Parameter Description
    migrateGoalData
    • Migrates all existing goal records from the Goal [goal] table to the Goal [sn_gf_goal] table. The sys_id remains the same. The corresponding target records will be created in the Target [sn_gf_goal_target] table.
    • Creates the existing relationship between the goal and work items (Project, Demand, Program) in the Goal Relationship [sn_gf_goal_m2m_relationship] table with the first goal (from the order in the glide list) as the primary goal.
    migrateStrategyData Migrates all existing strategy records from the Enterprise Strategy [enterprise_strategy], Business Unit Strategy [business_unit_strategy], and Strategic Objective [strategic_objective] tables to the Strategic Priority [sn_gf_strategy] table. The sys_id remains the same.
    migratingGoalStrategyM2Mdata In Goal Framework, a goal can be mapped to only one strategy. If an existing goal has two strategies mapped to it, a clone of the goal will be created (one as a generic goal and another as a sub-goal) with the same strategy populated for both. And, for the sub-goal, the first goal will be set as the parent goal.

    For example, consider a scenario where an existing goal (G1) is mapped to five strategies (S1, S2, S3, S4, and S5). Then, four clones of G1 will be created as sub-goals (G2, G3, G4, and G5) and the parent goal is populated as G1. For the parent goal (G1) and the sub-goals (G2, G3, G4, and G5), the Strategy field is populated respectively (S1, S2, S3, S4, and S5).

    Note:
    The name of the cloned sub-goal will be prefixed with Cloned SubGoal:, followed by the parent goal name.
    migrateStrategyWorkItemRelData
    • Migrates the existing relationship of strategy and work items (Project, Demand, Program) to the Goal Relationship [sn_gf_goal_m2m_relationship] table.
    • If a goal doesn't have an association between the strategy (as current strategy) and the work item in the Goal Relationship [sn_gf_goal_m2m_relationship] table, a dummy goal will be created with a strategy value of current strategy. And, a goal relationship is created with the dummy goal and the work item in the Goal Relationship [sn_gf_goal_m2m_relationship] table.
      Note:
      The name of the dummy goal will be prefixed with Goal:, followed by the strategy name.

    Migrate goal relationships for assigned entities

    Use the Migrate goal relationships for assigned entities job to populate the fields, Assigned entity type and Assigned entity on the Goal form based on the existing values in the legacy fields, Business Unit, Department, Company, Portfolio, and any customized entity field.

    Table 2. Scheduled Script Execution form
    Parameter Description
    Migrate goal relationships for assigned entities (For Strategic Planning users) Populates the fields, Assigned entity type and Assigned entity on the Goal form based on the data in the Goal Relationship [sn_gf_goal_m2m_relationship] table if you've created an m2m relationship with lens entities other than Company, Business Unit, Department, and Portfolio.

    If users had already created m2m relationship, they may use this script to move those relationships from the m2m table to the goals table to access and manage those goals in the respective portfolio plans.

    If the goal has only one relationship with an assign entity table type, the Assign entity type and Assign entity fields are populated on the Goal [sn_gf_goal] table based on the Goal Relationship [sn_gf_goal_m2m_relationship] table.

    If the goal has multiple relationships with an assign entity table type, number of relationships (n) cloned sub-goals will be created and the Assign entity type and Assign entity fields are populated on the Goal [sn_gf_goal] table based on the data in the Goal Relationship [sn_gf_goal_m2m_relationship] table for each cloned sub-goal.