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

readonly oddity

nipper

So I have a replicant of items, in each set some will be readonly and changed within formapi.

I have 2 issues. First, (should be an easy one), when I open an existing DCR, how do I know how
many times to set RO ? Where can I get the # of replicants on open ?

Second issue is strange.

During the open, I set the exiting fields to readonly. Works great. They are RO and grey,
making it obvious they are not writable. I also have a onaddreplicant event to make any new ones
added RO as well. They are readonly, however, they are not grey, but white.

Here is the code:

function init() {
IWEventRegistry.addItemHandler('/Catalog','OnReplicantAdded',newdata);
setreadonly();
}
function newdata(newitem){

var item=newitem.getName();
IWDatacapture.getItem(item+'/AccyCat').setReadOnly(true);
IWDatacapture.getItem(item+'/AccyTitleNomen').setReadOnly(true);
IWDatacapture.getItem(item+'/MotProdLine').setReadOnly(true);
IWDatacapture.getItem(item+'/PDSTitle').setReadOnly(true);
IWDatacapture.getItem(item+'/PDSImageSet').setReadOnly(true);
IWDatacapture.getItem(item+'/PDSImage').setReadOnly(true);
IWDatacapture.getItem(item+'/PDSContentDesc').setReadOnly(true);
IWDatacapture.redraw();
}
function setreadonly(){

IWDatacapture.getItem('/Catalog[1]/AccyCat').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/AccyCat').setReadOnly(true);
IWDatacapture.getItem('/Catalog[1]/AccyTitleNomen').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/AccyTitleNomen').setReadOnly(true);
IWDatacapture.getItem('/Catalog[1]/MotProdLine').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/MotProdLine').setReadOnly(true);
IWDatacapture.getItem('/Catalog[1]/PDSTitle').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/PDSTitle').setReadOnly(true);
IWDatacapture.getItem('/Catalog[1]/PDSImageSet').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/PDSImageSet').setReadOnly(true);
IWDatacapture.getItem('/Catalog[1]/PDSImage').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/PDSImage').setReadOnly(true);
IWDatacapture.getItem('/Catalog[1]/PDSContentDesc').setReadOnly(true);
IWDatacapture.getItem('/Catalog[2]/PDSContentDesc').setReadOnly(true);
IWDatacapture.redraw();
}

Find more posts tagged with

Comments

nipper

OK, so I answered my first question, could not get the # of replicants, but found a loop/conditional that
gave me what I needed:

var i=1;
while (IWDatacapture.getItem("/Catalog["+i+"]")) {
newdata('/Catalog['+i+']');
i++;
}

I use the same routine (with an additional if statement) to set readonly on startup
as well as adding a replicant. Why one is grey and not the other is a mystery.

LooseCannon

1) get the number of replicants:


my count = IWDatacapture.getItem("/Catalog").getChildren().length;

2) looks like a bug

JonathonG

On your second issue, we've had the same thing. And I haven't yet figured out any pattern to when it makes them gray vs. white. We flagged it as a bug, but I'm not sure a support case ever got created. The group here that manages our relationship with support is too busy to deal with "minor" issues like this.

Jonathon
Interwoven Developer
Allstate, Inc.

jbonifaci

Andy,

A better solution than getting a count, is to just get the children and iterate through the array of children. Also, you need to start using onFormInit:
//////////////////////////////////////////////////////////////////////
// Call the initializeDct function when this script loads.
//////////////////////////////////////////////////////////////////////
IWEventRegistry.addFormHandler("onFormInit", initializeDct());
//////////////////////////////////////////////////////////////////////
// Function: initializeDct
// Description: Initializes the DCT when the script loads.
// Parameters:
// None
// Return value: None
//////////////////////////////////////////////////////////////////////
function initializeDct()
{
initializeCatalogContainers(); IWEventRegistry.addItemHandler('/Catalog', 'OnReplicantAdded', handleNewCatalog);
}//function initializeDct()
//////////////////////////////////////////////////////////////////////
// Function: initializeCatalogContainers
// Description: Initializes the catalog containers on DCT load
// Parameters:
// None
// Return value: None
//////////////////////////////////////////////////////////////////////
function initializeCatalogContainers()
{
// Retrieve all of the Catalog containers.
var catalogContainers = IWDatacapture.getItem('/Catalog').getChildren(); // If there are Catalog Containers found, iterate through all of
// them and set them up.
if (catalogContainers)
{
for (var i=0; i<catalogContainers.length; i++)
{
setCatalogItemsReadOnly(catalogContainers.getName(), true);
}
}
}//function initializeCatalogContainers()
//////////////////////////////////////////////////////////////////////
// Function: handleNewCatalog
// Description: Handles the initialization of a new Catalog Container.
// Parameters:
// catalogItemObject - The item object for the new catalog
// container.
// Return value: None
//////////////////////////////////////////////////////////////////////
function handleNewCatalog(catalogItemObject)
{
setCatalogItemsReadOnly(catalogItemObject.getName(), true);
}//function handleNewCatalog()
//////////////////////////////////////////////////////////////////////
// Function: setCatalogItemsReadOnly
// Description: Sets the readonly attribute of the all of the items
// in the container passed to the value of the boolean
// passed.
// Parameters:
// catalogContainerName - The name of the catalog container to
// set the items readonly attributes for.
// readonlyBoolean - Boolean to set the passed container
// items readonly attribute to.
// Return value: None
//////////////////////////////////////////////////////////////////////
function setCatalogItemsReadOnly(catalogContainerName, readonlyBoolean)
{
// Set the readonly attribute of all of the items in the passed catalog container
// to the value of the readonly boolean passed.
IWDatacapture.getItem(catalogContainerName+'/AccyCat').setReadOnly(readonlyBoolean);
IWDatacapture.getItem(catalogContainerName+'/AccyTitleNomen').setReadOnly(readonlyBoolean);
IWDatacapture.getItem(catalogContainerName+'/MotProdLine').setReadOnly(readonlyBoolean);
IWDatacapture.getItem(catalogContainerName+'/PDSTitle').setReadOnly(readonlyBoolean);
IWDatacapture.getItem(catalogContainerName+'/PDSImageSet').setReadOnly(readonlyBoolean);
IWDatacapture.getItem(catalogContainerName+'/PDSImage').setReadOnly(readonlyBoolean);
IWDatacapture.getItem(catalogContainerName+'/PDSContentDesc').setReadOnly(readonlyBoolean);
}//function setCatalogItemsReadOnly()And I'm with Jonathon on the grey/white issue, I haven't played with it much, but it doesn't seem there is any way to control it.

~Jeff

nipper

Thanks for the code.

I agree it is a minor issue but training exceptions like this is a pain. It is easy
to tell someone when it is grey it is readonly, otherwise not.

re: FormInit, I am using it, but I did not include all my code.

Migrateduser

Curious, how is iterating through the children more efficient and/or more accurate than IWDatacapture.getItem('****').getChildren().length? That's what I use and it seems to work just fine.

Current Environments:
(1,2) TS 6.5 on W2K3
(3) Vignette V7 Portal on Solaris 9

jbonifaci

It just seems cleaner to me. Just using .getChildren() to get the length of the child array is like building an array just to get the length of it and then discarding it and rebuilding the array based on the length you just calculated.

~Jeff

Adam Stoller

Also, if there aren't any children, you might be dereferencing a null object and that would cause all the rest of the javascript to not get processed.

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

Adam Stoller

I just ran into this (TS6.5SP1 on W2K3 EE) and I believe the key element here is the event trigger onReplicantAdded process flow.
I'm in the process of opening a case with Support and will be supplying them our DCT and FormAPI code in the hopes that they can replicate the problem in house. (more info when I have it)

In our case - we have a form in which about 95% of the fields will be read-only (data being pre-populated from DB and form being used to QA and perform minor edits) - when the form loads up I traverse all existing fields including those in pre-existing replicant instances, and set the various fields to ReadOnly -- this works fine, they show up rendered in gray.

If the user chooses to add a new instance of any of the replicants, a variant of the same code I used before is being called to set the various fields in the new instance of the replicant to ReadOnly -- those show up in white - as-if you could edit them - but you cannot (so the ReadOnly aspect took-hold, but the proper rendering did not).

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

nipper

Sounds like it is a know bug (to DevNet) but may not have been reported to IW.

If they file a bug ID, please let me know so I can piggy-back on it. Jonathan may want
to as well.

JonathonG

That sounds promising, but it may not just be replicants, it may be re-drawing in general (which happens when a replicant is added). Our DCTs are 2 pages. When the DCT initially loads, the read only fields on page 1 are (usually) gray. But, a navigate to page 2 and back (usually) yields white, non-editable fields.

Just adding a bit more info. I'd love to piggy back, but I don't own our support relationship. For some strange reason the group that does is reluctant to open support cases.

Jonathon
Interwoven Developer
Allstate, Inc.

Adam Stoller

FYI - Support *has* been able to reproduce this from my source files.
There's some contention about setReadOnly() not being supported in replicants - but I (and the support person I was working with) contend that would be a bug in itself (besides the fact that it *does* work - it just doesn't do the rendering right).

I haven't yet received word of an official bug ID.

I'll keep you posted.

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

Adam Stoller

This is now officially filed as bug # 61745

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

getnaren

Got the solution

gzevin

This is now officially filed as bug # 61745

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

as far as I remember, I found this ages ago (actually, nipper was 1 yard away from me at that time) - and from what I heard, it was a known behaviour ...
Still am surprised that it was not filed as a bug before...

nipper

as far as I remember, I found this ages ago (actually, nipper was 1 yard away from me at that time) - and from what I heard, it was a known behaviour ...
Still am surprised that it was not filed as a bug before...

This thread started 1 1/2 years ago. So it may not have been quite as well known then. Besides, for as long as we worked together, did I ever do anything to give you the impression I paid attention to what you said ?

gzevin

This thread started 1 1/2 years ago. So it may not have been quite as well known then. Besides, for as long as we worked together, did I ever do anything to give you the impression I paid attention to what you said ?

sometimes it does pay to pay attention to what I am saying