We recently participated in a pre-market analysis exercise carried out on behalf of a large Social Housing Landlord. They had recognised that, whilst their main line-of-business application does have a document storage capability, it fall some way short of meeting their compliance obligations in terms of retention, archiving and disposal features. The wanted to explore how an integrated EDRMS would enhance the capabilities of their existing systems.
Many suppliers have told me ‘Its SQL Server, no problem to interface’ and I generally tell them to pop back when they can show me, would two weeks be enough?
As a Micro Focus Gold Partner, we’re proud that EDRMS-as-a-Service solutions are based Content Manager. It’s a best-of-breed EDRMS and it is probably unmatched in terms of functional capability, including integration options. I’ve been intending to sit down an explore the REST API for a little while, and this pre-market analysis exercise gave me the perfect excuse. So I span up test server and started to explore…
As a Micro Focus Gold Partner, we’re proud that EDRMS-as-a-Service solutions are based Content Manager. It’s a best-of-breed EDRMS and it is probably un-paralleled in terms of functional capability, including inegration options. I’ve been intending to sit down an explore the REST API for a little while, and this pre-market analysis exercise gave me the perfect excuse. So I span up test server and started to delve in…
The first thing to note is that there is oodles of documentation and – more importantly – code samples! I was delighted find an AngularJS “Tree View” sample: that would certainly hit the spot with regard to one of the requirements articulated by the Social Housing Landlord.
The API conforms to the OpenAPI specification which means it’s self-describing, and that you can use code-generation tools like Swagger to help you compose your API calls.
The Swagger interface reveals that there are 97 objects that we can programmatically interact with, each with as many as four operations we can invoke. That shouldn’t surprise us. Unlike with some EDRM systems, the API is not an after-thought. It’s an itegral part of the product: the standard Web Client and Webdrawer interfaces are built using the same API.
As daunting as that sounds, it’s surprising easy to use. Within minutes having the server set up, I was searching for records using a test harness. There’s plenty more to explore, but it’s certainly given me some great ideas about how we might enhance our products in the future.