To the best of my knowledge yes, but that has nothing to do with sharing fields 
across multiple pages/panels.

 

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Tadeu Augusto Dutra Pinto
Sent: Wednesday, December 21, 2011 1:10 PM
To: [email protected]
Subject: Re: Panel / Page Holder behavior on ARS 7.6.04 P2

 

** 

Hi LJ,

 

Thanks for reply.

 

But I wonder If I not have to create these 3 separete fields. We already have a 
large number of fields on this form, and we are trying to avoid the creation of 
extra fields, considering this purpose

 

Referring to the document “FormAppObj-7604”:

 

Workflow considerations for panels 
If the Tabless Borderless property of a tabbed panel holder is set to True, you 
must 
create workflow to enable users to change which panel is displayed. For 
information about removing borders and tabs, see “To create a panel holder” on 
page 336. 
Remember these considerations when building workflow for panels: 

􀂄 You can use a panel holder as a data source in workflow. For example, you can 
use a Run If qualification such as 'PageHolder' = "Page3".

 

 

For example, can I use this tip above in bold text to create an Active Link 
that makes a Character Field Visible / Hidden depending on the Page chosen?

 

Ex:

 

a)      Active Link 1:

 

Run If: ‘PageHolder’ = “Page1”

 

Set Fields Action: Change Field “Character Field” to Visible

 

 

b)      Active Link 2:

 

Run If: ‘PageHolder’ = “Page2”

 

Set Fields Action: Change Field “Character Field” to Hidden

 

 

 

Is that acceptable working with version 7.6.04?

 

 

Cheers,

 

Tadeu

 

 

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of LJ LongWing
Sent: quarta-feira, 21 de dezembro de 2011 17:42
To: [email protected]
Subject: Re: Panel / Page Holder behavior on ARS 7.6.04 P2

 

** 

Tadeu,

In 7.6.4 you can’t even share fields across multiple tabs.  It supports it for 
fields already added in previous versions, but you cannot configure a new field 
as such.  The BMC recommendation would likely be to create 3 separate fields 
and use AL’s to sync the contents.

 

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Tadeu Augusto Dutra Pinto
Sent: Wednesday, December 21, 2011 11:44 AM
To: [email protected]
Subject: Panel / Page Holder behavior on ARS 7.6.04 P2

 

** 

Hello everyone,

 

I Hope someone could help with any kind of information about Panels / Page 
Holders differences between 7.0.x and 7.6.04 version of ARS.

 

 

Here goes my predicament:

 

 

For instance, How could I create a scenario that a Character Field is shared 
through 3 “pages” of 5 pages available on a specific form?

Using the property Shared Fields (at Panels from a Page Holder component), the 
Character Field is visible in all of the 5 pages of my Page Holder.

 

 

I’m referring to my component as “Page Holder” because I’ve done the upgrade 
coming from ARS 7.0.01.

 

 

Since I share a field, it become available on all the 5 pages…

As a workaround for this problem, I used a non-fancy way of working with Trim 
Box’s components  to hide my Character Field in specific pages… 

 

 

AR Server 7.6.04 Patch 2

Oracle DB 11g (11.2.0.2.0) 64 bits

Mid-Tier 7.6.04

 

OBS: Trying to overlay components/forms to work on it using the new AR Server 
version (7.6.04)

 

 

Regards,

 

Att,

Tadeu

 

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to