Re: Hidden Fields Causing A Very Large Web Page

[Andrew C Goodall]

Trick is in developer studio (when you have the form open) on the menu
select  Layout / show Actual View Size (Cntl+Alt+M)

 

Then go to the outer right bottom edge of the form and look for the
black line indicating the edge of the form.

Click on the black edge and look for the black square to allow you to
drag the size in.

Then alter size of window to how you want it to look, then save form.

 

Regards,

 

Andrew Goodall

Software Engineer 2 | Development Services |  jcpenney . www.jcp.com
  |  972.431.1518



From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Drew Shuller
Sent: Thursday, May 05, 2011 5:04 PM
To: arslist@ARSLIST.ORG
Subject: Hidden Fields Causing A Very Large Web Page

 

** 

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 ARSlist: "Where the Answers Are"_ 

The information transmitted is 
intended only for the person or entity to which it is addressed and may 
contain confidential and/or privileged material.  If the reader of this message 
is not the intendedrecipient, you are hereby notified that your access is 
unauthorized, and any review, dissemination,distribution or copying of this 
message including any attachments is strictly prohibited.   If you are 
notthe intended recipient, please contact the sender and delete the 
material from any computer.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Re: Hidden Fields Causing A Very Large Web Page

[Jason Miller]

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  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 ARSlist: "Where the Answers Are"_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Re: Hidden Fields Causing A Very Large Web Page

[Mueller, Doug]

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 
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"

Re: Hidden Fields Causing A Very Large Web Page

[Drew Shuller]

>
>  It certainly is helpful Doug, thank you. I have at least one server-side
> table for that form. I'll try to remove all the fields from the view.
>



>  Resizing as Andrew suggests is not working - I still have a lot of space
> below and to the right of my form.
>

Drew

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Re: Hidden Fields Causing A Very Large Web Page

[Ben Chernys]

Hi Doug,

 

I found this very helpful and very well written indeed!  Thank you.

 

Cheers

Ben

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug
Sent: May-06-11 18:54
To: arslist@ARSLIST.ORG
Subject: Re: Hidden Fields Causing A Very Large Web Page

 

** 

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  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 ARSlist: "Where the Answers Are"_ 


_attend WWRUG11 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"

Re: Hidden Fields Causing A Very Large Web Page

[Guillaume Rheault]

I hope that Remedy developers at BCM are aware of this, since the main ITSM 
forms (HPD:Help Desk, CHG:Infrastructure Change, etc) still have a very large 
number of fields used in workflow, at least in ITSM 7.5.1

Guillaume


From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG] on 
behalf of Mueller, Doug [doug_muel...@bmc.com]
Sent: Friday, May 06, 2011 12:53 PM
To: arslist@ARSLIST.ORG
Subject: Re: Hidden Fields Causing A Very Large Web Page

**
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 
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"_ _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"

Re: Hidden Fields Causing A Very Large Web Page

[Easter, David]

Yes, they are.  This is one factor in why the performance of the applications 
increased significantly in 7.6.0x.

-David J. Easter
Manager of Product Management, Remedy Platform
BMC Software, Inc.

The opinions, statements, and/or suggested courses of action expressed in this 
E-mail do not necessarily reflect those of BMC Software, Inc.  My voluntary 
participation in this forum is not intended to convey a role as a spokesperson, 
liaison or public relations representative for BMC Software, Inc.

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Guillaume Rheault
Sent: Monday, May 09, 2011 07:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Hidden Fields Causing A Very Large Web Page

**
I hope that Remedy developers at BCM are aware of this, since the main ITSM 
forms (HPD:Help Desk, CHG:Infrastructure Change, etc) still have a very large 
number of fields used in workflow, at least in ITSM 7.5.1

Guillaume

From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG] on 
behalf of Mueller, Doug [doug_muel...@bmc.com]
Sent: Friday, May 06, 2011 12:53 PM
To: arslist@ARSLIST.ORG
Subject: Re: Hidden Fields Causing A Very Large Web Page
**
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 
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"_ _attend WWRUG11 
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"