Manipulating choice item with FormAPI

It is not documented and I am worried that it is impossible, but how can I automatically change the selection on a choice object using FormAPI. For an orcontainer, there is an optional second parameter to the addInstance method that does it, but it seems that there is no equivalent for choice. Anyone have any idea? Or even a hack?

TS 6.7.1, Solaris 9

Find more posts tagged with

Comments

ISCBorisB

It is not documented and I am worried that it is impossible, but how can I automatically change the selection on a choice object using FormAPI. For an orcontainer, there is an optional second parameter to the addInstance method that does it, but it seems that there is no equivalent for choice. Anyone have any idea? Or even a hack?

TS 6.7.1, Solaris 9

Perhaps that may help, take a look

chuckles

No, I mean a element not a . A item is like an orcontainer except it does not replicate and does not require a location attribute which is the main reason I want to use it.

nipper

According to the docs, a choice is just a container with combination=or, since you said the container has formapi that will work, can you change the choice to a container instead ?

I would not be surprised to see the choice object go away if it is redundant.

Andy

chuckles

The only benefit to using instead an orcontainer is that if you are doing custom XML mapping (which we are) does not require a location attribute which lets you add some complexity to your DCT without jumbling your XML which is what I was hoping to do.

Our DCRs are going straight to an app server that validates against an XSD and then generates a JavaBean so any changes to the XML require a new application build which I was hoping to avoid since I just want to add some dang javascript to my DCT and it shouldn't have a knock on our application.

chuckles

For anyone else facing this, I have a durty hack that seems to be effective:

function changeChoice(item, choiceName) {
top.datacapture.handleOrPopupChoice(item.itemImpl.instanceID, choiceName, false);
}

And to catch events when a new choice is selected:
top.getDCFrame().formframe.document.getElementById("or_addmenu_" + choiceItem.itemImpl.instanceID).onclick = myHandlerFunc;

ISCBorisB

For anyone else facing this, I have a durty hack that seems to be effective:

function changeChoice(item, choiceName) {
top.datacapture.handleOrPopupChoice(item.itemImpl.instanceID, choiceName, false);
}

And to catch events when a new choice is selected:
top.getDCFrame().formframe.document.getElementById("or_addmenu_" + choiceItem.itemImpl.instanceID).onclick = myHandlerFunc;

You can perhaps use "OnReplicantBeforeAdd" Event to catch your User activity, return 'false' from the handler to terminate
a request unconditionally and issue "addInstance" with desired parameters yourself.

Am I still missing something here?

chuckles

Boris, no that doesn't work. Changing the choice option does not trigger any events. I tried them all. NB to all Templating developers: always use orcontainers and never use choice!!

nipper

Boris, no that doesn't work. Changing the choice option does not trigger any events. I tried them all. NB to all Templating developers: always use orcontainers and never use choice!!

Like I said, the choice *seems* to be redundant and will likely be replaced by the container or.