...
The Web-client uses a typed form for creating/editing messages, which has two display modes-full screen (Fig. 1) and modal window (Fig. 2).
Fig. 1 – full screen mode Fig. 2 – modal window form display
...
Fig. 3 – elements of the order creation form
...
The data input area is divided into several blocks, the contents of which depend on the type of message (Fig. 2). Table 1 describes the blocks for contracts, MAs, reports and statement requests.
Fig. 4 – example of information blocks
...
Fig. 5 – required and optional fields
...
Fig. 8 – filling out the Master Agreement Number field
...
As a result, the main form will indicate the identifier of master agreement (Fig. 10,1), fields Party 1 of the master agreement and Party 2 of the master agreement will be filled automatically (see Fig. 10,2).
Fig. 10 – filling in form fields when selecting the MA number from the list
...
Fig. 11 – filling out the Party of the master agreement fields when choosing from the list of MA numbers
...
If the MA identifier was entered manually (see Fig. 8,1), fields Party 1 of the master agreement and Party 2 of the master agreement will be filled in from the list of the Choose counterparties pop-up window (Fig. 13), which is opened by clicking on the link [PARTY-1-CODE] Party 1 (Fig. 12). Anchor сторонаГС сторонаГС
Fig. 12 – filling in the Party of the master agreement field
...
Fig. 15 – example of filling the fields using directories Fig. 16 – searching a value in the list
To specify the draft name (only also for modal window form display), activate the name input field by clicking (Fig. 17), enter the order name into the field (Fig. 18) and click button to save the changes. To discard changes, click .
Fig. 17 – button enable the name input field Fig. 18 – order name input field
...
These actions are performed using the toolbar buttons, which are described in Table 2.
Table 2 – Description of the toolbar
...
– saving changes.
After clicking the button the order gets to the Drafts form
...
. If at the creation of a new message the name was not specified, the Save window will open, where you must enter the draft name and confirm saving by clicking on the Save button
...
.
Fig. 19 – saving changes
– checking for format compliance.
After clicking
...
the button, the system will automatically check the order for
...
compliance
...
with NSD formats.
...
Check results will be displayed in
...
the Log
...
tab in the form of a list of system errors.
...
(Fig. 20 and 21 – modal window).
Fig. 20 – Log tab Fig. 21 – modal window
Click on the error takes the user to the Reporting form. The incorrectly filled fields will be highlighted in red. The specific error, on which you have clicked, will be highlighted in yellow (Fig. 22).
Fig. 22 – Reporting form
If the check does not detect any errors,
...
the Log
...
tab will indicate that the order is valid.
...
The validation is also performed automatically when
...
clicking Send. An invalid order cannot be sent to the repository.
...
– sending order to the repository for registration (not available when creating, editing a template, order based on the template).
After clicking on the button a confirmation screen appears, where you need to click OK to place a DS (digital signature) and send the message to the repository (Fig. 23). The Send button is not available when creating, editing orders based on a template
...
.
Fig. 23 – sending order
– adding a file to an order.
Clicking on the button opens a context menu with two file upload options:
After selecting one of the upload options opens the screen form with using which you need to select the necessary file and click . When sending an uploaded document to the repository the file name will be changed automatically in accordance with the rules of NSD electronic document flow.
...
– exit the order creation/editing
...
form.
After clicking the button the confirmation window will appear, where you should click OK to exit form. You will be taken to the
...
form which was opened to create or edit an order (Fig.
...
24).
Fig. 24 – exit the order creation/editing form