Downloads

[Anthony Medlock]

I was talking to a client about Netshine and we looked at implementing it to his website, however , one facility that ended up in us not using it was the ability to have downloads associated to the client.

i.e. If a client ordered a "DOWNLOAD" then this download would be A.pdf, if another client ordered a download this would be B.pdf, i.e. each download was already created for the client outside of Netshine, but they could only download it when they had paid though the system. The other feature would that once the client had paid for it, it was then publicly available via a link.

i.e. imagine a certificate with a clients name on it, instead of a program or other download.

[netshine]

I don't really understand the requirement here. If you are going to create a document specifically for the client after they've paid, why not just send it to them or publish it on your site? I'm not sure what you want Billing to do...?

[Anthony Medlock]

Basically give them the customer the option to download it only when they have paid, at that point it then also becomes available to the public too. Its just the way this works.

or

The download is already prepared for the customer, but must not become available before it is paid for, when they have paid for it, it is also available to the public for free.