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; } } }

Controlling min/max of a replicant

arabif

Hi,

Can the "max" value of a replicant be controlled dynamically using FormAPI?

The requirement is -> The DCT consists of a radio box (National & regional as options) and a container with various fileds. When the user selects National, the container should behave as an replicant (min=0 and max=unbounded) and for Regional it should remain a container (min=0 max=1). Can this be achieved using FormAPI (without having to maintain different containers/fields for each choice)? Any thoughts/suggestions will be appreciated.

TeamSite: 6.5
on Solaris 2.8

Thanks

Find more posts tagged with

Comments

ang1

Not sure haven't tried it but using FormAPI you can probably add a listener to addInstance event on the replicant item, and check for the value of radio button. If it is regional, don't let the person add more than one instance of replicant.

-Anurag

ISCBorisB

Hi,

Can the "max" value of a replicant be controlled dynamically using FormAPI?

The requirement is -> The DCT consists of a radio box (National & regional as options) and a container with various fileds. When the user selects National, the container should behave as an replicant (min=0 and max=unbounded) and for Regional it should remain a container (min=0 max=1). Can this be achieved using FormAPI (without having to maintain different containers/fields for each choice)? Any thoughts/suggestions will be appreciated.

TeamSite: 6.5
on Solaris 2.8

Thanks

It can be done, sure. Your event is "OnReplicantBeforeAdd", returning true/false from your handler.

However, this sort of coding is very brittle on DCR updates. Here is the scenario: "National" chosen originally,
few replicants created. Later on, your author decides to make it regional. What happens to existing replicants ?
If you automatically clean them, what will an Editor do if he overrides Author's decision? And so on....

In my opinion you'd be better off by creating two containers (one per choice) and alternating their visibility.
Your PT if you have any should be made aware of this "hidden container" toggle as well.

ISCBorisB

Not sure haven't tried it but using FormAPI you can probably add a listener to addInstance event on the replicant item, and check for the value of radio button. If it is regional, don't let the person add more than one instance of replicant.

-Anurag

If you give somebody an advise, please try to be precise. You never know guy’s level of expertise.

- Listeners were not documented/supported before and are not now. Whereas
up to 6.1 we had to use them sometimes, starting with 6.5 99.99% of that cases
are covered by Item Handlers and extended set of Events.

- addInstance is not an event but rather IWItem method that under scenario
should NOT be used, etc...