none
[MS-OXORULE / MS-OXPROPS] Data type for PidTagRuleCondition and PidTagRuleActions RRS feed

  • General discussion

  • Hi,

    I'm looking at Rules, and there appears to be a conflict in MS-OXORULE (v1.03).
    2.2.1.3.2.9
    PidTagRuleCondition
    Type: PtypServerEntryId
    The condition used when evaluating the rule. The condition is expressed as a Restriction (as specified in [MS-OXCDATA]) and the PropertyValue buffer contains the Restriction structure packaged as specified in [MS-OXCDATA] (using 2-byte sized COUNT values).

    2.2.1.3.2.10 PidTagRuleActions
    Type: PtypServerEntryId
    The set of actions associated with the rule. Its structure is specified in section 2.2.5, using a 2-byte sized COUNT value.


    Those types (on the "Type:" line do not appear correct. PidTagRuleCondition should be a PtypRestriction (0x00FD), and PidTagRuleActions should be a PtypRuleAction (0x00FE).

    Similarly, in MS-OXPROPS, we have:
    2.1016
    PidTagRuleActions
    Canonical name: PidTagRuleActions
    Property ID: 0x6680
    Data type: PtypServerEntryId, 0x00FE
    Area: Server-Side Rules Properties
    References: [MS-OXODLGT], [MS-OXORULE]
    Alternate names: PR_RULE_ACTIONS, ptagRuleActions

    and
    2.1018
    PidTagRuleCondition
    Canonical name: PidTagRuleCondition
    Property ID: 0x6679
    Data type: PtypServerEntryId, 0x00FD
    Area: Server-Side Rules Properties
    References: [MS-OXODLGT], [MS-OXORULE]
    Alternate names: PR_RULE_CONDITION, ptagRuleCondition


    Where the values are correct, but the text is incorrect.

    Brad

    Friday, April 10, 2009 2:38 AM

All replies

  • Brad,

    A quick check and yes the types are incorrect.  I will file a TDI to get this corrected.


    Developer Consultant
    Friday, April 10, 2009 5:02 AM
    Moderator