legalpride
Feb 19, 2018

Question/Suggestions

3 comments

 

Document assembly : Will you be considering document assembly in the documentation section for example, merging customer and supplier data with certain standard documents?

 

Transaction history : How will you deal with transaction history in the data model and interface for example, transactions from previous years etc?

 

Archiving : How will you deal with transactions to archive from the system after some years and maintain data integrity?

Steven Sitas
Feb 19, 2018

Hi Andre,

1. Document assembly - you will see this functonality in v1.14 and v1.15

2. Transaction history - this is already in the data model and in the BPs.

3. Archiving - this will be in v2 and will also include MIGRATING functionality

 

legalpride
Feb 20, 2018

 

Thank You Steven, The a360 Documentation explains the data model very well. I can see that a lot of work went into the documentation. it’s clear and to the point. I will spend more time on the documentation first in the future. I’m impressed with the product, quality and meticulous approach.

Andre

Admin
Sep 1, 2018

BTW will you be releasing part of V2.0 as Open Source also?

New Posts
  • Admin
    Sep 1, 2018

    Hello, I observed that you are using values for database action like: 1 for Add 2 for Edit etc. Instead of this we should use Constants/Enumerators. For example for Add we can create a Constants/Enumerators variable called dbAdd (DB_ADD) = 1 It is easier to read such variables and understand instead of values. Just my thoughts.... Yogi Yang
  • legalpride
    Feb 20, 2018

    Thank You Steven, The a360 Documentation explains the data model very well. I can see that a lot of work went into the documentation. it’s clear and to the point. I will spend more time on the documentation first in the future. I’m impressed with the product, quality and meticulous approach. Andre

computerplus

Leoforos Dodonis 43,  45221

IOANNINA - GREECE

Registered VAT ID: EL084190121

sales@computerplus.gr