* support workflow activities
* minimal changes
* add Workflows and services
* add state semantics
* rename fille
* add info the node
Co-authored-by: elsiosanchez <elsiossanches@gmail.com>
* Adding the option to change Warehouse and Price List
* add service
* support service
* add Warehouse
Co-authored-by: elsiosanchez <elsiossanches@gmail.com>
* Add License to files inside project
This is recommended by GNU/gpl v3 according with it: https://www.gnu.org/licenses/gpl-3.0.html
```
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/licenses/why-not-lgpl.html>.
```
* Remove space
* Improve request util
- Improve request util based on basic and generic request
- Add ADempiere request layer (use it as template for others)
- Add Release information from github
- Chamge ADempiere request API fos a custom request
* Add release version
* Add rt-3.2 version
* Minmor change
* Add default action for release
* Add echo
* just a test
* Test release
* Add Release no version for test
* Add test for publish
* Add release no from tag
- Use default request utility from legacy source code
- Improve calling structure
- Implement posibility of create endpoint for request
- Allows define a generic calling for backend service
- Remove unnecessary functions
* add complete order from collection
* call the edit line fields only when they are displayed
* unnecessary calling of customer fields
* minimal changes
* Add point id to the route on initial load
Co-authored-by: Elsio Sanchez <elsiosanche@gmail.com>
* Improve source code and define structure for api
Note that currently does not exist a way for spared api and search from
backend or push, this pull request want reorder use of api by
functionality or tool:
- All inside ADempiere folder is dedicated for adempiere functionality
- ADempiere/dashboard: use this path for add your api resource for all
related with dashboard, note that already exist a file named
dashboard.js with standard dashboard for ADempiere, if you want to add a
new dashboard just create a new file <dashboard name>.js for gest info
from backend
- ADempiere/form: used for all form, for now exist the first
implementation named price-checking.js that matched with
components/ADempiere/form/PriceChecking, if you want to add a new form
just add a new file here
- ADempiere/browser.js: browser is a native functionality for Smart
Browser tool, just add here all functions related for browser
- ADempiere/private-access.js: just handle private access, will be used
for add role table access and record access (nice to have)
- ADempiere/process.js: related with all action for process and get
information from server like getProcessLog and others
- ADempiere/report.js: get info like getReportOutput from parameters
used for window report and change print formats
- ADempiere/rule.js: for now is used for dispatch callouts from server
but will be implemented for run rules directly for client on languages
like javascript, kotlin and groovy
- ADempiere/system-core.js: just get generic functions like
getWarehouseList and organization, also can be used for get langages and
other infor from server
- ADempiere/values.js: get info like lookup list, default values and
other values like systen configurator
- ADempiere/window.js: all functions related to window like record log,
workflow log and other infor that can be used for container
- ADempiere/persistence.js: handle standard CRUD for all entities and
implement functions like getTranslation from entity
* Improve source code and define structure for api
Note that currently does not exist a way for spared api and search from
backend or push, this pull request want reorder use of api by
functionality or tool:
- All inside ADempiere folder is dedicated for adempiere functionality
- ADempiere/dashboard: use this path for add your api resource for all
related with dashboard, note that already exist a file named
dashboard.js with standard dashboard for ADempiere, if you want to add a
new dashboard just create a new file <dashboard name>.js for gest info
from backend
- ADempiere/form: used for all form, for now exist the first
implementation named price-checking.js that matched with
components/ADempiere/form/PriceChecking, if you want to add a new form
just add a new file here
- ADempiere/browser.js: browser is a native functionality for Smart
Browser tool, just add here all functions related for browser
- ADempiere/private-access.js: just handle private access, will be used
for add role table access and record access (nice to have)
- ADempiere/process.js: related with all action for process and get
information from server like getProcessLog and others
- ADempiere/report.js: get info like getReportOutput from parameters
used for window report and change print formats
- ADempiere/rule.js: for now is used for dispatch callouts from server
but will be implemented for run rules directly for client on languages
like javascript, kotlin and groovy
- ADempiere/system-core.js: just get generic functions like
getWarehouseList and organization, also can be used for get langages and
other infor from server
- ADempiere/values.js: get info like lookup list, default values and
other values like systen configurator
- ADempiere/window.js: all functions related to window like record log,
workflow log and other infor that can be used for container
- ADempiere/persistence.js: handle standard CRUD for all entities and
implement functions like getTranslation from entity
