Combination View Flat View Tree View
Threads [ Previous | Next ]
Generate documents from URLs
toggle
Generate documents from URLs
2/21/10 5:24 PM
I'd like to make a suggestion for the server.

I've used the webservices API to create new projects and generate documents. What would be really nice however is, instead of having to use webservices is to simply have the enterprise server parse a url and return a document.

The URL should specify the document, return type, required arguments and so forth.

This feature would be nice so that I could generate links and simply post them on either a website or email to a client.

I've been playing around with yuml and they do a great job of basically treating urls as first class commands. take a look at yuml.me and how they render documents from urls. Different domain obviously but the right direction i think.
RE: Generate documents from URLs
2/24/10 10:00 PM as a reply to peter g cresswell.
Hi Peter,

We introduced something like this back in version 1.1 if I remember correctly. We made it possible to add parameters and document names to the url but it didn't quite return document as you suggest. It simply kick started the generation process so that the user bypassed the steps required to generate a document. It wouldn't be a big step to return the document.

In the scenario you have outlined how do you control access to documents. It could be a problem if it was easy to 'guess' parameter data based on what has been provided previously. Do you see any sort of custom authentication layer that would sit in from of the call that would check that the user requesting the document is authorised to do so?

Regards
Val
RE: Generate documents from URLs
2/26/10 2:02 PM as a reply to Val Cassidy.
My use case was to call the url from our sugarcrm system which already has a user authentication system. Security is an interesting concern and one I don't really have an answer for. I suppose there could introduce a concept of "public" verses "private" documents where "public" documents would be eligible for public generation. Defaulting to private would ensure that you had to explicitly specify if a document was publicly accessible.

Other than that, you could put ip filtering on the request I suppose and restrict access that way.

Or you could have a document based or system based password. I imagine you could do a document based password which the user would then have to provide prior to obtaining the document.

I like the idea of the having three options: private (no URL generation), authenticated (either IP based or password based) and public (no authentication required). In my case, the server was not publicly accessible outside our network so I wasn't worried about privacy but it is a real concern for a number of orgs.
RE: Generate documents from URLs
3/1/10 11:16 AM as a reply to peter g cresswell.
Hi Peter,

Let me take a look at the code that we introduced in the earlier version and I'll try to get that process documented. I suppose there are a number of ways that security can be implemented with various settings that can be applied at the project or document level. For a basic implementation it might be possible to allow access to documents generated in this way by means of an overall configuration setting.

Another alternative is to use a document repository such as Alfresco to store the generated document. This might tie in if you are synchronizing sessions between SugarCRM and Alfresco. I'll try to get back to you this by the end of the week.

Cheers
Val
Copyright © 2008 - 2010