How to set email properties with the Content Server rest api

In your screencap, you are initializing an AttributeGroup that corresponds to a Category: Attribute so is Email Properties a Category that you have created or does OT use a hidden system category of sorts?

Obviously, if you want to attach additional the rest api allows that hence asking

if you run ?func=attributes.dump does a category called Email Properties show up?

OTEmailProperties is the table in the OpenText CS database where e-mail properties are added when you add a file as type 749.

The reason why I always did set those properties myself instead of let CS doe it is because CS is verybad in getting the e-mail body correctly.

Unfortunately if the restapi does not support what soap api supports then you are left with some options

You could open a ticket with OT and show them the missing parity between rest and soap

You could add the code in rest api using oscript. I am a oscript developer so I would have done that

You could enforce a trigger in the creation and take that code in your program and write it directly into the table yourself

You could look and see if OI supports 749. In 2015-17 period I looked at OI and I extended it because at the time OI did not support 749 but it may now be supported. I think many people asked me how I did it and I shared my approach in the old forums

What I'm trying to set are the properties that you get when you retrieve node information from an node with type 749

https://forums.opentext.com/forums/developer/discussion/comment/968548#Comment_968548

I don't want to make custom code because that is problematic when upgrading to newer version. The best would be to have something that works out of the box. It did work in ELS and CWS so the reason is unknown to me why some things are missing in the REST API. It is to bad that OpenText labeled CWS as depricated and is forcing customers to use REST where functions are missing.

OI = Object importer?

OI is Object Importer previously when LAPI was deprecated OT did not pull that code base until about 10 years . AFAIK Sap is one of the biggest money makers to OT their current offering talks to CS over SOAP until they re write those interfaces I would think the deprecation just means you can’t raise bugs 🤣

Just see if you can add a email to a OT Transport and see if you can import it . If that succeeds XMLExport/Import not connected to OI is an option as well

try using {{csurl}}/v2/nodes/:nodeid/emailproperties (GET Method) to read email properties instead of node properties.

@Visal_k … I already tried that and I even used the same structure on a createnode request but then it still does not work.

Okay but in a snippet you posted, you are using node properties api which does have "emailproperties" but I too have found that to be unreliable. However, if you use the emailproperties api then email properties returned are correct. So maybe try that.

Also while creating email node, have you tried passing the properties data under "EmailProperties" key?

@Kees van Spelde Have you tried sending the create node request with data in following format?

body={"type":749, "parent_id":2000, "name":"New email", "roles":{emailproperties": {"properties":{"version":5,"Subject":"<Subject>"}}}}

Yes but not with type 0 …. 0 = folder?

@Vishal_K Your amended code works I used JSONLINT to understand the error so the correct payload is this you were simply missing a quote on emailproperties

{"type":749, "parent_id":17747346, "name":"New email", "roles":{"emailproperties": {"properties":{"version":5,"Subject":"<Subject>"}}}}

Very good to help the forum…