This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring standard precedence rules for reconciliation

Standard precedence rules define precedence values for CDM classes and attributes. You can modify the standard precedence rules, or you can add new rules.

For example, if you have created class or attribute, you can add a precedence for it.

When you modify the standard precedence rules, you change the rules for all datasets and all jobs that use the standard precedence rules.

Before you begin

Understand how precedence values are used in Merge activities for more information see, Standard identification and precedence rules for reconciliation jobs.

To edit, add, or delete precedence rules for reconciliation

New Precedence set


  1. From the Reconciliation console, click Standard Rules Editor.
  2. In the Precedence tab, click Add or Remove Datasets from the Columns icon on the right to select the datasets that you would like to be displayed in the columns.
  3. Select the check box against the datasets that you would like to view, and close the box.
  4. If you are unable to locate the required class/attribute click on the Show All Classes and Attributes icon to display all the classes and attributes from all namespaces.
  5. From the Precedence Object column, navigate to the class or attribute to which you want to set a precedence rule.
    1. To add a rule - In the dataset column, double click the cell where you want to add the rule.
    2. To edit a rule - In the dataset column, double click the cell where you want to edit the existing rule.
    3. To delete a rule - In the dataset column, double click the cell where you want to edit the existing rule. Delete the value entered in the cell.
  6. To add or edit numeric value use the input slider, click 'X' to confirm the input and close. Alternatively, you can also type the numeric value in the cell and press enter.

The precedence rule is displayed in the cell that you added or modified.

Note:

If you click on any class or attribute displayed in the Precedence Object column, the Dataset order pane displays the datasets in which that class or attribute appears in the order of precedence.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Kanchanmala Thanekar

    Pt 2: The button is no more "+" sign, the button tooltip reads "Add or Remove Datasets from the Columns".

    Pt 4: The button tooltip is "Show All Classes and Attributes" instead of Class/Attribute button.

    Pt 4: Instead of "all the classes and attributes from all datasets" it should be "all the classes and attributes from all namespaces"

    Oct 16, 2012 03:34
  2. Karl Halleni

    For 5c:  The entry with the attribute will still be visible but with a NULL value. How to get the entry completely removed from the list?

     

    Thanks

    Karl =)

    Nov 04, 2014 08:37
    1. Prachi Kalyani

      Hello Karl,

      Thank you for your comment. I will verify this with the concerned SME and get back to you.

      Thanks,

      Prachi

      Nov 05, 2014 05:13
      1. Karl Halleni

        Hi Prachi,

        You don't need to bother, I found out that if I hit <Enter> after setting the field to NULL value it works as expected. (smile)

        Thanks

        Karl =)

        Nov 05, 2014 05:56
  3. Worawut Ekarat

    Where do you update Defer if NULL setting from here? Or, is it available only from the legacy console?

    Nov 11, 2014 01:45
    1. Karl Halleni

      Double click the field keeping the precedence value of interest, out on the right hand side you have a down arrow between "1000" and the "quit cross" Click this down arrow and the option for Defer if NULL will appear

      Karl =)

      Nov 11, 2014 01:55
      1. Worawut Ekarat

        Thanks, Karl. There is no 'down' arrow in my system running on 8.1.01, though.

        Do you have a page that said this specifically? I was trying to find it, but this one is the closet I can get to it.

        Nov 11, 2014 02:11
  4. Jason Ho mok cheong

    Hi Karl,

    Looking further into this, it seems that the slider down arrow is only available if you open the form from the merge activity. However, it is not there if you open it from the Standard Rules Editor.

    The screenshot in step #6 looks incorrect, it shouldn't have the down arrow present correct? Is it possible the screenshot was taken from the merge activity rather? This is misleading users into thinking the options are available from the Standard Rules Editor when it's not visible.

    Steps to reproduce:

    Test # 1 - Slider shown with down arrow and includes 3 options

    Reconciliation Console > Select a Dataset > Edit Job > Select the Merge Activity > Edit Activity > Under Precedence click on Edit > Double click on one of the columns (i.e. BMC Asset column for one of the dataset) > The slider is shown with the down arrow and includes the 3 options.

    Test # 2 - Slider shown but no down arrow

    Reconciliation > Standard Rules Editor > Double click on one of the columns (I.e BMC Atrium Explorer) > Slider will display but there is no down arrow which shows the 3 options.

    Regards,

    Jason

    Nov 11, 2014 10:48
    1. Karl Halleni

      Hello Jason,

      You're correct, am not able to see the down arrow in the Standard Rules Editor. Here BMC need to step in and let us know the design idea.

       

      Thanks

      Karl =)

      Nov 12, 2014 02:04
      1. Amol Redij

        Hello Karl,

        Thank you for your comment. I will verify this with the concerned SME and get back to you.

        Thanks,

        Amol

        Nov 12, 2014 02:34
  5. Simon Lansbury

    In the opening text of this page, it states:

    When you modify the standard precedence rules, you change the rules for all datasets and all jobs that use the standard precedence rules.

    My organisation is on Remedy on Demand v8.1 and I have found this not to be true. I can't find any jobs whose Precedence rules are updated after I make a change using the Standard Rules Editor.

    Also if I create a new set of Precedence Rules for a job, all the datasets are set to value 100, and no specific CI Type or Attributes have a values set.

    Am I doing something wrong?

    Or is there a bug in Remedy 8.1?

    Apr 20, 2015 11:57
    1. Amol Redij

      Hi Simon,

      Thank you for your comment.

      I will have a discussion about this with the concerned SME and update you as soon as possible.

      Regards,

      Amol Redij 

      Apr 21, 2015 12:32
  6. Simon Lansbury

    I got a notification that Amol commented on this, but apparently that text is only available to BMC employees, was that intentional or was I supposed to see the reply?

    Apr 21, 2015 12:50
    1. Amol Redij

      Hi Simon,

      I have discussed your comment with the SME. The issue might need some further investigation and diagnosis.

      The Customer Support team can help you with this issue. To contact Customer Support, click here.

      Regards,

      Amol

      Apr 22, 2015 02:28
      1. Simon Lansbury

        I've found out what's causing the issue from support yesterday.

        Precedence values for a specific dataset are copied from the Standard Rules Editor into BMC Default Merge Precedence Set when there is a reconciliation job using that dataset as a source dataset.

        In my case, I was trying to set values for BMC Asset and they were not being copied into BMC Default Merge Precedence Set because we didn't have any job where BMC Asset was the source dataset.

        I'm blown away that this is how it works, I can't understand why editing the precedence values doesn't just update the BMC Default Merge Precedence Set. Why does a job need to exist which has that dataset as a source?

        Precedence values affect the way CI attributes are updated between a source and a target, it doesn't only affect the source.

        Apr 22, 2015 06:37