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

From OT CS unable to modify/edit the values of attributes of a category for a document which are not

Vrushu

Hi All,

AM trying to edit the values of attribute that are not set through my webService .

like say category = catgeory1 and having attributes A,B,C,D,E,F,G all are type of String .

so through my web service am setting value to A as below.

if(res.getType().equalsIgnoreCase("String") ){

StringValue A = (StringValue) categoryTemplate.getValues().get(0);

A.getValues().clear();

A.getValues().add("abc");

}

So am setting only one attribute for a category1.

Then am viewing the doument from OT CS adminstrator, and for the document ,category1 is applied and the value of A is also set and is editable.

But rest attributes are not editable.

Thanks in Advance.

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Girish,

This sounds like the known issue LESAPI-1820 which was resolved in the 2015-03 update for Content Server 10 and 10.5.

Kyle

Vrushu

Thanks Kyle ,

Please let me know from where can i get the patch/ fix mentioned?

Regards,

Girish

Kyle_Swidrovich

Girish,

As noted, this is resolved in the 2015-03 update for Content Server 10 and 10.5.

If you’re on 10.5 SP1, use Cluster Management to move to the latest update.

If you’re on an update of 10.5 earlier than SP1, or are using 10.0, you will need to download the latest update from the Content Server patches area of the Knowledge Center:

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=2394878&objAction=browse&sort=name

This is the issue in question from the update readme:

Issue LESAPI-1883|LESAPI-1820: Setting a category attribute to NULL via Web Services renders the attribute uneditable in the web UI

Affected Files:

\module\services\ospace\docmanservice[.oll]

Regards,

Kyle

Jatinder Panesar

We have similar issue where we can not set <none> value using webservices. I can set any other value from the drop down list but couldn't reset the values by passing NULL or null or empty string to clear. Any thoughts?

Appu_Nair1

The <None> is a visual indicator the livelink webpage knows how to show.If you have a popup and you apply it without setting it wouldnt it show in the GUI? Or are you saying if you apply the category using GUI you see <None> and with your wsapi attempt it is all messed up?.It is not a valid value to any livelink operation.If you create a value called None it can be set.

from the weblingo page that builds it

<SELECT CLASS="selectMenu" ID="_1_1_2_1" NAME="_1_1_2_1" ONCHANGE="markDirty();">
<OPTION VALUE="" SELECTED><None></OPTION>
<OPTION VALUE="Yes" >Yes</OPTION>
<OPTION VALUE="No" >No</OPTION>
</SELECT>

Jatinder Panesar

If via webservices, I can set value to 'Yes, it sets the value but if I try to reset back to <None> I cannot using web services. However via GUI we can reselect back.

I would like to understand how the value can be set back to <Noine> using web services.

curtis.robinson@capspire.com

Hello,

Iam working with a new OpenText 10.5 SP1 2015-12 instance which still experiences the 'uneditable" attributes on categories where some attribute values are populated by a web service. attributes that are left blank are uneditable through the UI. I have done a sys report and verified the required hotfixes and updates are installed that you mention should have fixed this.

the system is running on a SQL server database. that should hav no pearing on this issue right?

Thanks,

Jim Hewitt

Hello Curtis,

Is this happening to recently modifed attributes from CWS, or ones that were modified through CWS prior to applying the required updates?

curtis.robinson@capspire.com

Hi,

I opened a support ticket and yesterday applied patch pat105000736 per Support's instructions.

We then ran more tests using the web services to update category attributes. Still no-success. any attributes that were left null during the web services update were rendered un-editable through the UI.

I'm setting up to collect logs and try the operation again.

Kyle_Swidrovich

While ok for a quick test, patch 736 is really only intended for 2014-12, although it will likely have no impact on your 2015-12 system given that the code should be the same.

Please remove patch 736 and work with a standard 2015-12 system for further troubleshooting efforts.

Support may request a copy of your install directory to allow them to test against your exact codebase.

Thanks,

Kyle