Categories

System version

6.9

Version: 6.9

Changes in list configuration

The configuration of the list has been changed. In addition to the existing methods so far, that is, generating a list from a function or document type, you can also use a wizard that allows you to select the columns you want to add to the list.

This allows building lists more easily by selecting only the columns you need, without having to remove all unnecessary columns generated from a function.

Expansion of the control of workflow step executors

Until now, it was possible to indicate a field on the form, which contained users or elements of the organizational structure, as executors of the workflow step. Standard operations were available, i.e. any person or any person from the listed elements of the structure (departments, positions, etc.). It was problematic to create more elaborate conditions, e.g. that the step should be performed by any employee but from each element of structure.

In the new version, an option has been added for the step executor “Any of each”. It allows you to indicate that the executor of the workflow step should be any person from any department. The best way to show this is to fill in the field Organizational Units as yes on the form:

This workflow step must be approved by any person from the administration department, any person from the controlling department, any person from the logistics department and any person from the marketing department. That is, a total of four people must approve the step, each from a different department.

Changing the presentation of workflow execution

Due to the appearance of pending actions on the workflow and the increasing use of automatic operations with actions, the presentation of actions on the workflow has been expanded.

Two additional statuses have appeared in the list:

Pending execution – this status allows you to find all actions in the workflow of the type “Action pending” that are waiting for a condition to be met. This will make it easier to stake out the workflows that have been waiting a long time (several weeks or even months) for the condition to be fulfilled.

Failed to execute – this status shows all those actions that failed to execute for some reason. The reason could be the lack of step executors in the next action, an action error, etc. In the case of a sequence of automatic operations containing actions, this status will make it easier to find those steps that failed to execute correctly.

The status of the document after the process is started

Very often there is a need for a document to have a status as soon as it is saved and launched, even before the first action of the workflow is performed. Nowadays, when implementing integration with KSeF (National e-Invoice) system, it is even more important because the documents go into the system automatically so the status at the start makes it easier to manage them.

In the new version there is an option in the process configuration that allows you to set the status of the document at the start of the process.

Expanding KSeF integration

Archman continues to improve the integration of Navigator with KSeF. There are two minor improvements in the current version:

Action Send XML to KSeF

Often there is a need to reprocess a document downloaded from another system or prepared in another process. There is already generated an XML file that conforms to the KSeF structure and just need to send it to the system.

 

The new action works exactly the same as sending to KSeF the data from the form, but you do not need to configure the KSeF half and only indicate the file with the attachment. Like the older action, this one also records the session number in the indicated field (Session Reference Number option)

Extension of the Download from KSeF action

The KSeF system does not provide a visualization of the invoice as a PDF file. You can only download an HTML file with the invoice visualization. This solution is not always the most convenient, sometimes it is better to generate a PDF file yourself based on the invoice data than to use an HTML file.

In the new version, an option has been added to the Download invoices action, which allows you to control whether the system should generate an HTML file or not.

Archiving of payments

The Payments module has been expanded to include the ability to archive old payments. The mechanism works analogously to that for documents. The system operator can select the archiving option from the menu, which will cause the selected payments to disappear from the current list and be visible only by switching to the “Show Archive” mode.

However, it should be noted that the Edit Procedure option allows you to edit the procedure template. The NAVIGATOR system creates a copy of the procedure template and this copy is used to process the document. Changing the procedure template does not directly affect the procedure already running on a particular document.

Easier access to editing system elements

Until recently, the system administrator had access to edit from a form via an option in the More menu on the document. However, if they wanted to edit a document type or workflow procedure, they had to go to Settings and search for the appropriate item in the list.

In the current version, the Edit Document Type and Edit Procedure options have been added to the More menu. This allows us to quickly and easily go to edit a specific item without having to search for it in the system.

However, it should be noted that the Edit Procedure option allows you to edit a procedure template. The NAVIGATOR system creates a copy of the procedure template and this copy is used to process the document. Changing the procedure template does not directly affect the procedure already running on a specific document.

Menu