Box v1 EOL - Will Crocodoc still work on old documents?

Hi. Suppose we have an application that is using Box v1 API to convert documents into assets (svg, etc) which get stored in our s3 bucket. Then we use this package https://github.com/box/viewer.js to create a Crocodoc viewer instance. We point that instance at a folder in our s3 bucket, and it downloads and renders the svg for us.

My question is, will this still work after the Box v1 EOL? I understand that our workflow for *generating* those svg assets will not work, but will the *already existing* ones still work? It seems to me that it *should* work, because the npm package (above) that provides the Crocodoc object is installed locally, but I just wanted to make sure. For example, maybe the Crocodoc object makes API calls to Box v1 behind the scenes or something.

vmaker

October 20, 2017 17:00

This should work. As long as all the assets are stored in an S3 bucket managed by you, and if you are locally hosting the crocodoc viewer, you should be able to use the crocodoc viewer to preview existing documents.

rombluewink

January 16, 2018 02:24

Will i still be able to call the old API despite the EOL to convert documents and download their assets localy ?

Our app is basically used 1/2 million healthcare professionals in France.

Comments