bkper / bkper-issues

Feature requests and enhancements to existing bkper modules can also be filed here.
https://bkper.com/
2 stars 0 forks source link

Attach more than one file per transaction #39

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
It will be useful because a transaction sometimes involve an invoice and a 
payment proof/receipt.

Original issue reported on code.google.com by m...@nimbustecnologia.com.br on 29 Jul 2015 at 1:59

GoogleCodeExporter commented 8 years ago
Great feature to attend

Original comment by vanespen...@gmail.com on 8 Aug 2015 at 9:14

Jacobvdb commented 8 years ago

You can add external URLs to add more than one reference.
http://help.bkper.com/article/31-bkper-record-guide

zoqui commented 8 years ago

Is the [urls] property available in the api? It seems that API (batch) includes the url in the transaction as we see the link in the bkper, but it does not include it in the transaction list response. Something like a 'write-only' property.

maelcaldas commented 8 years ago

Hi Marco,

We still did not expose the attachment URL at the API due to security reasons. To provide it, we would need to send a temporary link or an authenticated way to call the image service.

Cheers,

Mael

2016-01-25 13:09 GMT-02:00 zoqui notifications@github.com:

Is the urls property available in the api? It seems that API (batch) proper includes the url in the transaction, but does not include it in the response (transaction list)

— Reply to this email directly or view it on GitHub https://github.com/bkper/bkper-issues/issues/39#issuecomment-174537288.

zoqui commented 8 years ago

hi Mael, thank you for the quick reply. I´m not referring to an attached transaction resource link (image/pdf), but the one user can freely type as a input transaction text (http://help.bkper.com/article/31-bkper-record-guide). In general, url will refer to a non bkper uri and therefore authentication should be made by the remote application (when applicable) example:

It can write it but can´t read it.

[]´s

maelcaldas commented 8 years ago

Hum... I got it!

This one would be safely exposed. There is list of parsed URL's on transactions entities, but still not exposed on API. I will expose it and get in touch. Hope have this done at next deploy, which occurs usually once a day or two.

Cheers

2016-01-25 14:57 GMT-02:00 zoqui notifications@github.com:

hi Mael, thank you for the quick reply. I´m not referring to an attached transaction resource link (image/pdf), but the one user can freely type input transaction text ( http://help.bkper.com/article/31-bkper-record-guide). It in general will points to a not bkper uri and therefore authentication should be made by the remote application (when applicable) example:

It can write it but can´t read it.

[]´s

— Reply to this email directly or view it on GitHub https://github.com/bkper/bkper-issues/issues/39#issuecomment-174582100.