Search Results

Existing scheduled jobs should only be updated by users with access to the code base. Viable updates for scheduled jobs are changing description, enabling/disabling the job, it's email notification on failed run, or changing the "Cron interval", that specif...

Scheduled jobs should ONLY be deleted by administrators with access to the code base. If a scheduled job is no longer needed, rather than deleting it, disable it, leaving a chance for it to be reactivated if ever needed. 

Some scheduled jobs can be run manually from the ERP, if a need for that ever arises. Manual runs should not be the norm, as scheduled jobs are configured to auto-run atregular intervals. To run a scheduled job, go to scheduled job's edit page and look for th...

Existing event actions should currently never be updated by anyone else but the developers. When a need arises for a different functionality, a new event action should be created, deactivating the old one.

Existing event action should never be deleted, instead being deactivated.

System options are settings that are used by the administrators to customize the ERP system. These options should only be managed by people, who understand their purpose and context, as changing a key option could lead to severe issues within the ERP, if done...

This action requires the "create system option" permission.  A new option can be created by accessing the creation form on the system options page through the "Create new" button. You get redirected to the creation form page, where you can input required i...

This action requires the "update system option" permission. To update an existing system option, find it in the table, and click the "edit" button at the end of it's row. This takes you to the editing form, where you can update the option's name, slug, des...

This action requires the "delete system option" permission. To delete a system option, use the checkbox to select it, and then click on the "trash" icon, that appears in the top right corner of the page. You will be asked to confirm you want to delete the sys...

This action requires the "create print signer" permission. New print signers can be created through the Create new print signer form. There can be only one print signer of a document type's template  active at any given time. The selected "Signer" can be ...

Print signers are users, who are responsible for signing certain documents.  The "print signers" table is used to define, which user is signing which document print and for how long (from and until dates).

This action requires the "update print signer" permission. Past signers cannot be edited. Signers have the "Active/Inactive" state, determined by the "Active from" and "Active to"  dates. If a signer is inactive, the entire edit form is disabled, to prevent c...

In the ERP system, partners are used to refer to external entities, usually other companies. with which the organization interacts.  Partners are used to represent customers, suppliers, logistics providers, or company subsidiaries.  Partners are managed in...

This action requires the "delete partner" permission. Partners should never be deleted, unless they are a duplicate partner with no history (no linked order, invoices...). Before any partner is deleted, the accounting department should be contacted for confor...

Holidays in an ERP’s HR module serve as a centralized reference for public, regional, and company-specific holidays, ensuring consistency and compliance in workforce management.  Holidays are marked on the HR dashboards with the "🎄" icon. Holidays are used...

This action requires the "create holiday" permission. New holiday entries can be added through the "Create new holiday" form, which can be found above the "holidays" table or directly "here". When adding a new holiday, the only information needed are the h...

This action requires the "update holiday" permission. Holidays should not be updated due to their use within the HR module. Dates of existing holiday entries should not be updated, as changing the dates could impact planned employee vacations or workdays. How...

This action requires the "delete holiday" permission While holidays can be deleted if necessary, it is strongly recommended to avoid deletion to maintain data integrity and prevent disruptions in processes such as payroll, attendance, and compliance tracking,...

This action requires the "create holiday" permission. Holidays can be added one at a time through the "Create new" form or they can be generated for the entire year through the "Add holidays for year" form. To generate holidays for a select year, first we ...

Goods receipts are primarily used to "receive" materials into stock. Goods receipts are used for documenting and confirming the receipt of goods or materials into inventory, ensuring accurate records and supporting various processes within the ERP.  They u...