CA Service Management

  • Private Community

  • 1.  Default value not working for Property Validation Rule

    Posted Apr 19, 2019 11:40 AM

    Hello Experts,

     

    We use properties under Request/Incident/Problem Area. I created a property and associated with a Property validation rule (dropdown). The validation rule having a default value. However when I am trying to create a new Incident with that same Incident Area, the default property dropdown value is not auto field.

     

    I tried with several combination but same result and seems like default value feature is not functional. We are using r14.1. But I tried in r17.1 as well and found the same issue. Is it a bug? If yes, what is the fix?

     

    Thanks

    ArunavaS



  • 2.  Re: Default value not working for Property Validation Rule

    Broadcom Employee
    Posted Apr 22, 2019 10:02 AM

    Arunava, I maybe miss something here as I don't seem to recall there is a default value for property validation rule...is it something you customize? Thanks _Chi



  • 3.  Re: Default value not working for Property Validation Rule

    Posted Apr 23, 2019 01:47 PM

    I believe this is a CA OOTB feature.

     



  • 4.  Re: Default value not working for Property Validation Rule

    Posted Apr 25, 2019 06:07 AM

    Am I not clear in this context !!



  • 5.  Re: Default value not working for Property Validation Rule
    Best Answer

    Broadcom Employee
    Posted Apr 30, 2019 12:01 PM

    Arunava, thank you. My mistake that said can't recall default. I quickly tested this on a 17.1.02 and this part behaviors weird...if I set the rule to have value required it will not populate the default value; if I set the rule to not have value required it does populate the default value. I am not sure if this works as designed or a bug. Please open a Support case to have this sorted. Thanks _Chi



  • 6.  RE: Default value not working for Property Validation Rule

    Posted Jul 24, 2019 09:18 AM
    Hi Arunava,

    Hope you have already sorted this issue with support. I happen to stumble with the same thing and got the answer in this KB article:

    https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=49668

    so the logic given is:

    From R12 release only on, this behavior changed: it's been decided to change the way defaults for properties work.

    The behavior exhibited is working correctly.

    Dropdown will show "<empty>" on the User Interface. This will enable user to really enter some value when the property is set as "Required".

    So, if you want the property to be set as "Required", do not set any default values to the property. This will enable users to enter some value to the properties.

    Or, if you want the property to be set to some default value when creating a ticket, then do not set the property associated with the Request Area or Category as "Required".

    Cheers!!


    Original Message