Integration of css / cms api's with workfront which required specific endpoints

SK1415

We are working on integrating Workfront with OpenText using CSS and CMS APIs to store files or images on OpenText and access them from the Workfront side. However, we are encountering an issue where Workfront appends certain fixed endpoints to the base URLs, such as /files (which we have for the CSS API), /metadata, /search, /uploadInit, /upload, /thumbnail, /download, /createFolder, /serviceInfo, etc. These endpoints do not exist on the OpenText side, resulting in 404 errors when these appended URLs are generated.

Does anyone have a solution for this? Is there anything that can be configured or adjusted on the OpenText side to resolve this issue?

gvicari

@SK1415, I'm not 100% certain I understand your use case, but to access CSS residing content, you should provide the CSS URLs. If you cannot avoid Workfront appending to and basically corrupting/changing the CSS URLs, perhaps a solution would be to use a proxy that removes the appended path elements before submitting to CSS. Overall, I'm afraid this is something that would have to be fixed at the consuming side.

SK1415

Is there any way to find out about other clients or vendors who have completed this Workfront and OpenText integration integration, so we can reach out to them for assistance?

gvicari

You can reach out to your OpenText representative. If you don't know who that is, I can try to help you find them. I'll send you a private message to take this forward.

SK1415

Thank you! That would be very helpful. I appreciate your assistance in connecting with the right OpenText representative. Looking forward to your message.

gvicari

You should have received a personal message. Please let me know if you did not. Otherwise, I'm assuming we can continue the conversation via email. Cheers.