replacing new node content from base64

yaronlu · 2025-03-19T12:45:53+00:00

There was an error rendering this rich post.

Hi,

I am trying to add signiture on any pdf loaded to content server (Ext. ECM 24.2).
I managed to send the node as base64 string to the customer's Signer server,
and I return to Oscript the Signed doc as Base64.
Now I am trying to replace the content of the newly added file (DAPINODE) with the decoded Bytes i got from the signed base64 doc.

How can I do the replacement of the node content? I dont want to add version because the customer wants to save only the signed doc version.
If there is another way to achieve the scenario i described, i will be glad to hear about it.

Any way, I will appreciate your help.

Thanks,

Yaron

Find more posts tagged with

Comments

appuq

Supported ways of node manipulation include adding a version or rendition. If you change the content of a node then OT will not qualify for all the stringent standards they are known for and most likely it may void your warranty as well.

Rendition means a Version tied to a specific version so you could create a Rendition called "Signed" and put it as your signed stuff.

Unsupported ways will be something by which you replace the file although nowadays OT puts a checksum on a version and it may not serve a manipulated file and it will be almost very difficult if you were on OTAS.

yaronlu

Hi Appu, and thanks for the fast reply.

I thought inplementing by saving the base64 as file in the content server file system and then uploading it to CS.
In this scenario I am stuck at the phase of converting the base64 to file and then uploading it, and all of that
from Oscript.

Can you please send me some snippet of implementing my request with AddVersion?

Thanks again,

Yaron

appuq

I am not fully following the thought process

You have a Word Document in OTCS
You sent the Current Version of that Word Document to a Signing service as Base64 is a requirement of that interface
That interface returns it as Base64 again is that a limitation of that interface?
So in the Oscript level, the File is Base64 but you don't know how to make it into a Word MIME?

I might have to look in my Oscript files but it won't be fast all I think I would do is ask CHATGPT how to base64 a file to its real MIME.There are plenty of AddVersion Oscript samples including ones I did , or now Reiner Merz puts out code day in/day out in linkedin so I would check there as well.