atk4 / warehouse Goto Github PK

When editing company data, one should be able to specify "next invoice ref".

When invoice is made "live" it should automatically take this value, but the company field should increment. For instance if "next invoice ref" was "INV1000293" then it advances to "INV1000294".

There should be separate numbering for sales invoices that are not "Posted" yet.

Category may not have 2 subcategories with the same name.

• Must fix atk4/ui#173 before that.

Add validation for at least some base fields. For example, many fields should be mandatory with a proper error message if left un-filled.

• EAN should only permit be A-Z0-9
• all currency fields should reject thousand separator (",") as an error.

It should be possible to set a "country" setting for the company, which may affect the following:

• locale, for displaying numbers.
• UI language, at least some of it.
• Validation errors
• Date formats

Sample brands are:

Karcher
Bosch
Makita
DeWalt
SmartRobby
Metabo
MTD

Sometimes items are sold before purchase invocies are entered. It's a normal occurence, but user should be warned about it.

We would like to have a warning message appear in the top menu:

• "Negative stock values for 4 items"

Clicking on the text should bring up the report showing up all stock items in a table with links.

I've tried the online demo warehouse app and it doesn't work (http://atk-warehouse.herokuapp.com/) - can't login with test/test.

I've then downloaded it from github (https://github.com/atk4/warehouse) and tried running composer on the downloaded file.
Has an error, because in the composer.json it needs "dev-feature/grid-status-fixes" which isn't available any more.

Running composer with the "*" as version downloads the most recent version of atk.
Opening index.php of the warehouse app gives me just error messages.
How can I get it running?

Anyone should be able to enter registration details to set up a new company with their own account.

business logic needs changin

• producer is a text field, no need to store it as an entity.
• user shouldn't be allowed to affect any stock count manually. He need to create 'Inventorisation' document across all articles, when it goes into effect, it adjusts all stock counts.
• something else here..