Hello,
i would like to ask few questions to team responsible for
developing
"Plugin architecture : Creation of a real architecture for GLPI
plugins". Are there at least draft of guidelines for developers,
how to
write plugins for new plugin architecture? I am asking this
because
current Financial-info-module is inflexible and insufficient for
my
needs. Thus i would like to write alternative one, which would
fulfil
needs for invoices simultaneously for European Union and other
countries. Also such a module would have to be "kind of" object
oriented. Let me explain, how i imagine it should look like on
the
graph:
Bought
hard/software
|[0]
object -------> Blob object
(Invoice data) [1] (Scan of invoice)
|
-----------------------------------------------
|[2] |[3] |[4] |
hardware <=> Working
<=> license something
store [5] PCs,LAN [6] store else ?
| | | |
-----------------------------------------------
|[7]
Salvage,
removed
from
evidence
[0] manual entering invoice data
[1] scan of invoice document to BLOB object instead of regular
file will
simplify backup of data - only DB dump needed
[2] option for manual entering data for devices that are waiting
in
store as e.g. spare parts, and ability to link them with invoice
object.
[3] option for linking devices in GLPI/OCS with invoice object
[4] option for manual entering data for licences that are
waiting in
store as e.g. spare licences, and ability to link them with
invoice
object.
[5] option for moving objects from hardware store to GLPI and
the other
way, keeping properties and link with invoice objects.
[6] option for moving objects from license store to GLPI and the
other
way, keeping properties and link with invoice objects.
[7] option for removing device from evidence (e.g. old PC's) but
keeping
history of that equipment.
Tell me what do you thing about that
Another question, what exactly is Accountant module? Has
it something
common with invoices?
--
Kind Regards
Patryk Benderz
IT Specialist
ERSTE Securities Polska S.A.
+48 22 538 6292
Linux registered user #377521
"...if something can go wrong,
it will, except of a prototype,
where if it can go right, it will..."
Engineer's Law.
This message and any attached files are confidential and intended solely
for the addressee(s). Any publication, transmission or other use of the
information by a person or entity other than the intended addressee is
prohibited. If you receive this in error please contact the sender and
delete the material. The sender does not accept liability for any errors
or omissions as a result of the transmission.
_______________________________________________
Glpi-dev mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-dev