User authorization – change status, void, register payment
We made some additions regarding the user authorization.
1. Change status
If you want all users to approve documents before being able to trigger the fulfillment (SO, WO) or receive the items (PO), you can set up the document validation as Approved in the Administration > Localization:
Once you enable this, the users must change the status to ‘approved’ in the sales order and work order, if they want to trigger the fulfillment (if they want the missing items to appear in the fulfillment list):
And for the purchase order, the document status must be changed to ‘approved’ in order to be received:
Of course, you can change the status of the documents in a bulk:
Of course, you can control this on the user level as well! You can disable an operator to change the status of the document:
In this case, the operator won’t be able to trigger the fulfillment or receive the PO until an Admin, or another Operator approves the document:
The entered Sales Order won’t even have the option to change the status:
2. Void the document and Record payment You can also disable your users from voiding the documents or registering payments:
If you turn off these 2 functions, they won’t have the buttons for voiding the document or registering a payment on the right-side menu:
Now you have more restrictions you can apply as an Admin. Use them wisely!
JSON/XML Designer in ERPAG is a visual tool that will allow users to transform data from the ERPAG database into JSON or XML format. This can be further used for future integration with API services. This tool provides a user-friendly interface where users can define...
The biggest change we developed is Automatization and Customization. This change is a huge milestone for us, and we will publish individual instructions for using the new features in the upcoming period. This module is divided into individual wholes: JSON Designer -...
ERPAG has the ability to use Blockly Script to send or receive data via the HTTP protocol. Integration of two systems via API (Application Programming Interface) is always a complex process, especially for someone with little experience. In this blog we will explain a...
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.