Arbitrary pages and links in menus

Материал из WiKi - UserSide

en | ru

In the left main menu of the system you can add your own links or pages to the necessary internal resources or documents of the company.

[[Файл:|thumb|800px|center]]
Customisation is performed in the section "Settings - Main - Various - Customising custom links and pages in the UserSide menu"

[[Файл:|thumb|800px|center]]

When setting up your own links and pages in the UserSide menu, you should fill in the following fields:

  • In the "Section" field you should select in which category the (link/page) will be displayed;
  • In the "Name" field specify the name of the created (link/page);
  • In the "Link" field specify the necessary URL. If the "Open page in frame" checkbox is selected, the page will be opened in the current tab.
  • In the "Available from operators" section it is possible to select profiles for which the data (links/pages) will be available.

[[Файл:|thumb|800px|center]]

You can use such parameters in URL links

Version 3.17dev1+:

[employee_id] - will be replaced by employee ID
[employee_hash] - will be replaced by the hash ID of the employee which is encoded by the algorithm:
$hash = md5(md5($apiKey) . $employee_id . $apiKey);
[employee_hash_date] - will be replaced with the hash ID of the employee which is encoded by the algorithm:
$hashDate = md5(date('Ymd') . md5($apiKey) . $employee_id . $apiKey);

(the first API key from the $apiKeyArray array serves as $apiKey)

For example:
http://site.com/index.php?userside_employee_id=[employee_id]&userside_employee_hash=[employee_hash]

Version 3.16dev5+:

[employee_id] - will be replaced by the employee ID
[employee_hash] - will be replaced by the hash ID of the employee which is encoded by the algorithm:
$hash = md5(md5($zapikey) . $employee_id. $zapikey);
[employee_hash_date] - will be replaced by the hash ID of the employee which is encoded by the algorithm:
$hashDate = md5(date('Ymd') . md5($zapikey) . $employee_id. $zapikey);

For example:
http://site.com/index.php?userside_employee_id=[employee_id]&userside_employee_hash=[employee_hash]

Version 3.16dev2 - Version 3.16dev4:

[employee_id] - will be replaced by the employee ID
[employee_hash] - will be replaced by the hash ID of the employee which is encoded by the algorithm:
$hash = md5(md5($zapikey) . $employee_id. $zapikey);

For example:
http://site.com/index.php?userside_employee_id=[employee_id]&userside_employee_hash=[employee_hash]

Prior to version 3.16dev2:

[operator_id] - will be replaced by the operator ID 
[operator_hash] - will be replaced by the hash ID of the operator that is encoded by the algorithm:
$hash = md5(md5($zapikey) . $operatorId . $zapikey);

For example:
http://site.com/index.php?userside_operator_id=[operator_id]&userside_operator_hash=[operator_hash]

This way you can clearly understand on the side of your script which operator has accessed it and whether it is authorised in userside.