LAPI - Attribute values not getting added in dauditnew table thru LAPI

[hanreb]

Hello,

IN LAPI, when we create a document, attaching a category to it, does the attribute values of the category get stored in the audit table(dauditnew table).

When I run a LAPI program in java, the attribute values are not getting added to the dauditnew table. But when I do it manually thru livelink the dauditnew table has the attribute values.


I tried two different ways to upload a document in livelink, using LAPI.



1) Create the document and attach category to the document by calling a single LAPI function ( one shot ) .

doc.CreateObjectEx(volumeID, objectID, doc.OBJECTTYPE,
doc.DOCUMENTSUBTYPE, "logfile.txt", createInfo, objectInfo)

2) Create the document using one LAPI function. Attach category to the created document, using another LAPI function.


doc.CreateObjectEx(volumeID, objectID, doc.OBJECTTYPE,
doc.DOCUMENTSUBTYPE, "logfile.txt", createInfo, objectInfo)

doc.SetObjectAttributesEx(lobjectID, catVersion)



In both the above 2 cases attribute values are not getting added to the dauditnew table, but they are getting added to the llattrdata table .

Any idea , why attribute values are not getting stored in the daudit new table.

I appreciate any help in this matter.

Thanks,
Sunu

 

[appnair]

I thought I would check this behaviour on my LL9.7 version of livelink.I have event auditing turned on in my system.I added a document and I attched a category to it with a small java program.Here's the output

Document  BrandNewDocWithCategory1 (189691)   Version Added   Admin   05/06/2008 08:54 AM 
 
   Version 1 added with description  
 
 Document  BrandNewDocWithCategory1 (189691)   Create   Admin   05/06/2008 08:54 AM 
 
   Created in Enterprise:BrandNewDocWithCategory1 
 
 Category  VM SDRL Documentation (152278)   Version 16 Opened   Admin   05/06/2008 08:54 AM

Then I went thru the gui and changed the value of the category:attribute to 2 and got this

Document  BrandNewDocWithCategory1 (189691)   Attributes Changed   Admin   05/06/2008 09:04 AM 
 
   Attribute VM SDRL Documentation[1].Documentation Code[1] was changed from '1.000' to '2.000'

Is that what you were expecting on initial creation.Out of box only attributes changed are audited in livelink.On initial creation it is not deemed as a change.

But I am guessing if you create the object and add a category,then change something on the new object's category and close the call with UpdateObjectInfo you may get your entry into dauditnew.I wil test that approach wnemI have some time

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[hanreb]

Hi Appnair,

Thanks for the reply.
Below is a description of my problem again.

When I add a document named audit.xml and attach a category (any category, here my category name is PTDI_DEV -13 attributes) to it, thru livelink UI, below is the result that I get from the database(dauditnew table)


select auditstr,valuekey,value1,value2 from llw.dauditnew where dataid=821468

I see all the values that I added to all my category attributes in the dauditnew table with the auditstr as ‘AttrChange’.

AUDITSTR,VALUEKEY,VALUE1,VALUE2
AddVersion,audit.xml,1,
Create,,Enterprise:audit.xml,audit.xml
CategoryAdded,310128,'PTDI_DEV',audit.xml
AttrChange,PTDI_DEV[1].BOX #[1],,'11'
AttrChange,PTDI_DEV[1].BU#[1],,'005'
AttrChange,PTDI_DEV[1].FEIN[1],,'94-1648752'
AttrChange,PTDI_DEV[1].COMPANY NAME[1],,'ROBERT HALF INTERNATIONAL INC.'
AttrChange,PTDI_DEV[1].EIN/ACCT #[1],,'11'
AttrChange,PTDI_DEV[1].TAX TYPE[1],,'940'
AttrChange,PTDI_DEV[1].TAX YEAR[1],,'XXX'
AttrChange,PTDI_DEV[1].DOC DATE[1],,D/2008/1/6:0:0:0
AttrChange,PTDI_DEV[1].DOC TYPE[1],,'DEPOSIT CYCLE'
AttrChange,PTDI_DEV[1].STATE[1],,'AL'
AttrChange,PTDI_DEV[1].FREQUENCY[1],,'QUARTERLY'
AttrChange,PTDI_DEV[1].QUARTER[1],,'11'
AttrChange,PTDI_DEV[1].PURPOSE[1],,'11'



If I perform the same set of operation thru my LAPI program, I mean add a document and attach category with values to it, I see only two records going into the dauditnew table. The attribute values with the auditstr=’AttrChange’ as you see above is not there in the dauditnew table . But upon completion of the LAPI program, in livelink UI the document ‘logfile.txt’ is available in livelink with all the attribute values added to the category.

select auditstr,valuekey,value1,value2 from llw.dauditnew where dataid= 821844


AUDITSTR,VALUEKEY,VALUE1,VALUE2
AddVersion,logfile.txt,1,
Create,,Enterprise:logfile.txt,logfile.txt



Is this the way LAPI would behave ideally. Or what would be wrong in what I am doing in my LAPI code.
Is there a way to get the attribute values into dauditnew table thru LAPI.

Looking forward for a reply

Thanks,
Sunu

 

[appnair]

The only thing I would suggest is if you have done your howework/research send OT the results and ask them why Lapi is behaving differently,if they think it should be done as you think it should probably you can talk them into giving you a patch.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[appnair]

Just so that other forum memebrs may know that this qn has been addressed in the OT KB.The long and short of it is they have a patch /issue number "LPO-376".

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[ggriffit]

Do you have the link for the KB discussion for reference ?

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[appnair]

https://knowledge.opentext.com/knowledge/llisapi.dll/open/765428

I beleive this is it

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[hanreb]

Thanks appnair and ggriffit for the help.

I did talk to open text customer support.
Opentext does not have a patch for livelink 9.7.0, which is my version of livelink.

I will get the patch to incorporate into my system, as soon as they are ready with the patch for livelink 9.7.0.

Thank You for your support,
Sunu