2099261 - Make Content Dynamic Using lock-behavior-content tag - Competencies

• Can the behaviors on live forms be updated?
• How to we stop the behavior descriptions from changing on forms
• This KB article explains how lock-behavior-content behaviors can be configured to be either static or dynamic content on forms

Note: If lock-behavior-content behaviors are dynamic and you change the behavior description or behavior name in your competency library, the behavior description or name will also update on your live forms. Completed forms will not be affected by the status of lock-behavior-content.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors Performance and Goals

lock-behavior-content

• True or false (default is false)
• lock-behavior-content works for all competencies supported (job-specific, core and custom)
  • If lock-behavior-content is activated, update behaviors in your library won't change live forms that are in progress
• lock-behavior-content is an element that is configured on the PM template at the xml level that can be either true or false. It cannot be edited via admin tools at this time
• Behavior content will only update when someone physically opens the form, so unless users do that, reports may still show the old descriptions

Tip: Use the template open&save feature to trigger the update for mass forms. This applies to behaviors only and not competencies

behavior-mode-opt

• If behavior-mode-opt is set to 0, this attribute is assumed false
• If behavior-mode-opt is non-zero and this is set to false, behavior list is not hardcored to the form during form creation and form modification, and behavior list is linked to the corresponding competency
• In this case, when jobcode changes or behavior name/description is updated, the behavior for the existing form instances do reflect changes
• If behavior-mode-opt is non-zero and this is set to true, behavior list is hardcoded to the form during form creation and form modification, rather than being linked to the corresponding competency
• In this case, when jobcode changes or behavior name/description is updated, the behavior for the existing form instances do not reflect changes

SF, success factors, PMGM, PM, behaviors, lock-behavior-content, behavior-mode-opt, behavior, sf, performance management, lock , KBA , sf competencies & behaviors , LOD-SF-PM-FAM , Competencies Behaviors Families and Roles , How To