Order Export - История изменений

Илья Шалетин в 09:26, 14 мая 2020

2020-05-14T09:26:22Z

Илья Шалетин: /* Export process */

2020-05-13T14:02:09Z

‎Export process

Илья Шалетин в 14:00, 13 мая 2020

2020-05-13T14:00:53Z

Илья Шалетин: /* Settings */

2020-05-13T13:59:43Z

‎Settings

Илья Шалетин: /* Export process */

2020-05-13T13:58:20Z

‎Export process

Илья Шалетин в 13:51, 13 мая 2020

2020-05-13T13:51:08Z

Илья Шалетин: /* Exporting orders under an authorized user (in a personal account) */

2020-05-13T13:26:43Z

‎Exporting orders under an authorized user (in a personal account)

Илья Шалетин: /* Order export for "Hotels" component */

2020-05-13T13:25:44Z

‎Order export for "Hotels" component

Илья Шалетин: /* Package Export parameters */

2020-05-13T13:25:12Z

‎Package Export parameters

Илья Шалетин: /* See also */

2020-05-13T13:24:17Z

‎See also

@@ Строка 1444: / Строка 1444: @@
 |-
 | CreateDate
-| Date and time of payment transaction creation {{{NameSystem}}.
+| Date and time of payment transaction creation in Websky.
 | String. Example: 2014-06-06 15:10:00.
 |-

@@ Строка 14: / Строка 14: @@
 '''Attention!'''
-* An order in SOFI format will be exported during synchronization only if there are changes in the order.
+* Order in SOFI format will be exported during synchronization only if there are changes in the order.
-*An order in SOFI format will only be exported when cancelled if the order contains cancelled services.
+* Order in SOFI format will be exported during cancellation only if the order contains cancelled services.
 == Settings ==

@@ Строка 3: / Строка 3: @@
 [[Категория:Модули]]
 [[Категория:Встроенные модули]]
 '''Order export''' is export of order data or orders for various components of the Websky system.

@@ Строка 21: / Строка 21: @@
 [[Файл:Выгрузка заказов.jpg|400px|thumb|right|Setting up the order uploading process for airline tickets]]
 Order export settings are available via '''System settings → Integration → Export of bookings'''.
-** '''''Nemo Backoffice''''' — the possibility to export orders in JSON format, which provides more complete and up-to-date data amount, uses international standards of data format, and is an improved version of data export protocol in Websky format.
+* '''Nemo Backoffice''' — the possibility to export orders in JSON format, which provides more complete and up-to-date data amount, uses international standards of data format, and is an improved version of data export protocol in Websky format.
 * '''Address for sending notifications about order changes''' —  if specified, a GET-request is sent to this address when changes are received during the actualization. ('''Example''' ''http://127.0.0.1/?booking_id=ORDER_ID&nemo_id=NEMO_CONNECT_ORDER_ID&locator=LOCATOR''). The value format supports variables '''LOCATOR''', '''ORDER_ID''', '''NEMO_CONNECT_ORDER_ID''' - ('''LOCATOR''' - service identifier in service provider's system, '''ORDER_ID''' - Websky order identifier, '''NEMO_CONNECT_ORDER_ID''' - order identifier in NEMO Connect).
 * '''Url of third party script for XML notifications in Websky format — URL to which the data will be uploaded.

@@ Строка 12: / Строка 12: @@
 The process of order export is schematically presented on the block diagram.
-[[файл:ВыгрузкаСофиИНемо.png]]
+[[файл:Sofi_Nemo_export.png]]
 '''Attention!'''

@@ Строка 21: / Строка 21: @@
 [[Файл:Выгрузка заказов.jpg|400px|thumb|right|Setting up the order uploading process for airline tickets]]
 Order export settings are available via '''System settings → Integration → Export of bookings'''.
-** '''''Nemo Backoffice''''' — the possibility to export orders in JSON format, which provides more complete and up-to-date data amount, uses international standards of data format, and is an improved version of data export protocol in Nemo format.
+** '''''Nemo Backoffice''''' — the possibility to export orders in JSON format, which provides more complete and up-to-date data amount, uses international standards of data format, and is an improved version of data export protocol in Websky format.
 * '''Address for sending notifications about order changes''' —  if specified, a GET-request is sent to this address when changes are received during the actualization. ('''Example''' ''http://127.0.0.1/?booking_id=ORDER_ID&nemo_id=NEMO_CONNECT_ORDER_ID&locator=LOCATOR''). The value format supports variables '''LOCATOR''', '''ORDER_ID''', '''NEMO_CONNECT_ORDER_ID''' - ('''LOCATOR''' - service identifier in service provider's system, '''ORDER_ID''' - Websky order identifier, '''NEMO_CONNECT_ORDER_ID''' - order identifier in NEMO Connect).
 * '''Url of third party script for XML notifications in Websky format — URL to which the data will be uploaded.
@@ Строка 40: / Строка 40: @@
 == Order export formats ==
-The system supports order export in formats '''''Nemo''''', '''''SOFI''''' и '''''JSON'''''. It is recommended to use JSON export functionality.
+The system supports order export in formats '''''Websky''''', '''''SOFI''''' и '''''JSON'''''. It is recommended to use JSON export functionality.
 === Components supporting order export  ===
@@ Строка 190: / Строка 190: @@
 === Order export for the Avia Tickets component ===
-For the '''«Avia Tickets»''' component, orders in Nemo and/or SOFI formats are available for export (when '''«SOFI order export»''' module is enabled).
+For the '''«Avia Tickets»''' component, orders in Websky and/or SOFI formats are available for export (when '''«SOFI order export»''' module is enabled).
 <div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
@@ Строка 1145: / Строка 1145: @@
 === Order export for "Hotels" component  ===
-For the '''«Hotels»''' component, order export is available in Nemo and/or JSON formats.
+For the '''«Hotels»''' component, order export is available in Websky and/or JSON formats.
 <div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
@@ Строка 1155: / Строка 1155: @@
 === Order export for "Rail" component ===
-For '''«Rai»'''  component, order export is available in Nemo and/or JSON formats.
+For '''«Rai»'''  component, order export is available in Websky and/or JSON formats.
 <div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
@@ Строка 1782: / Строка 1782: @@
 </div>
-== Package order export in Nemo format==
+== Package order export in Websky format==
 Order export service allows you to export the necessary samples by orders in XML, XLS(X) format. For example, you can select orders by date of booking and get information on them in the desired format. Export in XLS(X) format will upload a maximum of 1000 orders at a time. If more orders need to be exported (to get complete statistics on all orders), you need to export orders for successive periods.
@@ Строка 1846: / Строка 1846: @@
 If the order export was not successful, the system provides the possibility to export it again. To do this, the manager of the agency needs to go to the page of the problem order in the "Service Information" section, where the link "Re-export order", after clicking on which the order will be re-exported.
-Moreover, if the setting of '''export both Nemo and Sophie''' in the ''System Settings → Integration → Export of bookings'' section is enabled, the order will be re-exported in both Nemo and SOFI formats.
+Moreover, if the setting of '''export both Websky and Sophie''' in the ''System Settings → Integration → Export of bookings'' section is enabled, the order will be re-exported in both Websky and SOFI formats.
 It is also possible to re-export orders from your Personal Account. To do this, in the "Orders" section,  you need to click on the link "Re-export order" for the desired order in the column "Actions".

@@ Строка 1790: / Строка 1790: @@
 === Exporting orders under an authorized user (in a personal account) ===
-[[File:exportxmlxxxlsx.jpg|600px|thumb|right|Filters for package export orders in personal account]].
+[[File:exportxmlxlsxlsx.jpg|600px|thumb|right|Filters for package export orders in personal account]].
 The "Show Export Panel" pseudo link opens a form that allows you to export your orders to an XML, XLS or XLSX file format.

@@ Строка 1148: / Строка 1148: @@
 <div class="toccolours mw-collapsible mw-collapsed" style="width:1000px">
-==== Формат JSON ====
+==== JSON format ====
 <div class="mw-collapsible-content">
 see https://docs.nemo.travel/en/hotels/hotelsbackoffice

@@ Строка 1838: / Строка 1838: @@
 |-
 | passenger second name (for each ticket)
-| no
+| n/a
 | Passengers->Passenger->lastname
 |-
 |}
 === Order re-export ===

@@ Строка 1861: / Строка 1861: @@
 *[[Ticketing]]
 *[[Voiding (Air tickets)|Voiding]]
-*[http://ru.wikipedia.org/wiki/%D0%A1%D0%BF%D0%B8%D1%81%D0%BE%D0%BA_%D0%BA%D0%BE%D0%B4%D0%BE%D0%B2_%D1%81%D0%BE%D1%81%D1%82%D0%BE%D1%8F%D0%BD%D0%B8%D1%8F_HTTP HTTP Status Code List].
+*[https://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP Status Code List].