Результат MediaWiki API

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "S7_NDC",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "2049": {
                "pageid": 2049,
                "ns": 0,
                "title": "Reallocation of funds",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[\u041a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f:\u041c\u043e\u0434\u0443\u043b\u0438]] [[\u041a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f:\u0414\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u043c\u043e\u0434\u0443\u043b\u0438\u200e]][[\u041a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f:\u0420\u0435\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f B2B]]\n'''Reallocation of funds''' \u2014 is an additional module of the Websky online ticket booking system for B2B agencies.\n\n== Purpose of the module ==\nWhen using a standard scheme of payment from company balance sheet, a single account is allocated to every company, and all expert employees of this subagent and the company manager himself have equal access to it by default.\nBut in this case it is difficult to avoid cases of the account abuse:\neach employee can dispose of virtually the entire available amount of the account / available overdraft. \nThe Reallocation of funds module allows you to set a limit on a certain amount for a specific user of the company (or a group of users) within one account, thus avoiding such situations. Secondly, this module makes it possible to pay orders from the company's balance to ordinary users of the company (not experts), which is not supported in the standard payment scheme from the balance of the companies. <br>\n\n== Module connection ==\nThe module is connected additionally by the Websky system administrator. To connect the module, use the Websky project tracker.\n\n== Principle of operation ==\n\nThe subagent can distribute the amount of  its account set for it by the root agency among its own users so that the users of the subagent can use the ''''payment method from the company's balance.'''' <br>\nThe subagent allocates for its user/user group a part of the account that was previously given to the subagent by the root agency.<br>\nThe part of the account that the subagent manager distributes to its users cannot be used to pay for orders by the subagent (subagent manager/expert).\n\nRules of the ''Reallocation of funds'' module:\n* You can distribute the entire amount that is listed on the balance sheet of the company and the available sub-agency\u2019s overdraft. \n* The amount by the selected accounts of all objects cannot exceed the amount of the company's balance + available overdraft of the sub-agency.\n* The user uses his / her own account for payment, or, if his own account is not assigned to him by a subagent, the account of the first object in the hierarchy upwards to which the account is assigned (for example, the account of the group to which this user belongs). <br>\n* The user can make a payment only within the account related to him. \n''''Attention!'''' If the account is not distributed to the user, but is assigned to the group to which it belongs, the user uses the group\u2019s shared account. <br> In particular, it can be the balance of the subagent itself after deducting the distributed part, if the user is included in the root group of the subagent. \n\n* If no fund reallocation is specified for users or groups of a subagent, then payment from the company's balance will be available ''''only to the manager / expert of the subagency''''.\n* If at least one reallocation entry is specified for users or subagent groups in the table, payment from the company's balance is allowed for those users for whom reallocation is set and this payment method is activated in the section '''Finances \u2192 Payment Methods \u2192 Gateway access settings'''.  The amount available to the user is set during the reallocation. \n\n''''Attention!'''' When using the Funds  Reallocation module, the subagent needs to keep track of those users / groups of users whom it allows to pay for orders from the company's balance sheet. <br> To enable and disable access to payments from the company's balance sheet for a user / group of users, under Finances \u2192 Payment Methods \u2192  Gateway access settings, adjust the availability of payment methods for different groups and users of the subagent (see Payment Methods in {{Name.system}} for more details). \n\n{| class=\"wikitable\" align=\"center\"\n|-\n|[[\u0424\u0430\u0439\u043b:reallocation_of_funds.jpg|800px|center|Agent reallocation scheme]]\n|}\n===Billing strategy===\nWhen using the '''Reallocation of funds''' module, the '''deduct own fee of the subagent''' option (for managers and experts) (the ''Billing strategy for subagents'' parameter for subagents in Product control \u2192  Aviatickets \u2192 Pricing \u2192 Settings) is always enabled regardless of the option settings. Thus, with the inclusion of the '''Reallocation of funds''' module, the withdrawal of funds from the general account of the subagent is always minus the subagent\u2019s own charge. \n\nThe movement of funds in the accounts is carried out according to the following principle:\n* When the ''user of the subagent'' pays for the order: \n** ''payment amount'' is displayed in full on the user\u2019s order page,\n** when paying with the ''user's'' company balance, the entire amount of the order, including fees and charges of the subagent, is withdrawn, and the subagent\u2019s own fee is returned to the account of the subagent,\n** the amount of the order along with the commission, is deducted from the total account of the subagent ''minus the own charge of the subagent''. <br> In the ''History of account transactions'' (see Company Balance article) two transactions will be displayed - debiting the full amount from the user's balance account, crediting the fee to the subagent's account.\n* When paying for the order by the ''manager or expert of the subagent'':\n** when displaying the order amount on the order page:\n*** if the ''deduct subagent\u2019s own charge'' option and/or ''deduct subagent\u2019s commission'' is active, then on the order page for the manager and expert the amount less the own charge and/or commission of the subagent is displayed.\n*** if the ''deduct subagent\u2019s own charge'' option and/or ''deduct subagents\u2019 commission'' is not enabled, the full amount is displayed on the order page for the manager and expert.\n** When paying with the ''subagent\u2019s'' company balance, the order amount is withdrawn ''minus commissions and charges of the subagent''. \n\n===Loan payment and refund for orders payed by the distributed account===\n\nWhen you pay for a loan or make a refund, the amount is returned to the account from which the payment was made. If this account has already been deleted, the amount will be returned to the account of the first in the hierarchy above the object in which it is installed.\n\n== Subagency funds reallocation ==\nAfter connecting the module in the administration panel, a section on Reallocation of funds appears, located at Finances \u2192 Balances and overdrafts \u2192 Reallocation of funds. The section is accessible only to the ''root agency manager'' and the ''subagency manager''. \n\nSelect the settings application object in the '''User''' field. Depending on the selected user, the page displays either the fund distribution table of the selected subagent or a form for allocating funds to the selected user. \n\n===Overview of redistributed funds by users of subagency===\nIf a '''subagency''' is selected as a user, the page displays: \n* '''Information on the current state of the sub-agency balance''':\n** subagency balance.\n** subagency overdraft.\n** allowable amount to be distributed - The amount available for distribution is calculated in the following way:<code> \"Company balance sheet amount\" + \"Available overdraft\" - \"amount already distributed to users of the subagent\" </code>.\n* '''A table with all the established balance amounts of the selected subagent and the balance on the subagent balance'''. \n\nThe table contains the following columns:\n* '''User''' \u2014 list of users / user groups of the subagent for which the account has been allocated. The last user on the list is the subagentry itself. \n* '''Sum''' \u2014 balance of the company allocated to the user or group.  \n* '''Edit''' \u2014 link to the user account editing page. When you click the link, the user is transfered to the form to edit the account value of this user.\n* '''Delete''' \u2014 button which allows you to delete a user account record. When deleting, user funds are returned to the sub-agency account. \n\nTo sort the entries in the table in ascending / descending order, click on the column header of the table.<br>\nEditing/deleting a sub-agency\u2019s own account is unacceptable because it is set by the root agency manager in the '''Balance account settings''' section, see \u201cCompany Balance\u201d article. \n\n{| class=\"wikitable\"\n|-\n|[[\u0424\u0430\u0439\u043b:\u0422\u0430\u0431\u043b\u0438\u0446\u0430 \u043f\u0435\u0440\u0435\u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f \u0441\u0440\u0435\u0434\u0441\u0442\u0432 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0441\u0442\u0432\u0430.jpg|1200px|\u0420\u0438\u0441. 1 \u0422\u0430\u0431\u043b\u0438\u0446\u0430 \u0441\u043e \u0432\u0441\u0435\u043c\u0438 \u0432\u044b\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u043c\u0438 \u0434\u0435\u043f\u043e\u0437\u0438\u0442\u0430\u043c\u0438 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0441\u0442\u0432\u0430]]\n|-\n|Table of reallocation of funds to users of the sub-agency: \"\u041f\u0435\u0440\u0435\u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u0435 \u0441\u0440\u0435\u0434\u0441\u0442\u0432\" - Reallocation of funds\n\"\u0411\u0430\u043b\u0430\u043d\u0441 \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0441\u0442\u0432\u0430\" - subagency balance\n\"\u041e\u0432\u0435\u0440\u0434\u0440\u0430\u0444\u0442 \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0441\u0442\u0432\u0430\" - subagency overdraft\n\"\u0413\u0440\u0443\u043f\u043f\u0430 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0430\" - subagent users group. \"\u041f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0430\" - subagent user. \"\u0421\u0443\u0431\u0430\u0433\u0435\u043d\u0442\" - subagent. \n|}\n\n===Editing the account of a subagency user===\n\nTo set an account for a user or group:\n# Go to the section '''Editing the user balance of the sub-agency'''. You can enter the user/group user balance editing page in two ways:\n#* Select the object to apply the settings in the'''User''' as ''user/ user group''.\n#* If the account for a user / user group has been set up earlier, you can proceed to editing the user's funds from the funds reallocation table (see the previous section). \n# Set the size of the account provided to the selected user \u2014 the value that will be allocated from the subagent\u2019s own funds to this user or group. <br> When you specify the value of the account, the amount allowable for distribution decreases. \n#* If an amount excceding subagent\u2019s own funds is entered, the current value of this user's account will remain unchanged, and the page will display the following message: ''The account size has not been changed, because the amount exceeds the maximum value''. <br>\n\nThe currency of the account is determined by the currency of the subagency\u2019s account, i.e. if the account of the subagency is set in RUB, then the currency of the user/group account is also RUB. <br>\nOnly positive numbers are allowed as account size, with the fractional part separated by a dot or a comma. <br>\n\n{| class=\"wikitable\"\n|-\n|[[\u0424\u0430\u0439\u043b:\u0424\u043e\u0440\u043c\u0430 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0431\u0430\u043b\u0430\u043d\u0441\u043e\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f.jpg|700px|\u0420\u0438\u0441. 2 \u0424\u043e\u0440\u043c\u0430 \u0441\u043f\u043b\u0438\u0442\u0430]]\n|-\n|User balance management form: \u0414\u043e\u0441\u0442\u0443\u043f\u043d\u043e \u0434\u043b\u044f \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f - Available for reallocation. \u0423\u043a\u0430\u0436\u0438\u0442\u0435 \u0431\u0430\u043b\u0430\u043d\u0441, \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0432\u044b\u0431\u0440\u0430\u043d\u043d\u043e\u043c\u0443 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044e - set the balance for the selected user.\n|}\n\nIt is also possible to set for the user an account that exceeds the real balance of the subagency company via the setting '''the amount of distributed accounts can exceed the amount of the subagency\u2019s balance'''. In this case, the user will be able to pay for the flight only if the sub-agency\u2019s account has enough money to pay for the flight. Otherwise, the user will be prompted to contact the agency. To enable this setting:\n* Go to '''Finances \u2192 Balances and overdrafts \u2192 Balance account settings''' \n* Turn on the '''Amount of distributed accounts setting may exceed the amount of the sub-agency balance''' and save the changes.\n\n==Paying from the company balance==\n\nIn order for a subagency user or group of users to have access to a payment method from the company's balance, the '''company balance''' payment method must be enabled for these objects under '''Finances \u2192 Payment Methods \u2192 Access to Payment Methods'''. Also make sure that the payment gateway is set up for these users in the '''Finances \u2192 Payment Methods \u2192 Gateway control''' section and that the '''Payment gateway enabled''' option is active in the filter settings of this payment method (for more details, see the article Payment Methods in Websky). \n\nAfter choosing the '''company balance''' payment method after booking, when you switch to payment, on the order page, the user will see the status of the company's available balance: \n* \u00abCompany Balance\u00bb,\n* \u00abAvailable overdraft\u00bb,\n* \u00abWill remain after payment\u00bb,\n* \u00abAmount to pay\u00bb.\n\nTo pay for an order with funds from the company balance: \n* The user clicks the '''Pay''' button.\n* A message will appear in a pop-up window: \"Attention, funds will be written off from your company's balance sheet. Continue?\". To pay from the balance of the company, the user must agree.\n* The funds are debited from the balance of the company that is assigned to the user. The order status is ''Paid''.\n\n==See also==\n* [[\u0411\u0430\u043b\u0430\u043d\u0441 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0439|Company Balance (rus)]]\n* [[\u041f\u043b\u0430\u0442\u0435\u0436\u043d\u044b\u0435 \u043c\u0435\u0442\u043e\u0434\u044b \u0432 Nemo.travel|Payment methods in Websky (rus)]]\n* [[\u0420\u0430\u0441\u0448\u0438\u0440\u0435\u043d\u043d\u044b\u0439 \u043c\u043e\u0434\u0443\u043b\u044c \u0441\u0443\u0431\u0430\u0433\u0435\u043d\u0442\u0441\u043a\u0438\u0445 \u043f\u0440\u043e\u0434\u0430\u0436|Advanced subagent sales module (rus)]]"
                    }
                ]
            },
            "2144": {
                "pageid": 2144,
                "ns": 0,
                "title": "Registration",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[\u041a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u044f:\u0422\u0435\u0440\u043c\u0438\u043d\u044b]]\n<!-- -->\n'''Registration''' is the generation of login and password for further use during user authorization in the system or on the site. Registration of individuals/legal entities from the main page of the website (\"Registration\" link ) and auto registration of individuals during booking are available in Websky system.\n== Setting up the registration process ==\n[[File:settings_registration.png|700px|thumb|right|Adjusting the registration process]].\nYou can set up the registration process by going to menu item \"Account management\" \u2192 \"Registration process\". You must specify the following settings:\n* {{Setting| Close site for unauthorized users}} - closes access to the site for unauthorized users, only registration, authorization and CMS content pages are available.\n* {{Setting| User registration is allowed}} - setting enabled by default.  If it is disabled, registration on the site will not be available to everyone.\n* {{Setting| Register type}} - this setting specifies the acceptable type of account created during registration.  Options:\n** {{Setting| All}} - when registering, you will be able to choose the registration form both for an individual and a legal entity.\n** {{Setting| Only individuals}} - corresponds to the \"User\" account type.\n** {{Setting| Only legal entities}} - corresponds to the \"Company\" account type (for subagents).\n* {{Setting| Allow registration for anonyms}} - if this option is enabled, anonym will be asked to create an account when filling in the customer information, e-mail will be used as a login (a \"Greeting of a new user\" will be sent to the specified e-mail).\n* {{Setting| Anonyms registration is mandatory}} - if this option is enabled, the registration will be automatic (by entered e-mail if the password is generated randomly and by entered e-mail and password, if the password is manually entered by the user), the user will have no choice whether to create an account or not.\n* {{Setting| Generate a random password when authoregistering}} - if this option is enabled, the user will receive an e-mail with a randomly generated password.\n* {{Setting| Enable e-mail validation check of new user by sending confirmation link}} - if this option is enabled, an email with a link (a \"Registration\" email) will be sent to the user's email address specified during the registration process.  If the setting is disabled, after registration, the user gets to the site under his login immediately, without confirmation (in this case, the \"Greetings of a new user\" letter will be sent to the mail).\n* {{Setting|Validity of a link for confirmation (in hours)}} - configurable timeout to confirm registration. If this field is not filled in, it is 24 hours by default. If the confirmation did not happen during this period, then the old unconfirmed registration record will be deleted after trying to register again with the same e-mail.\n* {{Setting| Registration benefits and opportunities}} - this information is displayed in the pop-up window, which opens when the user clicks on the link \"Why register?\", the link is located in the customer data block.\n* {{Setting| Popup registration}} - registration of individuals and legal entities is carried out in the pop-up window.\n\n\n'''Attention!''' While using Booking Form 2.0, the following settings become irrelevant: \n# The auto-registration password is generated regardless of the setting {{Setting| Generate random password during auto-registration}}.\n# The setting {{{Setting|\u041f\u0440\u0438\u043d\u0443\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e to register as anonymous when creating an order}} does not register anonymous users when creating an order. \n\n== Registration Form Settings ==\n\nYou can customize the type of registration form on the \"For technical support\" page \u2192 \"Outdated settings\" \u2192 \"Form settings\" \u2192 \"Registration form\". This setting allows you to configure the fields to be displayed on the registration form. By default, mandatory fields are: e-mail (login), password for individuals and e-mail address, password for legal entities. Other fields can be displayed (either as mandatory or optional) or hidden. \nSetting {{Setting| Enter the code from the image}} helps avoid bots registering in the system.  When filling in, the user will be asked to enter the code from the letters and numbers shown in the image. \n\n[[File:Code.png]].\n\n== Registration form of a individual / legal entity ==\n[[File:registr_physic.png|500px]].\n\n[[File:registr_legal.png|500px]]\n\n== Setting up registration message templates ==\nDepending on the setting {{Setting| Enable verification of a new user's email address by sending a confirmation link to the email address}}, the user may receive two types of email informing them of their registration.  You can customize the type of these emails in the \"System Settings\" \u2192 \"Notifications\" \u2192 \"Email Templates\" menu.\n\n* '''Registration Template''' - this template is applied if the above setting is active. To fill this template we offer a number of variables, among which there are <syntaxhighlight lang=\"text\" enclose=\"none\" style=\"font-size: 1.2em; padding: 0 3px; background: #F0F0F0F0; border: 1px dashed #2F6FAB;\">%CONFIRM_LINK%</syntaxhighlight> - the link, which should be used by a new user to confirm the order. \n\n* '''New User's Welcome Template''' - applied if the above setting is inactive, and always at auto-registration. As in the first case, in this template you can use the same variables (agency name, client name, login, password), except for the confirmation link.\n\n\n== See also ==\n* [[\u041e\u0442\u043a\u0440\u044b\u0442\u0438\u0435 \u0441\u0442\u0440\u0430\u043d\u0438\u0446 \u0432 \u043c\u043e\u0434\u0430\u043b\u044c\u043d\u043e\u043c \u043e\u043a\u043d\u0435|Output of registration form in a modal window]]\n* [[Email Templates]]\n* [[User]]\n* [[Anonymous user]]\n* [[Orders]]"
                    }
                ]
            }
        }
    }
}