Replicant Behavior

Working in 6.1 SP1 on Solaris 9, in a DCT is there a way to control access to replicant behavior by role? Specifically, can I allow only certain roles to be able to create additional replicants and/or delete replicants and have other roles only see this somehow as readonly?

Thanks!

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Find more posts tagged with

Comments

Adam Stoller

Using FormAPI - you can probably use the IWDatacapture.getRole() call to get the current user's role and then modify permissions on the replicant elements based on that.

In 6.5 manipulation of replicant items is, I believe, significantly improved - so if you have the choice of upgrading you might want to do so ....

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jimk351c

>In 6.5 manipulation of replicant items is, I believe, significantly improved - so if you have the choice of upgrading you might want to do so ....

I was afraid you were going to say that, Adam. I will check out the API. Thanks!

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Migrateduser

There's a webcast that goes over the enhancements, and has a code example included. See:

http://devnet.interwoven.com/site.fcgi/webcasts/docs/webcast-recordings.html#webcast04-23

hth,

lissa

jimk351c

Looking through the Forms Publisher API, I don't see a way to modify any attributes of replicants. This seems to be restricted to items and not to containers or replicants.

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Migrateduser

I'm on 6.1, too, and Adam hit the nail right on the head. IWDatacapture.getRole() seems to be the answer you're looking for and simple Javascript can take it from there. For instance:


var userRole = IWDatacapture.getRole();
if (userRole == 'master' || userRole == 'admin') {
  IWDatacapture.getItem(...).setVisible(true);
}

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 6.1 SP2 on Win2K

jimk351c

Dave,
I see what you are saying. But, I don't understand how to make this work for replicant controls, specifically the controls that let you add / subtract / sort replicants. There is no "item" associated with those controls that I know of. I want all users to be able to see what items are filled out in the replicants, I just don't want certain users to be able to access those replicant controls.

Thanks,

Jim

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Migrateduser

Although it's undocumented, there is the onItemAdded and onItemDeleted events that are available in 6.1. As Adam said, there are many more controls available in 6.5, but at least this is basic. For instance,

parent.IWDCEventRegistry.addListener("onItemAdded",doAction);

This will cause FormAPI to "listen" for replicants to be added. Unfortunately, doAction is kicked off whenever ANY replicant is added, but a simple IF statement in your function can cause your routine to work the way you want it to.

Other than this, what replicant controls are you looking for?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 6.1 SP2 on Win2K

Adam Stoller

You can't modify attributes of replicants as a whole (I don't believe) - but rather you have to iterate through the replicants that exist and/or as they get created in ordere to modify the items within the replicant.

It is in this last part that 6.5 offers enhancements such as:

IWItem.addInstance(index, [choice_name])
IWItem.deleteInstance(index)
IWItem.getChildByName(name)
IWItem.getChildren() -- this existed before 6.5
IWItem.isCollapsed()
IWItem.moveInstance(from_index, to_index)
IWItem.setCollapsed()
IWItem.setReadOnly(readonly, [recursive]) -- setReadOnly existed before - but 6.5 added the ability to have it recurse through children so that you could make this work on the entire contents of a container/replicant by referencing it from the top.

Events:

OnReplicantAdded
OnReplicantBeforeAdd
OnReplicantBeforeMove
OnReplicantDelete
OnReplicantMoved

Hopefully that gives you an idea of what 6.5 adds to the ability to interact with replicants. With 6.1 you're basically stuck using IWItem.getChildren() and writing your own recursion routines.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jimk351c

>>parent.IWDCEventRegistry.addListener("onItemAdded",doAction);

Dave,
Thanks, this is exactly what I needed! Can you tell me the names of the events to listen for, for "deleting" replicants and for "sorting" replicants as well?

Thanks!

Jim

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Migrateduser

Well, like Adam said (who's beginning to sound like a 6.5-snob, by the way), there are no methods for deleting or sorting replicants in 6.1. I've struggled with this, too. FYI, when you want to add a listener for deleted replicants, though, replace "onItemAdded" with "onItemDeleted".

I don't personally think that using recursion to traverse all replicants in order to, say, make a field required or change the value, etc., is so painful. The only curse in this is the performance is compromised.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 6.1 SP2 on Win2K

jimk351c

Now I see the merits of 6.5. How painful of an upgrade is it from 6.1 to 6.5?

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Adam Stoller

Going from 6.1 to 6.5 should be relatively painless ... *except* ... you have to figure out how you're going to deal with the new Seach component piece (do you *try* to install it all on one server or install it on two servers [recommended] - do you use the flat file default or a database [recommended])

There's the new search piece (above "optional" but you would have to go through customizations to *remove* the UI for it), the new TeamSite groups / iwgroup CLT (optional: you can ignore it until/unless you want to use it), the new reporting mechanism (optional: extra $'s additonal license), and the enhancements to FormAPI -- I think everything else is basically the same.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jimk351c

This seems to do the trick, Dave. However, I was having problems with the "onItemDeleted" event. I searched the forum and found this:

Delete
parent.IWDCEventRegistry.addListener( 'onItemRemoved', handleItemDelete );

Swap
parent.IWDCEventRegistry.addListener('onItemsSwapped', handleItemSwap);

It's all working perfectly now. Thanks, all!

Jim

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Migrateduser

The goal of 6.5 was to make it painless to upgrade from 6.1 or 6.0. I know Adam has posted a few gotchas. I will work with the folks on the TeamSite team to get these corrected and/or good workarounds.

The new 6.5 FormAPI capabilities are a great help to FormsPublisher developers.

regards,

lissa