nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Capturing events in non-replicating container

Dan_O

I'm having trouble capturing the event that results from clicking the (+) in a non-replicating container. The container is set up as an "or" with min and max of 1. It has three further containers within it, only one of which shows up, based on the selection made via the (+). In this scenario, it doesn't seem to trigger the onReplicantAdded nor onItemChange event handlers.

l'm trying to have a handler execute when one of the three options is selected; in this case, /content_type/Affiliate. I have tried to run the handler from onFormInit, and it works fine. But if a different container is chosen, and then the container with the special handling, the handler never gets executed again. I don't see any JavaScript errors, either.

I can find lots of DevNet articles about capturing such event on replicants, but none that I've found on this particular problem. I appreciate any help at this point.

Dan Olson
TS 6.5 Solaris

Here is a very simplified DCT that acts the same way:

[html]

Content Well

Type
Specify the target for the content

Employer Name

Affiliate Name

<script> IWEventRegistry.addFormHandler("onFormInit", init);  function init() { IWEventRegistry.addItemHandler('/content_type', 'onReplicantAdded', sayHi ); } function sayHi(item) { alert("Triggered onItemChange on replicant"); } </script>

[/html]

Find more posts tagged with

Comments

Adam Stoller

Hmm - interesting - not sure IWOV ever tried this edge-case.

The only thing I can think of that might work is if you change the OR container definition from min=1, max=1 to min=0, max=1, default=0 and then clicking the '+' might result in an onReplicantAdded event.

Dan_O

Interesting thought, Ghoti. I tried it, and it does work, which at least tells me that my coding was correct. However, the only way to navigate from one internal container option to another is to delete the open one and then open the one that is desired. Not an elegant interface, but unfortunately it's the only (and thus, leading) candidate for workaround.

So near, and yet so far...

This is my third attempt at various techniques to accomplish what I'm trying to do, and given this technical roadblock, I'm open to other suggestions. I have three sets of data (General, Affiliate, Employer), only one of which will be used at a time. Hence, the OR-container with the three containers within it. In the Affiliate container, we have thousands to choose from. My solution was to break the list up into dropdowns, grouped by letter. There is also a line of clickable letters, upon which a click makes that particular dropdown appear. Everything works, except for the fact that when the Affiliate container is selected, the entire data set appears, which is why I was trying to capture the event to act upon. I can turn it off initially via an onFormInit function call, but each revisit to the container produces the entire data set again. Anyone have a different viewpoint to solve this?

Dan

DropTableBasedOnUserParameter.rptdesign

Adam Stoller

Interesting thought, Ghoti. I tried it, and it does work

I'm glad it worked - I strongly suggest that you file a case with IWOV about this situation though - it may not get fixed right away (unless your with a company that can throw some weight around to get a black-patch) - but it should, in the long run, lead to a fix.

I have three sets of data (General, Affiliate, Employer), only one of which will be used at a time. Hence, the OR-container with the three containers within it. In the Affiliate container, we have thousands to choose from. My solution was to break the list up into dropdowns, grouped by letter. There is also a line of clickable letters, upon which a click makes that particular dropdown appear. Everything works, except for the fact that when the Affiliate container is selected, the entire data set appears, which is why I was trying to capture the event to act upon. I can turn it off initially via an onFormInit function call, but each revisit to the container produces the entire data set again. Anyone have a different viewpoint to solve this?

Here's an idea - instead of using a single OR container for 3 types of fields - consider creating 3 containers preceded by a set of 3 radio-buttons for the different types of data - then you should be able to catch the onChange event of the radio button to hide/expose the right container and whatever else you need to do within them.

This would probably mean a change to your PT as well (or whatever might be consuming your DCR) but it should be relatively easy to code the conditional logic based upon the value of the radio-button.

Hope that helps.

Dan_O

I may give that a try. I'm pretty sure I can make the logic work.

Meanwhile, back in replicant ****.... I was inspired by the initial reponse to set the values on the replicant container to min=0, max=2, default=1, at which point I was able to capture the onReplicantAdded event. I could even capture onReplicantBeforeAdd. However, I still only wanted one replicant to appear, so I tried running a deleteInstance to remove the previously-existing one. I had problems putting deleteInstance in either the onReplicantAdded or onReplicantBeforeAdd handlers.

If I merely click delete in the UI to get rid of the replicant, the container says it has 0 items, and shows "- Currently there are no entries -". When I then click Save (in whose handler I have put more alerts), it says there are no children.

All is well, so far. Then it gets weird.

If I put deleteInstance in onReplicantBeforeAdd, I wind up with an identical replicant container to above. I know the onReplicantAdded handler has run, because I see the alerts from within it. But when I click Save, it says there is 1 child, even though I have no visible indication as such.

If I then move deleteInstance(1) to the end of the onReplicantAdded handler, I get a totally blank replicant container (not even "- Currently...") and it tells me there is 1 item, which is confirmed by clicking Save. If I change it to deleteInstance(2), it throws an uncaught exception error. If I put moveInstance(1,2) before the delete, I get the same results only reversed, where deleteInstance(1) throws the exception and deleteInstance(2) shows the empty replicant container which has one item. Where, I have no clue.

One other oddity: If I run moveInstance(1,2) without deleting, I get both replicants, but item #2 is shown first, rather than resorting as I would expect.

It seems to be acting like the replicant isn't entirely added at the time the onReplicantAdded handler is run, despite what the docs say. I assume that deleteInstance and moveInstance work as advertised when not executed within the handlers associated with the creation of a related replicant.

Anyway, this is a long-winded rant, mostly to give others who may try this some warning. And to put a burr under IW's saddle. But I will have a case opened about all this.

Dan

ISCBorisB

I may give that a try. I'm pretty sure I can make the logic work.

Disadvantage of this approach is that FormAPI is pretty much ignored in "View" mode, so all components will be visible

Dan_O

FYI,

I have been told this week by IW support that my initial issue (the inability to handle onReplicantBeforeAdd, onReplicantAdded or onItemChange events on a non-replicating container works in TS 6.7.1. As of now, it has not been tested by them in 6.5 to confirm, and I don't know when it was fixed.

Still working on the second issue... But at least I have a viable workaround. (Thanks, fish!)

Dan

Tim__D

FYI,

I have been told this week by IW support that my initial issue (the inability to handle onReplicantBeforeAdd, onReplicantAdded or onItemChange events on a non-replicating container works in TS 6.7.1. As of now, it has not been tested by them in 6.5 to confirm, and I don't know when it was fixed.

Still working on the second issue... But at least I have a viable workaround. (Thanks, fish!)

Dan

I found this issue and thought I would just comment that as of TS 6.7.2 on Solaris 10 this is still not fixed.

min="0" max="1" default="1" combination="or" is the only way I could get it to work.

- Tim