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

Replicant Delete

rjoseph

For a single template I want to restrict a users ability to delete a replicant. In TeamSite 6.x I am able to handle a users request to delete a replicant in the following manner..

IWEventRegistry.addItemHandler("/prodInfo/prodRelations/rowItems", "OnReplicantDelete", "disallowDelete");
IWEventRegistry.addItemHandler("/prodInfo/prodTranslations/rowItems", "OnReplicantDelete", "disallowDelete");

function disallowDelete( item ) {
alert " cannot be deleted")
item.setValid( false )
}

Does anybody know if there is any way to provide the same or similar functionality in 5.5.2? If so, what is it? I have RTFM'd, searched forums, support, devnet, and scratched my head and can't come up with anything. I am guessing that somebody ran into this and resolved it prior to moving to 6.x/

Thank you

Robert Joseph

Find more posts tagged with

Comments

Migrateduser

The short answer is no. The major feature of 6.5 was adding the functionality for FormAPI to support various operations and events in replicants.

I'll also make the obligatory comment that 5.5.2 is post-EOL, so you need to be encouraging your boss/customer to upgrade in any case.

rodigz

hi all,

how will i know which replicant user have selected for the delete?
I have requirement that it will do something in different replicant delete.

thanks!

Adam Stoller

hi all,

how will i know which replicant user have selected for the delete?
I have requirement that it will do something in different replicant delete.

thanks!

If you're using a replicant event handler - the function will be passed the specific instance of the replicant which has been requested to be operated on.

ISCBorisB

This post has been removed