Making items not visible in a form

Permanently deleted user

April 23, 2013 11:03

Hi to all

As a means of customising or tuning a form based on prior user input I wish to be able to make some form items not visible rather having several forms following each other.

ie in the Runtime modifications:

       form.Find(Of GroupBoxFormItem)("GroupBox1").Visible = False

when the content of that GroupBox is not required in the current usage circumstance.

Is this possible?

It would appear that it is not. Just thought that I would check and potentially ask for a feature enhancement iin that case.

That enhancement request would apply to most any form item but a GroupBox would seem a good place to start.

Regards

Ralph

0

• 

  Ryan Cooney

  May 23, 2013 07:52

  Hi Ralph,

  This is not possible at the moment. But it is such a good idea that it is now under development. You will be able to hide any form item with this pattern. It should be available later this summer. Great suggestion!

  --Ryan

  0
• 

  Permanently deleted user

  May 23, 2013 08:22

  Hi Ryan

  Thanks for the confirmation. Much appreciated. The Forms are such a useful tool. Runtime modifications were a big enhancement and this just further build on it.

  Regards

  Ralph

  0
• 

  Permanently deleted user

  October 30, 2013 18:43

  Is there any update now that we are post Summer.....

  I want to make one of two textboxes visible depending on the option that a user has selected in a radio button without the need for two forms.

   Pseudocode

  If RadioButton.Selected = Search by zip code

  Then ZipCodeTextBox.Visible = True AND PostcodeTextBox.Visible = False

  Elseif RadioButton.Selected = Search by Postcode

  Then ZipCodeTextBox.Visible = False AND PostcodeTextBox.Visible = True

  End if

  Any advice appreciated.

  0
• 

  Ryan Cooney

  October 30, 2013 22:35

  Yes, support for an "IsVisible" Boolean property was added to all form items in Essentials 3.15. You will also need to be using either GVS 1.10 or GVH 1.3.

  --Ryan

  0
• 

  Permanently deleted user

  October 31, 2013 01:57

  Hi colinbt

  just to clarify on behalf of Ryan, it appears that you wish to have client-side event handling in your form ie hide or show a textbox based on which radiobutton item is selected in a SINGLE form.

  I do not believe that is currently possible with the current workflow forms. If you write your own client module etc then yes.

  How about having one textbox all of the time and treat the contents as a postcode if the postcode radio button is selected and a zipcode if the zipcode radio button is selected?

  Regards

  Ralph

  0
• 

  Permanently deleted user

  October 31, 2013 02:01

  How would you be able to make a client module?

   

  "I do not believe that is currently possible with the current workflow forms. If you write your own client module etc then yes."

  0
• 

  Permanently deleted user

  October 31, 2013 02:13

  Hi Jason

  have you reviewed the Quickstart at all?

  I have only made use of custom coding for client interactions, (getting graphics etc) as compared to creating new interface components.

  But essentially you will need to create a new client window interface with appropriate code to initiate, control and dismiss it, package it into a .xap file, include it in the ClientBin directory, continue to feed it when updating viewer versions etc.

  Seems a lot of trouble to go to unless you are wanting to do something way bigger than what you have described so far.

  Regards

  Ralph

  0
• 

  Permanently deleted user

  October 31, 2013 04:17

  Ralph, Jason,

  Thank you for your help and guidance thus far.  I agree with what you have suggested and creating my own custom component is ultimately too much work for what I have in mind.  I will proceed with having one textbox and a radio button.  The complexity was that for my POSTCODE I want an auto-complete box and for GRID REFERENCE I want to use a textbox.

  What I will do is stick with the auto-complete box, based on the practical assumption that:

  a) auto-complete box will function when a user wants to gazetteer based on a POSTCODE.

  b) when a user wants to enter a GRID REFERENCE to text entered will not resemble a POSTCODE therefore no spurious results will autocomplete, so to speak.

  Not the most elegant solution, but I think it is preferable to adding a two stage and two form process for the users...  I guess its just a case of seeing how my assumption holds up in testing.

  Hopefully a future release will permit form component run time manipulation based on user interaction.

  Thanks again,

  Colin BT

  0
• 

  Permanently deleted user

  July 11, 2014 10:37

  Was thinking about doning the same thing in HTML5 viewer but realise it's not supported by Workflow. Would be great if it did. I'm also wondering what the Dynamic External Activity does in workflow, never used it nor really understood it. Would be great could have some examples.

  regards,

  Jack

  0

Please sign in to leave a comment.