I have noticed different behavior, maybe issue, after upgrading APEX to version 19.2.
We have upgraded from version 4.2.
On page I have a button to submit it for some calculations.
The property of the button "Execute Validations" is set to "No".
On the form there are some other fields requiring any value - "Value required" is set to "Yes".
At the old APEX 4.2 the validation is not executed, but in new version of APEX 19.2 the validation is executed and the page shows an error message "Value of is required".
Have you any experience with such a confusing and annoying behavior?
BTW: I have found a workaround by using a javascript dynamic action for submitting a page when button is clicked. I am able to implicitly disallow executing of validations. Unfortunately we have quite a lot of applications with a lot of forms which are using this way of bypassing validations. So I am looking for standard way to solve a problem.
Thanks for ideas to help me to solve it.
Related
I'm creating a tabbed form with validation, and there is one thing I don't understand how to do: when I hit the submit button, and there is a validation error in some field, the form is not submitted - but if the field is in an hidden tab (a non focused one), there is no error message displayed either.
Is there am easy way to switch to the tab with errors, or to inhibith focusing on following tabs until all errors in current one had been cleared?
I'm new to all the React, JSX and modern JS development, please do not be too much concise! :)
Thanks!
I reproduced the problem and opened an issue on our repository. I'll let you know how it goes.
In the mean time, one way to mitigate this issue would be to create a custom saga. You'll need some knowledge about redux-saga though.
The idea would be to:
catch failed validations actions from redux-form (SET_SUBMIT_FAILED)
trigger a custom notification with an error message indicating the field and the tab where the error occurred. Unfortunately, you'll have to check the fields names to know for which resource the error occurred.
I have an apex program that i want to make a custom error page for it instead of the following default message that is been displayed when i call a non existing page.
apex version is 3.2
Thanks in Advance.
This is something I did in 3.x, but I'm not sure it would capture this particular scenario?
http://www.grassroots-oracle.com/2010/09/jquery-error-page-replacement.html
How are people opening pages that don't exist.
For every field (parameter) in my report, when using the PUC (Report Viewer), the PUC refresh the screen. It take quite a time and most of the reports i made have about 3-6 fields.
Searching in Pentaho Docs, i found this link that tells something about the Prompting API: http://wiki.pentaho.com/display/Serv...+Prompting+API.
But I have read all related pages and didn't find how to disable this reloading. It says that this behavour is to enable custom loadings parameters (like Country and State), but for me it's not necessary to have this kind of fields.
How could i disable this option? Note that i am not talking about auto update REPORT on selection, but auto update PARAMETER FIELDS.
Do i need to change the source code of some project or i can do that just by xml setting? I am not a developer so if there is a XML or related file it would be easyer to me.
See that my problem is not the "report reload" when i change a field, but is that the PUC refresh the screen to "reload filter configuration", as in its documentation. What i whant to do is to be able to type every parameter on the screen without having to wait for this loading, as you may know, you can not use "TAB" to fill this parameters, because of this reloads.
Thanks.
The refresh is handled by the JavaScript frontend. You can find the code in our GitHub repository and in your "pentaho-solution/system/reporting" directory.
However, the easiest way to disable the auto-submit checkbox and/or to set the auto-submit attribute on the master-report to false. This should positively prevent updates until you press the submit button.
There is no way to do that in the version i tried, pentaho dont suport disabling this feature...
Dont waste your time like me.
I am following the "Joomla! Programming" book by Mark Dexter and Louis Landry.
I came up to the point where we create a plugin to check whether both terms of service agreement and age above 18 is checked in the alternative registration form layout which we create earlier (approval.php).
When testing this plugin, I checked only one of the checkboxes and showed the "Registration Failed" error as expected. But on the error page, the registration form is the default one and not the alternative one which we created earlier (approval.php)
Why is this?
In the jqgrid 4.4.4 $("#myGrid").getGridParam("page"); to get the page number that user entered in the pagination text box.
But it returns the page number that was already present in that pagination text box.
Note: In the jqgrid 3.7.2 (+ jquery 1.4.2) it was working fine(ie returning the user entered value)
Anyone have suggestions and workarounds ?
(Now I am using jquery version 1.9.0 + jqgrid 4.4.4)
The following will give you the value:
$(".ui-pg-input").val();
this issue is occuring to my after upgrade to 4.4.4. The cause of the issue is basically the comit https://github.com/tonytomov/jqGrid/commit/3e4aa0f2fdcb8c2c2a17e842899aca6d1000410a
This commit changes the onpagin to execute BEFORE grid page calculation. In my current project I have reverted this lines so my pagination works again (I use external source binding). I propose to implement onBeforePaging and onAfterPaging, and each users can attach to the event they wants.