Jason is correct. You do not need to have fields in the view to use them in workflow.
AND, you will get better performance and scale if you take any field that you never need to have visible out of the view. This makes your definition smaller (you don't need the display properties for something you never display). This makes your web page smaller and more efficient. This makes less data have to flow over the wire. In all ways, it is a win. Now, as Jason also points out, due to some oddities of what you can interact with, if you have an attachment field that you want to interact with and it is never visible, you may need to leave that on the form as a hidden field because you do need some of the constructs related to the field display around to work with them (even though not visible). There may also be an issue with table fields if you are going to load and walk (why else would you ever load it in the first place) a table that is not visible. This is not that common, but it can occur. You may have to have the table field as a hidden field. But, other than these cases (not that common), you can remove all fields that never display from the view and all workflow will work just fine and your application will be faster and more efficient. NOTE: even the table field case... I would strongly suggest that if you have a hidden table field that you are getting data to do some kind of a table walk to do some calculation, that you consider moving that to a service call so that you make a service call to the server, have filters load the table, walk it, and calculate, and then return the answer. This is less traffic on the wire (all the table data) and does everything in one round trip (vs. several) and scales better and allows you to remove the table from the view for sure making your UI lighter and faster. Something to think about. I hope this is helpful, Doug Mueller ________________________________ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller Sent: Thursday, May 05, 2011 5:24 PM To: arslist@ARSLIST.ORG Subject: Re: Hidden Fields Causing A Very Large Web Page ** You do not need hidden fields in the view to use them in workflow. I have occasionally had issues with Attachment pools/field where they had to be in the the view. Aside from that we typically do not put hidden fields in our main view. Jason On Thu, May 5, 2011 at 3:03 PM, Drew Shuller <drew.shul...@gmail.com<mailto:drew.shul...@gmail.com>> wrote: ** Good afternoon everyone! Our main default help desk form has quite a few hidden fields on it, off to the right side and below. The Mid-Tier renders this form very wide and long, as if the fields are there, but the fields of course are not displayed. Aside from adding hidden tabs to the middle of the form and putting the hidden fields on those tabs, is there a trick to making sure that the web page is only as wide as the visible fields? How about if I remove the fields from the view? But don't I need the hidden fields for whatever workflow is running when the users have that form open? Thanks in advance for the help. Drew Shuller JTF-Bravo _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
