Migrate existing goals data to Goal Framework

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read

    • With the admin role, you can migrate the existing goals data to the Goal Framework tables by running the scheduled job.

    Before you begin

    Role required: sys_admin

    About this task

    If you are an existing user of IT Business Management, then you must migrate your existing goals to the Goal Framework. New customers automatically have the new framework and they do not need to run the job mentioned in this procedure.

    Procedure

    1. Navigate to All > System Definition > Scheduled Jobs.
    2. Search and click the Migrating Goal, Strategy, and related Work Item data to the new tables scheduled job.
    3. On the Scheduled Script Execution form, perform the following steps:
      1. Ensure that the frequency is selected as On Demand in the Run field.
      2. Set the value to true for the required parameters in the Run this script field.
        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 as the primary goal.
        Note:
        Only existing goal records that have the Direction field populated on the Goal [goal] table are migrated to the Goal [sn_gf_goal] table.
        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 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 does not 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.
    4. Click Execute Now.