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

How can I disable replicant's add instance button?

enthusiast

Is there a way to disabled the add instance button of a replicant through javascript? I want to control when an instance can be added regardless of the pre-defined min and max values.

Find more posts tagged with

Comments

Pawan

Is there a way to disabled the add instance button of a replicant through javascript? I want to control when an instance can be added regardless of the pre-defined min and max values.

You cannot disable the add instance, but you can definitely handle the event of the added replicant. You can look for onReplicantAdded functions in the form api developer's guide.

bhaskar_1981

hey... even i am looking for a similar behaviour , where i want that the users should not be able to add replicants using the add button. any pointers?

Regards,
Bhaskar

Adam Stoller

hey... even i am looking for a similar behaviour , where i want that the users should not be able to add replicants using the add button. any pointers?

Regards,
Bhaskar

If you don't want users to add replicants, don't define the container as a replicant. If you don't want users to add more than N instances of a replicant, define the max for the container to be N.

If there is some other situation you are trying to handle, be precise in describing the details of the scenario.

ISCBorisB

hey... even i am looking for a similar behaviour , where i want that the users should not be able to add replicants using the add button. any pointers?

Regards,
Bhaskar

See if [thread=29319]this[/thread] thread may help

curiousmaverick

A possible scenario can be one where we use custom templates, meaning a DCR is used as a template. In that case, we wouldn't want replcant instances to added or deleted by the user, since it is a template now.

jagadesh

Have you tried setReadOnly option in your form API on init method for replicant container. on certain condition as well u can set readonly for the container item in form API.

curiousmaverick

setReadOnly won't serve the purpose here. It can't restrict addition/deletion of replicant instances.

You need to do something like this:

IWEventRegistry.addItemHandler ("/root/..","OnReplicantBeforeAdd",allow_replicant_add_delete_move);
IWEventRegistry.addItemHandler ("/root/..","OnReplicantDelete",allow_replicant_add_delete_move);
IWEventRegistry.addItemHandler ("/root/..","OnReplicantBeforeMove",allow_replicant_add_delete_move);

allow_replicant_add_delete_move will return false after alerting some message.

jagadesh

SetReadOnly will helpful for container level replicants. For Item level replicants solution should be onReplicantBeforeAdd

curiousmaverick

setReadonly will never work for restricting addition/deletion of replicant instances.

Adam Stoller

A possible scenario can be one where we use custom templates, meaning a DCR is used as a template. In that case, we wouldn't want replcant instances to added or deleted by the user, since it is a template now.

I'm not sure this makes sense as a scenario - but more to the point, I was asking the person(s) who posted the question regarding this what they're actual use case scenario is - not for everyone and their brother to make guesses as to what the use case scenario was.

curiousmaverick

It's a discussion forum, so there should not be a problem.

Adam Stoller

It's a discussion forum, so there should not be a problem.

Perhaps - but generally it's best to discuss either the source or resolution of the problem - not the identification of what the problem is. It's best if the definition of the problem is provided by the person(s) originating the thread - then everyone can jump in and suggest resolutions. Your guessing only serves to sidetrack the thread into something likely to become even more unintelligible (IMO).

curiousmaverick

may be, but Ive ensured to address the resolution as well. Hope that way I'm making sense.

jagadesh

How you are opposing setReadonly wont give solution to restrict addition/deletion at container level replicant.

Have you tried before.

I implemented the solution using setReadonly in my current assignment.
values are retrieved from the DB, based on no of values it should be displayed in UI. addition/deletion disabled to Business users on UI using setReadOnly(true).

If you want code snippet and screenshot for you reference I will be ready to share with you.

curiousmaverick

Yes sure, I'fd love to see how you've implemented it.

jagadesh

Find the attachment for your reference
Code snippet
DCT
<container name="offers" min="0" max="290" default="1">
<label> Offers</label>
.........
<container>
Form API code
IWDatacapture.getItem("/rootcontainer../offers").setReadOnly(true);

I hope so you are refering some older version teamsite. Now the latest version is TS6.7.2 Sp2-Build70044. My best advice to be
"Don’t argue with peoples without having knowledge"
Think twice before speak/do once

curiousmaverick

Great knowledge, I admire you. can't stop wondering how you can rememeber even the build version.

hats off..

btw, the question was about restricting add option. and the most perfect solution to it is using on replicantbeforeadd. He may want to keep delete/move options still intact.

jagadesh

Thanks mav for your compliment. If requirement needs to restrict only addinstance, then only onReplicantBeforeAdd should be good solution. it will restrict user but wont diasble the addinstance.
Anyway based on requirement solution should go.

bhaskar_1981

If you don't want users to add replicants, don't define the container as a replicant. If you don't want users to add more than N instances of a replicant, define the max for the container to be N.

If there is some other situation you are trying to handle, be precise in describing the details of the scenario.

I want the container to be replicant. The instances should be added programmatically using javascript. User should not have the add or delete replicant buttons as we normally have on the replicant containers.

any pointers?

jagadesh

Bhaskar,
Then try the setReadOnly(true). Can you please look into the attached screenshot in my earlier posts.
Long ago we have implemented to get list of values from DB. based on values count, Form APi will load the container. Business User cant add/delete the replicant values in Form. using Form APi we can add or delete the container instance.

bhaskar_1981

Perfect! Thanks Jagan! Your solution rocks :-)

jagadesh

Always welcome Bhaskar