hclleapforum

Open full view…

builtin Dojo 'Loading' box for service calls

jabe08
Wed, 17 Jul 2019 15:57:51 GMT

Hello - I'm looking for a way to disable the built in Dojo loading box functionality which looks to be a newer feature (we are using version 9.2.0.15). I did not see an option for disabling this, i'm wondering if there is some JavaScript that can be placed in onStart or somewhere to disable it. The box more than occasionally gets 'stuck' which prevents the form from being interacted with further. Not exactly sure what's causing it. the console does not show any errors or issues. Basically, we have some JavaScript on a checkbox which triggers a service call to add Users from a closed group into a table on the form. Although the issue does not happen every single time, the Loading box that is triggered will stay active on the form and there is no other way to interact with the form besides refreshing the page. inItemChange of the checkbox: if (BO.getCurrentStage() === "ST_Start" || "ST_Return") { if (BO.F_sfcheckbox.getValue() === true) { if (BO.F_csrecount.getValue() === 1) { form.getServiceConfiguration("SC_sfrolelookup").callService(); BO.F_countofsyst ems.setValue(BO.F_countofsystems.getValue()+ 0); } else { if (BO.F_csrecount.getValue() === 0) { form.getServiceConfiguration("SC_sfrolelookup").callService(); BO.F_countofsystems.setValue(BO.F_countofsystems.getValue()+ 1); }}}} Any advice is appreciated. Thanks! [Loadingboxstuck](//muut.com/u/hclleapforum/s1/:hclleapforum:iAjz:loadingboxstuck.png.jpg)

Rob Lintern (HCL)
Wed, 17 Jul 2019 18:58:45 GMT

This sounds like a bug that we will look into. In the meantime, you can disable the "progress" indicator by unchecking the "Disable user action while running" checkbox on the "Details" tab for the service configuration..

Rob Lintern (HCL)
Wed, 17 Jul 2019 19:15:05 GMT

[Snap45](//muut.com/u/hclleapforum/s2/:hclleapforum:sNJw:snap45.jpg.jpg)

jabe08
Wed, 17 Jul 2019 19:42:10 GMT

Thanks for the reply Rob. I took a look and noticed none of the service calls i have currently have this checked, including SCfrolelookup in this example. See attached screenshot (Service Config). I went ahead and checked it off and then re-launched the form. the Loading box still behaves in the same way as described above. i did notice there is one service call that does not have the box checked, and the loading box does not show (as expected). The rest of them seem to have the the functionality of 'user input disabled while running' even though the box is not checked. Is there an option/setting in the Configuration file that may affect this? Some other background info, these are applications that currently work in a prior release (pre LEAP) that were imported into our LEAP 9.2.0.15 environment. Thank you. [Service Config](//muut.com/u/hclleapforum/s1/:hclleapforum:d76i:serviceconfig.png.jpg)

Rob Lintern (HCL)
Wed, 17 Jul 2019 20:19:44 GMT

This is looking like a product bug. Please file a support ticket so that we can work with you to bring it to resolution. https://hclpnpsupport.hcltech.com/csm

Rob Lintern (HCL)
Thu, 18 Jul 2019 00:50:09 GMT

Note: There are 2 issues here that we will fix: 1. The behaviour of "Disable user action while running” for existing apps defaults to _true_. This should be _false_. Until the fix is ready, one possible workaround is to Edit the app, Save the app (no changes are necessary), and then redeploy the app. 2. There is a race condition in the display of the progress indicator, that sometimes leads it to stay visible.

braudrick
Thu, 18 Jul 2019 14:28:12 GMT

We ran into the same issue when regression testing version 9.2.0.15 so we entered a ticket and have put our upgrade on hold until there is a fix. thanks

jabe08
Tue, 23 Jul 2019 12:49:09 GMT

just following up since I've been out of the office. We ended up submitting a ticket for this i believe last week. We also noticed a workaround for this is to re-create the service call in LEAP or (the easier way) just toggle the 'disable user action while running' checkbox on and then off, save and then deploy. We noticed this seems to happen (at least 1. in Rob's Notes above) when we import an application into LEAP.