Please share any other relevant files that may be required (for example, logs).
N/A - no errors encountered, this is a configuration question.
Share all details about your problem, including any error messages you may have received.
Steps we have tried:
Set batchRequestGenerateIdentityRequests to true in SystemConfiguration via Debug (confirmed the entry exists and shows <Boolean>true</Boolean>).
Submitted a 'Reset Miscellaneous Caches’ request via System Caches.
Restarted Tomcat on both UI and Task servers.
Hard-refreshed the browser (Ctrl+F5).
After all of the above, the checkbox still renders unchecked on page load. We suspect the backing bean (BatchRequestScheduleBean) does not read this SystemConfiguration key to initialise the UI default.
Is there a supported configuration setting (SystemConfiguration, UIConfig, Global Settings, or otherwise) that controls the default state of this checkbox? Or is this hardcoded in the bean and requires a page-level customisation?
Hi @acgsneddon - I believe there is only one way to do that.
Edit the createBatchRequest.xhtml file under manage>batchRequest.
Add the following line to the script:
jQuery(‘input[id$=“generateIdentityRequests”]’).prop(‘checked’, true);
Note that you will need to add this to your build and make sure it persists with any patches or upgrades. Not technically supported but is a simple customization.
I would suggest to do it via plugin, basic small plugin which gets invoked at this jsf page only, and the generate identity request checkbox is always checked.
just invoke the plugin at this page, and make sure checkbox is turned on.
It is always easier to make the changes using plugin, instead of making changes in the .xhtml file on the server.
Thank you both for taking the time to respond — really appreciate the input.
Just a quick update: due to other in-flight work I haven’t yet been able to test or implement either suggestion, so I don’t have any new findings to share at this stage. I wanted to acknowledge your replies rather than leave the thread sitting silent.
For visibility on next steps:
I’ll be looking to apply Ryan’s suggested change to createBatchRequest.xhtml (under manage/batchRequest) — adding jQuery(‘input[id$=“generateIdentityRequests”]’).prop(‘checked’, true); to the existing Ext.onReady script — in a lower environment first.
I’ve also noted Naveen’s recommendation to deliver this via a small plugin rather than editing the shipped .xhtml directly, as it’s more upgrade-safe. I’ll weigh that against our current customisation/build process before deciding the final approach.
Either way, I’ll come back to the thread with results (and mark a solution) once I’ve had the chance to test properly. If anyone else lands here in the meantime with experience of the plugin-based approach for this specific page, I’d be glad to hear it.
@acgsneddon It is recommended to go with plugins with any xhtml changes, to avoid any version related issued during mismatch.
However in this specific case, you should go ahead with xhtml changes directly, as it is just one line change. Basically you need to figure out how big a change is and whether it is worth putting effort on plugins.
In case post upgrade something changes, you again need to do the same changes in xhtml or plugin. So whatever path you go, if something changes, you need to make the change.
@acgsneddon I definitely did not have plugins on the brain , but that is the way to go. Here is a very simple one that will inject that js only that page. You can play around with to see if it meets your needs. I have it working on 8.4
, but that is the way to go. Here is a very simple one that will inject that js only that page. You can play around with to see if it meets your needs. I have it working on 8.4