[Date Prev] [Date Next] [Prev in Thread] [Next in Thread] [Date Index] [Thread Index]

Re: ARS 9.1: Question about hiding fields

The main advantage is the fact that the field isn't taking up any screen real estate anywhere on the form.  The object still exists on the form, is still transferred to the client, so it's not a transport advantage, but the fact that the field's not cluttering up the display is a maintenance advantage :)

On Fri, Nov 18, 2016 at 12:45 PM, Fawver, Dustin <FAWVER@mail.etsu.edu> wrote:


During my analysis of workflow for the migration to ARS 9.1, I have found that fields can be hidden in several ways.

- Hidden explicitly by the field's properties

- Placed in a panel page that the user doesn't not have permissions to.

- Removed from the user's view

- The field not being placed in any view

I found some fields being referenced in workflow that existed on the form but that weren't in any views.  Are there any advantages or disadvantages to having a field that's not present in any view versus a field that is simply hidden?

Thanks for your input.

--Dustin Fawver

HelpDesk Technician

Information Technology Services

East Tennessee State University


_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_