Business Rule Query checkbox not selectable

Katie A
Mega Guru

Hello, I am attempting to create a Before Query Business Rule. However, the 'Query' checkbox does not activate at all when clicked on.

I believe this might be a bug in Fuji. We recently upgraded to Fuji from Eureka.

I have tried the following troubleshooting steps:

* Enabling debug and examining Security ACLs and Business Rules

* Various different browsers

Note: The existing Query Business Rules that were in the system prior to the upgrade are working and the checkbox is checked. The issue impacts NEW Business Rules.

Screen Shot 2015-08-01 at 3.39.47 AM.png

1 ACCEPTED SOLUTION

Katie A
Mega Guru

Ok the issue was the UI Policy "Hide advanced controls".



Strangely enough, the Query checkbox was still visible on the form, but it was being disabled by that UI Policy, thus it wasn't selectable.



I had to configure the layout to enable the Advanced checkbox and enable that option and then the Query button was selectable.



Thanks for all of the suggestions everyone!


View solution in original post

6 REPLIES 6

Mike Allen
Mega Sage

We recently upgraded, as well, and I cannot replicate what you are seeing.   You may want to open a HI ticket on this one.   I wonder if something erred in your upgrade that they can easily spot and fix.   It is not the tell tale grey that tells us it is RO, so I am not sure what it could be.


bernyalvarado
Mega Sage

Hi Kathryn, do you checked if you already had select the table of the business rule or is it a global business rule? If the table is global or if it's not selected then it's possible that the query checkbox gets disabled.



Thanks,


Berny


Anurag Tripathi
Mega Patron
Mega Patron

Hi Kathryn,



These come on top of my head,



1) Right click on the field, query check box, and go to the dictionary , check if its marked "readonly" on the dictionary itself,


2) Check the ui policies/client scripts on sys-script table


3) Check all ACL on sys_script


-Anurag

Kalaiarasan Pus
Giga Sage

Just a guess here...



Se if the field is added to more than one section .. I had seen this issue on one of the demo instances long back and removing the field from one of the section solved the issue ....