Choice controls remain active after disabling the View on a Form

  • 16 February 2021
  • 0 replies
  • 36 views

Userlevel 5
Badge +20
 

Choice controls remain active after disabling the View on a Form

KBS100104

PRODUCT
K2 Five 5.0
K2 blackpearl 4.7
BASED ON
K2 blackpearl 4.7
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.

Issue

When disabling a View on a Form using a Form Rule, Choice Controls still remain active when they are set to Display Type: Check Box List or Radio Button List.

Symptoms

When a Form Rule is used to disable the View and the actions are executed asynchronously, the Choice Control will not be disabled.

 

 

The following rule configuration will result in the issue:

 

When the Form is Initializing
then start the following asynchronously
asynchronously on ChoiceView View, execute the Initialize method (configure)
asynchronously disable ChoiceView View

 

In Runtime, the Form containing the View will display as follows:

Image

Resolution

A bug item was logged with the Developers. A fix should be included in a future update for K2.

 

The issue appears to be related to the "asynchronously Initialize the View" Rule on the Form, and only when Choice Control is set to Radio Button List or Check Box List.

 

The following workarounds are suggested:

Workaround 1 is to make the Form rule execute synchronously (then complete the following one after another). This will have an impact in terms of potential UI lockup. The UI will wait for all the controls to load in before removing the spinner. This will become more apparent if large lists of data is fetched for each control being populated.

 

When the Form is Initializing
then complete the following one after another
then on ChoiceView View, execute the Initialize method (configure)
then disable ChoiceView View

 

Workaround 2 is a design consideration: Use a Choice Drop-Down List in place of a Choice Radio Button List or Choice Check Box List.
Performance wise, this would be the best, but it might not be the preferred user experience.


Workaround 3 is to disable the view and then disable just the control in a separate action.
This results in an insignificant negative performance impact.

 

When the Form is Initializing

then start the following asynchronously
asynchronously on ChoiceView View, execute the Initialize method (configure)
asynchronously disable ChoiceView View
asynchronously on ChoiceView View, disable Choice control

 


0 replies

Be the first to reply!

Reply