Unable to setup approval process configuration records with same phase name, with unique criteria.

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy Change Management Application


    APPLIES TO:

    BMC Remedy Change Management Application



    PROBLEM:

     

    I am trying to accomplish the following:

    Create an approval process configuration set of records that will allow change process for specific change type to bypass stages that are not needed.

    EX) Change Type = Change. I want change ticket to move from Request for Authorization stage to Scheduled For Review (as long as no approvals needed). Then go from Scheduled for Approval to Scheduled Status, looking for approval (which should be valid).

    I thought to accomplish this by creating 2 approval process configurations:

    1) Form Name = Infrastructure Change, Company = Global, Status = Enabled
    Phase Name = Change Approval Process
    Process Name = Change Level - Review
    Impacts Approval Status = Yes
    Status Flow: Begin = Request for Authorization, Approved = Scheduled for Review, Rejected = Rejected, No Approvers = Scheduled for Review.
    Change Type = Change

    2) Form Name = Infrastructure Change, Company = Global, Status = Enabled
    Phase Name = Change Approval Process
    Process Name = Change Level - Implementation
    Impacts Approval Status = Yes
    Status Flow: Begin = Scheduled for Approval, Approved = Scheduled, Rejected = Rejected, No Approvers = Scheduled.
    Change Type = Change

    System won't allow me to save this, because it thinks these two rules are not unique. Receiving error:

    This record already exists. Please verify or reselect your field entries and try again. (ARERR 40000)

      
      BMC Remedy Change Management Application 7.x & AR System 7.x (version 7.0.03) 
      
      n/a 

     


    SOLUTION:

     

    Legacy ID:KA297399

      
      Error was being generated because of the duplicate phase names. Once the phase name was changed to be unique, items were able to be saved. Also made a side note recommendation to create new custom approval processes for their company and leave the Global approval processes untouched even if not using multi-tenancy. This will always allow for easier restoration of out of the box approvals if needed.  

     


    Article Number:

    000070090


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles