How can I clear just enabled fields from FormPanel? - gxt

I have a form panel (GXT from Sencha) with 3 fields. One of them is disabled. I want to implement clear button which will clear just enabled fields and will leave the value of disabled field. How can I do this?

Related

Can I make checkbox required?

According to answer https://support.docusign.com/s/question/0D51W000069k9V3SAI/how-to-make-a-checkbox-mandatory checkboxes are always optional fields when signing. But this answer was 2 years ago.Is it possible to make a checkbox required now?
Checkbox can be either checked or unchecked.
You can decide what is the default. Change it to checked.
If you mean you want the checkbox to be always cheked - it has to be readonly and marked checked by your code.

Powerapps - Make a single field editable and all fields viewable in a Form

I want to make a single field editable(Display mode.Edit) and make all other fields viewable (FormMode.View) in Powerapps.
Will the FormMode override DisplayMode of fields.?
In my case, when I tried, every fields get viewable when I give FormMode.View.
You cannot override Edit mode for View mode.
You will need to use disable property of each of your Field on Form to disable it (read only).
Look into this thread.

In angular-formly hideExpression remove fields from the DOM but not from the MODEL

When fields are remove from DOM due to hideExpression, its values in the model still exits and send on submit.
Using
angular-formly v8.4.1
angular-formly-templates-bootstrap version 6.5.1
¿How can I remove hidden Fields from de model or set them as null?.
Here you have an example of the problem:
http://angular-formly.com/#!/example/field-options/hide-fields
I want the checkbox state do not send in the model if checkbox is hidden.
Because if this checkbox is used for hide another third field, if we hide checkbox while is checked (using a hideExpression on it) this third field still show in the DOM which is a bit weird behavior because if checkbox is removed the third dependen field must be removed.
I have been able to observe that by simply putting null in the model the fields that are no longer in the DOM perfectly hide the dependent fields in chain
Please help to refresh model when hide fields.
Thank you in advance (sorry my bad English)
set it to use ng-if as the hideDirective in the formly-form

Issue related to Kentico on-line form (bizform) validation

I have created a form using Kentico on-line form and applied the built-in "required" validation on it. Whenever a textbox is empty then a required validation is shown. Now, I have entered a value in the textbox and press tab from the keyboard but the required message does not disappear. I want to remove or hide the message from the form when the user enters a value in the text box before the submit button is clicked.
How to resolve this issue?
I don't recall this being something that Kentico handles out-of-the-box. You'll most likely need to add some custom client-side script for this. Typically - where I work, at Ridgeway - we use custom layouts for forms, as the standard layout is fairly table-rich.

Best practice in dealing with xpages extensions dialog box?

I have an extension pages dialog box that I placed in a custom control. The dialog box is used to search for cost centers and return information such as market, cost center number, cost center name etc.
A "Select" button is pressed and the dialog box appears. The user searches for and selects their cost center. The OK button is pressed and it closes the dialog box and updates the various fields on the xPage.
A couple of questions.
Currently the "Select" button on the CC needs to know and refer to the name of the dialog box control within the CC. Seems to me that this is not the best practice. My end user programmer needs to know the ID of that dialog box control within the CC. Is there any way for my "Select" button could "show" the CC and the CC would actually show the dialog box control?
My CC makes use of custom properties to store the various document fields from the selected cost center. The OK button then uses these properties to set the various fields on the xPage. This again does not seem to be a best practice. If I wanted to use that CC in another application then I might need to edit the code in the OK button. Is there a better way to deal with this? Like I can set properties for a CC when I drop it on my xPage, is there a way I can tell it the code that I want to execute when the OK button is pressed?
One thing I thought was to have properties for the fields that need to be updated by the OK button but that does not seem to be so flexible.
For the issue of needing to know the id not sure if theres a typo but I don't understand why its bad that a select button inside a cc needs to no the id of the dialog to open it? did you mean the select is outside the cc? either way have you tried anything like creating a property on the custom control so that from outside it you can set something maybe
<xc:mycustomControl showDialog="false">
and then when something outside it happens change showDialog and refresh the cc, then inside the cc you can have a before / after page load to determine what happens when showDialog is true / false.
For your second issue it sounds to me like this should be using a domino document structure. Rather than the dialog pulling out each piece and the ok button updating, what I would do is have a domino doc data source on the page. when something is selected through the dialog I would update the document this source is pointing to and have all the fields bound to what ever fields they need to be. This way after something is selected the fields will just update to what ever the document contains, and it will be much more re useable so long as the domino docs have the same field names

Resources