BUSINESS RULES ENGINE
The Business Rules Engine is a separate application before ISP-Invoice.
The application is created to enrich and/or transform data in the XML via customer specific business rules, right before importing in ISP-Invoice
It can also be used without ISP-SmartScan to enrich XMLs from ie. IDT, InvoiceSharing and other EDI-sources.
Getting started
Setting up the development environment takes some steps, which are outlined below.
### Installing dependencies
Ensure you have a virtualenv created and activated in the root-directory - virtualenv –python=python3 env - source env/bin/activate
Install the dev dependencies with ** - pip install -e “.[tests,pycodestyle,docs,dev,release]”
** Installing on Mac needs the quotes, where Windows/Linux might not. Details: https://zsh.sourceforge.io/Guide/zshguide05.html#l137
Run unit-tests
Ensure you have a virtualenv created and activated in the root-directory Simply run Pytest - pytest
Code coverage
To view how many code has been covered during tests we use Coverage
Ensure you have a virtualenv created and activated in the root-directory Run coverage - coverage run –source bre -m py.test Or to export to HTML - coverage html -d coverage_html
Command line tool
To start the BRE-tool via command line use the following command - bretool URL-TO-INFO-API Example: - bretool http://localhost:8000/bre/api/info
Optional;y add debug-information in log-file; - bretool http://localhost:8000/bre/api/info –loglevel=DEBUG
Optionally use a different log-file - bretool http://localhost:8000/bre/api/info –logfile=PATH_TO_FILE
1 maintainer
Metadata
1 maintainer
Release files for bre-next 0.22
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bre_next-0.22.tar.gz | 26.2 kB | Without provenance | Details for bre_next-0.22.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bre_next-0.22-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for bre_next-0.22-py2.py3-none-any.whl |
Total release size: 78.2 kB
Release files / bre_next-0.22.tar.gz
| Download URL | bre_next-0.22.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdf45bc2ad573b0b83f3d698e16b6e4b2b07864fa2b24ee3f7d0a8126067a545
|
|
BLAKE2b-256 checksum How to use checksums |
1b99ef132c58edc266726f8f6c129400d61e167e039f9fa6d79c6992612edbde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / bre_next-0.22-py2.py3-none-any.whl
| Download URL | bre_next-0.22-py2.py3-none-any.whl |
|---|---|
| Size | 52.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
586d2b3ceeb098d7c4d8e6d55a48a9db612d6d3ac1ac156128cec407b62286fe
|
|
BLAKE2b-256 checksum How to use checksums |
156838c62ee04d3fcd8a0e2dc135023f99b0caa1d8d87f143f5f4d70f6dc2b0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for bre-next 0.22
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
