×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC FootPrints Service Core 12.1 ... Migrating from FootPrints version 11.x Components that are not implemented or migrated

Reviewing escalations with Checkbox Field criterion turned off

This topic is for troubleshooting escalations with Checkbox Field criteria set to off while migrating from FootPrints version 11.0 to FootPrints version 12.0.

Description

The following table describes Checkbox Field criteria in FootPrints 11.0 and FootPrints 12.0.

FootPrints 11.0FootPrints 12.0
  • A Checkbox Field has three possible values including On, Off and Null.
  • A Null value occurs only in tickets, which already existed when the Checkbox Field was added.
  • You can select On, Off, Off (incl. null values), and Ignore.
    The following image displays Checkbox Field.



  • The Check Box fields are of type Boolean with two possible values:
    On (selected) and Off (deselected). A Null value is not possible.
  • The rule criteria for a checkbox field allows you to specify only On or Off.
    The following image displays Checkbox Field.
  • The Off and Null values are migrated as Off.
  • The escalations with Checkbox Field criteria set to Off can result in escalation of additional tickets, which would not have escalated in FootPrints version 11.0.
  • The tickets that have a null value in FootPrints version 11.0 are turned off.
  • This does not apply to On create rules, because tickets created in the past can never again be affected by On create rules. The newly created tickets will never have a Null value in the Checkbox Field.
UI location: Administration> Workspace> Escalation> (escalation) > Issue CriteriaUI location: Administration > Workspaces > (workspace) > Record Definitions > (ticket) > Business Rules > (rule) > Criteria

Resolution

To resolve this issue, review your escalations containing the Checkbox criteria set to Off in FootPrints version 11.0 and analyze tickets data in Checkbox fields. It is possible that this issue could have little or no adverse impact on your system, if the tickets with Null in the checkbox field are presumed to be no longer active or relevant and are not expected to be escalated. Consider the following points.

  • You may probably not need to make any changes, if there are no FootPrints 11.0 tickets, whose Checkbox Field is Null. However, you should still review and test your rules.
  • Consider following points, if the Checkbox Field is set as Off for a few tickets and Null for other tickets. The Null and Off values have different business meanings.

    1. Identify an additional criteria that can be used to distinguish the tickets that must be escalated.

    2. Analyze whether your purpose can be achieved by using a drop-down choice field with three choices instead of the Checkbox Field.

    3. Consider the need to keep the Checkbox Field for historical purpose or how other FootPrints features might be using the Checkbox Field.

  • Before activating the Checkbox field in a production environment, activate and test your migrated escalation rules.
Was this page helpful? Yes No Submitting... Thank you
Last modified by Pallavi Tayde on Mar 20, 2017

Comments

Log in or register to comment.

Reviewing escalations set to not re-escalate
Configuring settings for Active Directory Password Reset
<copyright information for the space>
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.