Hi,
It seems it's possible using "Overlay-Mode" in ar.cfg:
https://docs.bmc.com/docs/display/public/ars81/Ignoring+overlay+and+custom+objects+at+runtime
If you set it to 0 all overlays (and custom) will be ignored.
The interesting part is this sentence:
////////
You can, however, configure the server to execute overlaid objects at runtime and to ignore overlay and custom objects unless an operation's control record specifies an overlay group. (This exception enables clients to specify that the server should execute an overlay or an origin object.)
////////
Though there is no specific example.
It seems it's possible using "Overlay-Mode" in ar.cfg:
https://docs.bmc.com/docs/display/public/ars81/Ignoring+overlay+and+custom+objects+at+runtime
If you set it to 0 all overlays (and custom) will be ignored.
The interesting part is this sentence:
////////
You can, however, configure the server to execute overlaid objects at runtime and to ignore overlay and custom objects unless an operation's control record specifies an overlay group. (This exception enables clients to specify that the server should execute an overlay or an origin object.)
////////
Though there is no specific example.
On 09 Apr, 2013,at 10:09 AM, "Hullule, Kiran" <kiran_hull...@bmc.com> wrote:
Hi Joe,
As far as I know, that is not possible, as soon as you create an overlay of any base object (oob object) the overlayProp columnsets its value in database as: -> 2
See below for more details.
overlayProp column
AR ORIGINAL OBJECT 0 un-touched or out of the box object
AR OVERLAID OBJECT 1 base object which is overlaid
AR OVERLAY OBJECT 2 overlay object
AR CUSTOM OBJECT 4 object created through custom mode client
Once server identifies that base object has an Overlay created then server will respond to the client queries (APIs) as against overlay object and Overlay object will be user (client) facing. You cannot enforce base layer to clients when its overlay object is already in place.
HTH.
Regards,
Kiran
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza
Sent: Tuesday, April 09, 2013 8:20 AM
To: arslist@ARSLIST.ORG
Subject: Re: Can't create unique index in 8.1 on overlay forms?
If that's the case, from the AR System client perspective, how do I connect
to the base layer if I did not want to connect to the overlay layer?
Cheers
Joe
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Chuck Mousseau
Sent: Monday, April 08, 2013 8:51 PM
To: arslist@ARSLIST.ORG
Subject: Re: Can't create unique index in 8.1 on overlay forms?
Hey Folks,
The inability to create unique indexes on a form overlay is not a bug; it's
intentional.
The reason is that it affects operations at the origin layer as well as at
the overlay layer.
Records for a form and its overlay are stored in the same database tables.
That means indexes created for either affect data operations for both.
If a unique index were created in the overlay layer, it would still be
enforced on records created or modified through the origin layer, so the
behavior of the origin layer would be changed.
If the index is on a custom field, then it becomes impossible to create
records at the origin layer. If the index is on an origin field or on an
overlaid field, it can still prevent operations that were previously legal
at the origin layer.
Among other things this could cause upgrades to fail by preventing them from
updating data.
Unique indexes can be created on custom forms, because changes to custom
forms do not affect the origin layer -- those forms are not visible there
and no data operations can be performed on them at that layer.
One workaround that has been suggested is to go to Base Development mode in
Developer Studio and then to add the unique index to the origin form. Doing
that can prevent upgrades from succeeding. It also doesn't guarantee that
the change will be persisted across an upgrade if the upgrade should
succeed, because the change is not captured in an overlay.
If we want to ensure that a field's contents on an overlaid form are unique
in the overlay layer, the best way to accomplish that is to create a custom
filter that returns an error when duplicate data is written.
The filter will not affect operations performed at the origin layer, but it
will protect data written at the overlay layer.
Hope this helps,
-Chuck
____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
