@veeroute/lss-studio-angular 7.35.3290 → 7.37.3331

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
- # @veeroute/lss-studio-angular@7.35.3290
1
+ # @veeroute/lss-studio-angular@7.37.3331
2
2
 
3
- Veeroute Studio API. # Description Server part of the Veeroute Studio. ## Reserved attributes These attribute keys are reserved for specific business logic: | Attribute key | Parent entity | Purpose | |:---------------------|:--------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `ICON_NAME` | location | The attribute value is written to the `web_location_geopoint.icon_name` field | | `FORCED_GEOPROVIDER` | geo_settings | The attribute value determines the geodata provider for rendering flights on the map, which will be used instead of the one specified in the `plan_settings.geo_settings.geo_provider` field | ## Entity relationship diagram ![erd](../uml/studio.svg)
3
+ Programming interface for the Veeroute Studio tool. # Description The server side of Veeroute Studio. ## Reserved attributes These attribute keys are reserved for specific business logic: | Attribute key | Parent entity | Purpose | | ---------------------| ----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `ICON_NAME` | location | The attribute value is written into the `web_location_geopoint.icon_name` field | | `FORCED_GEOPROVIDER` | geo_settings | The attribute value defines the geo data provider used for drawing trips on the map; it will be used instead of the value specified in `plan_settings.geo_settings.geo_provider` | | `TRIP_VERIFIED` | trip | The attribute value indicates whether the trip has been verified and approved manually | Usage example — overriding the geo provider for drawing trips in Studio: { \"plan_settings\": { \"geo_settings\": { \"attributes\": [ { \"key\": \"FORCED_GEOPROVIDER\", \"value\": \"OSRM_EXTERNAL\" } ] } } } ## Additional attributes Rules for processing additional attributes when using Universal Extension: * If the entity key does not exist — such an additional attribute is ignored * If the attribute key for the entity already exists — the attribute value will be overwritten after the calculation finishes ## Roles Restrictions on working with a virtual folder: * After creation, a folder cannot change its owner or company. * When a new folder is created not in ROOT, it inherits the owner and the company from the parent folder. Effect of the account role on the virtual file system: ### ADMIN, PARTNER, USER, BOT * Access only to one\'s own folders (`folder.owner_username = account.username`) and to files inside those folders * Ability to open any other user\'s files for editing via a direct file link ### COMPANYOWNER * Access only to folders of one\'s own company (`folder.owner_company_key = account.company_key`) and to files inside those folders * Ability to open any other user\'s files for editing via a direct file link ### OVERLORD * Access to all folders in the environment (`folder.owner_company_key = *`) and to files inside those folders ## Entity diagram ![erd](../uml/studio.svg)
4
4
 
5
- The version of the OpenAPI document: 7.35.3290
5
+ The version of the OpenAPI document: 7.37.3331
6
6
 
7
7
  ## Building
8
8
 
@@ -24,7 +24,7 @@ Navigate to the folder of your consuming project and run one of next commands.
24
24
  _published:_
25
25
 
26
26
  ```console
27
- npm install @veeroute/lss-studio-angular@7.35.3290 --save
27
+ npm install @veeroute/lss-studio-angular@7.37.3331 --save
28
28
  ```
29
29
 
30
30
  _without publishing (not recommended):_
@@ -4,8 +4,8 @@ x-description-ru: >
4
4
  Тип ошибки:
5
5
  * `INCONSISTENT_REFERENCE` - ссылка на несуществующую сущность
6
6
  * `UNIQUE_IDS_VIOLATION` - все идентификаторы должны быть уникальными
7
- * `INVALID_ROUTING_MATRIX` - проблема с размерностью матрицы гео-данных
8
- * `INVALID_GEO_PROVIDER` - проблема с указанным гео-провайдером
7
+ * `INVALID_ROUTING_MATRIX` - проблема с размерностью матрицы геоданных
8
+ * `INVALID_GEO_PROVIDER` - проблема с указанным геопровайдером
9
9
  * `INVALID_TIME_WINDOW` - проблема с указанным временным окном
10
10
  * `COMPATIBILITY_CARGO_BOX` - ни один груз не совместим ни с одним отсеком
11
11
  * `COMPATIBILITY_TRANSPORT_PERFORMER` - ни один транспорт не совместим ни с одним исполнителем
@@ -22,28 +22,6 @@ x-description-ru: >
22
22
  * `PERFORMER_WRR_MEANINGLESS_BREAK` - заданный перерыв невозможно начать
23
23
  * `TOO_MANY_WARNINGS` - количество предупреждений `warning` больше 15001
24
24
  * `UNCLASSIFIED_ERROR` - неклассифицированная ошибка
25
- x-description-zh: >
26
- 错误类型:
27
- * `INCONSISTENT_REFERENCE` - 错误的参考键
28
- * `UNIQUE_IDS_VIOLATION` - 所有键必须是唯一的
29
- * `INVALID_ROUTING_MATRIX` - 错误的路由矩阵维度
30
- * `INVALID_GEO_PROVIDER` - 错误的地理提供商
31
- * `INVALID_TIME_WINDOW` - 指定的时间窗口存在问题
32
- * `COMPATIBILITY_CARGO_BOX` - 没有货物与任何盒子兼容
33
- * `COMPATIBILITY_TRANSPORT_PERFORMER` - 没有传输与任何表演者兼容
34
- * `COMPATIBILITY_TRANSPORT_LOCATION` - 没有任何交通工具与任何位置兼容
35
- * `COMPATIBILITY_ORDER_PERFORMER` - 没有订单与任何表演者兼容
36
- * `INCONSISTENT_HARDLINK` - 本质密钥必须仅存在于一个硬链接中
37
- * `PLANNING_HORIZON_EXCEEDED` - 超出规划范围(数据集中最早和最新时间​​戳之间的差异)
38
- * `MEANINGLESS_RESTRICTIONS` - 指定的限制没有意义
39
- * `LOCATION_LIMITS_VIOLATION` - 限制的时间窗口不得重叠,并且它们的联合必须与位置可用性窗口 `work_window` 相对应; 如果设置了 `min_cargos`/`min_transports` 约束则必须设置 `max_cargos`/`max_transports` 约束; `min_cargos`/`min_transports` 约束必须小于所有 `max_cargos`/`max_transports` 约束
40
- * `PERFORMER_WRR_MUST_BE_SET` - 工作和休息计划中,`rest_rules` 或 `break_rules` 字段至少必须设置一个
41
- * `PERFORMER_WRR_INVALID_REST_COUNT` - 休息次数不能超过 14 次
42
- * `PERFORMER_WRR_INVALID_BREAK_COUNT` - 休息次数不能超过 14 次
43
- * `PERFORMER_WRR_MEANINGLESS_REST` - 指定的休息时间不能插入
44
- * `PERFORMER_WRR_MEANINGLESS_BREAK` - 指定的休息时间不能插入
45
- * `TOO_MANY_WARNINGS` - 警告数量大于 15001
46
- * `UNCLASSIFIED_ERROR` - 未分类错误
47
25
  description: >
48
26
  Error type:
49
27
  * `INCONSISTENT_REFERENCE` - bad reference key
@@ -44,50 +44,6 @@ x-description-ru: >
44
44
  * `REMOVED_ITEMS_NOT_EMPTY` - в процессе проверки данных были удалены сущности из исходного датасета, список удаленных сущностей находится в объекте `removed_items`
45
45
  * `INCOMPATIBLE_REQUIREMENTS` - заданы несовместимые требования: учет нагрузки на локацию и оптимизация мягких окон.
46
46
  * `UNCLASSIFIED_WARNING` - неклассифицированное предупреждение
47
- x-description-zh: >
48
- 警告类型:
49
- * `NO_AVAILABLE_TRANSPORT` - 订单无法完成,因为没有可用的(按班次限制)运输方式
50
- * `NO_AVAILABLE_PERFORMER` - 订单无法完成,因为没有可用的(按班次限制)执行者
51
- * `NO_COMPATIBLE_TRANSPORT` - 订单无法完成,因为没有兼容的(就容量和/或兼容性标签而言)运输方式
52
- * `NO_COMPATIBLE_PERFORMER` - 订单无法完成,因为没有兼容的(按兼容性标签)执行者
53
- * `NO_AVAILABLE_ORDER_FOR_TRANSPORT` - 传输无用,因为没有兼容的(按容量和/或兼容性标签)顺序
54
- * `NO_AVAILABLE_ORDER_FOR_PERFORMER` - 表演者无用,因为没有兼容的(按容量和/或兼容性标签)顺序
55
- * `NO_COMPATIBLE_ORDER_FOR_TRANSPORT` - 运输无用,因为没有可用的订单(根据轮班限制)
56
- * `NO_COMPATIBLE_ORDER_FOR_PERFORMER` - 执行者无用,因为没有可用的订单(根据轮班限制)
57
- * `PICKUP_AND_DROP_VIOLATION` - 订单中的每件货物必须有且只有一次装载和一次卸载(`PICKUP_TO_BOX` 和 `DROP_FROM_BOX` 订单除外)
58
- * `PICKUP_AND_DROP_VIOLATION_PRECEDENCE_IN_ORDER` - 订单中的每件货物,装载必须在之前进行卸载(`precedence_in_order`)
59
- * `PICKUP_AND_DROP_VIOLATION_PRECEDENCE_IN_TRIP` - 指定了相冲突的订单优先顺序要求(`precedence_in_trip`)
60
- * `VIOLATION_PRECEDENCE_IN_TRIP_AND_ORDER` - 行程中的订单优先顺序要求(`precedence_in_trip`)和订单中的订单优先顺序要求(`precedence_in_order`)相互矛盾
61
- * `TIME_WINDOW_VIOLATION` - 时间窗口的开始时间晚于窗口的结束时间或时间窗口超出允许的最大值
62
- * `DURATION_VIOLATION` - 持续时间与允许的间隔不符
63
- * `ORDER_WINDOWS_INTERSECTION_VIOLATION` - 软窗口不应超出硬窗口的边界
64
- * `PERFORMER_SHIFTS_INTERSECTION_VIOLATION` - 表演者工作班次的时间范围必须不重叠,下一个窗口的开始不能等于前一个窗口的结束
65
- * `TRANSPORT_SHIFTS_INTERSECTION_VIOLATION` - 运输工作班次的时间范围不应重叠,下一个窗口的开始不能等于前一个窗口的结束
66
- * `LOCATION_WINDOWS_INTERSECTION_VIOLATION` - 一个位置的工作窗口的时间范围不应相交,下一个窗口的开始不能等于前一个窗口的结束
67
- * `NO_TRANSPORT_BOXES` - 如果有货物订单,则运输必须至少有一个箱子
68
- * `MAX_CAPACITY_VIOLATION` - `max_capacity` 限制超过所有箱子的总容量或仅为一个箱子设置或小于某些箱子的容量
69
- * `MAX_BOXES_VIOLATION` - 限制 `max_boxes`大于或等于箱子总数或为一个箱子指定或等于零
70
- *`TOO_MANY_CARGOS_FOR_DROP_VIOLATION` - `DROP` / `DROP_FROM_BOX` 类型的订单的装载数量不得超过一个
71
- *`EMPTY_CARGOES_LIST` - `DROP` / `DROP_FROM_BOX` / `PICKUP` / `PICKUP_TO_BOX` 类型的订单的装载列表为空
72
- *`CARGO_WORK_VIOLATION` - 对于 `WORK` 订单,货物清单必须为空
73
- *`GEODATA_TIME_WINDOW_VIOLATION` - 计划范围超出最大可用值
74
- *`SHIFT_RESTRICTIONS_COULD_BE_MORE_PRECISE` - 艺术家变更的工作窗口 `working_window` 不完全位于可用性窗口 `availability_window` 内
75
- * `DURATION_DOES_NOT_FIT_INTO_HARD_WINDOW` - 事件的持续时间不符合硬时间窗口
76
- * `DURATION_DOES_NOT_FIT_INTO_SOFT_WINDOW` - 事件的持续时间不符合软时间窗口
77
- * `EXTRA_DURATION_DOES_NOT_FIT_INTO_SOFT_WINDOW` - 需求执行的额外时间不符合软时间窗口
78
- * `MAX_CALCULATION_TIME_VIOLATION` - 已超出允许的最大计算时间
79
- * `MAX_WAITING_TIME_VIOLATION` - 已超出允许的最大等待时间
80
- * `INVALID_HARDLINK` - 无法分配具有 `WORK` 类型需求的订单进行运输
81
- * `CARGO_BOX_VIOLATION` - 对于除 `DROP_FROM_BOX` 之外的所有类型的请求,货物所在箱子的键必须为空
82
- * `CARGO_MULTIBOX_VIOLATION` - 对于类型为 `DROP_FROM_BOX` 的订单,指示的货物位于不同车辆的箱子中
83
- * `CARGO_CAPACITY_VIOLATION` - 机上指定的货物超出了其所在箱子的大小
84
- * `CARGO_ORDER_VIOLATION` - 订单中指定的货物不在订单中
85
- * `FEATURE_LIFETIME_VIOLATION` - 特征时间窗口相互相交或用于更改执行者或运输的工作窗口 `working_window` 与特征时间窗口不相交
86
- * `QUOTA_EXCEEDED` - 超出服务配额
87
- * `MAX_LOCATIONS_LIMITS_PENALTY_EXCEEDED` - 生成的解决方案不满足 `max_locations_limits_penalty` 要求
88
- * `REMOVED_ITEMS_NOT_EMPTY` - 在数据验证过程中,实体被从源数据集中删除,删除的实体列表位于 `removed_items' 对象中
89
- * `INCOMPATIBLE_REQUIREMENTS` - 指定了不兼容的要求:位置负载核算和软窗口优化
90
- * `UNCLASSIFIED_WARNING` - 未分类警告
91
47
  description: >
92
48
  Warning type:
93
49
  * `NO_AVAILABLE_TRANSPORT` - the order cannot be fulfilled, since there is no available (by shift limitations) transport
@@ -115,7 +71,7 @@ description: >
115
71
  * `EMPTY_CARGOES_LIST` - empty list of loads for orders of type `DROP` / `DROP_FROM_BOX` / `PICKUP` / `PICKUP_TO_BOX`
116
72
  * `CARGO_WORK_VIOLATION` - for a `WORK` order, the cargo list must be empty
117
73
  * `GEODATA_TIME_WINDOW_VIOLATION` - the planning horizon exceeds the maximum available value
118
- * `SHIFT_RESTRICTIONS_COULD_BE_MORE_PRECISE` - the working window `working_window` of the change of the artist does not lie entirely inside the window of availability `availability_window`
74
+ * `SHIFT_RESTRICTIONS_COULD_BE_MORE_PRECISE` - the `working_window` of the performer's shift does not lie entirely inside the availability window `availability_window`
119
75
  * `DURATION_DOES_NOT_FIT_INTO_HARD_WINDOW` - the duration of the event does not fit into the hard time window
120
76
  * `DURATION_DOES_NOT_FIT_INTO_SOFT_WINDOW` - the duration of the event does not fit into the soft time window
121
77
  * `EXTRA_DURATION_DOES_NOT_FIT_INTO_SOFT_WINDOW` - additional time for demand execution does not fit into the soft time window
@@ -123,10 +79,10 @@ description: >
123
79
  * `MAX_WAITING_TIME_VIOLATION` - the maximum allowable waiting time in queue has been exceeded
124
80
  * `INVALID_HARDLINK` - it is impossible to assign an order with demands with the `WORK` type to transport
125
81
  * `CARGO_BOX_VIOLATION` - for requests of all types except `DROP_FROM_BOX` the key of the box where the cargo is located must be empty
126
- * `CARGO_MULTIBOX_VIOLATION` - for an order of type `DROP_FROM_BOX` the indicated cargoes are in boxes of different vehicles
82
+ * `CARGO_MULTIBOX_VIOLATION` - for a demand of type `DROP_FROM_BOX` the indicated cargos are in boxes of different transports
127
83
  * `CARGO_CAPACITY_VIOLATION` - the specified cargo on board exceeds the size of the box in which it is located
128
84
  * `CARGO_ORDER_VIOLATION` - the cargo specified in the order is not present in orders
129
- * `FEATURE_LIFETIME_VIOLATION` - feature time windows intersect with each other or the working window `working_window` for changing the performer or transport does not intersect with the feature time window
85
+ * `FEATURE_LIFETIME_VIOLATION` - feature time windows intersect with each other, or the `working_window` of the performer's or transport's shift does not intersect with the feature time window
130
86
  * `QUOTA_EXCEEDED` - service quota exceeded
131
87
  * `MAX_LOCATIONS_LIMITS_PENALTY_EXCEEDED` - the resulting solution does not satisfy the `max_locations_limits_penalty` requirement
132
88
  * `REMOVED_ITEMS_NOT_EMPTY` - during data validation, items were removed from the original dataset, the list of removed items is in the `removed_items` object
@@ -66,6 +66,18 @@
66
66
  "operation_id": "delete_files_batch",
67
67
  "type": "TRACE"
68
68
  },
69
+ {
70
+ "method": "PUT",
71
+ "uri": "/studio/explorer/batch/sharing",
72
+ "operation_id": "enable_sharing_batch",
73
+ "type": "TRACE"
74
+ },
75
+ {
76
+ "method": "DELETE",
77
+ "uri": "/studio/explorer/batch/sharing",
78
+ "operation_id": "disable_sharing_batch",
79
+ "type": "TRACE"
80
+ },
69
81
  {
70
82
  "method": "GET",
71
83
  "uri": "/studio/explorer/batch/counters",
@@ -3756,6 +3756,26 @@
3756
3756
  "field": "TRIP_NAME",
3757
3757
  "type": "STRING_SEARCH"
3758
3758
  },
3759
+ {
3760
+ "disabled": false,
3761
+ "field": "PERFORMER_KEY",
3762
+ "type": "STRING_SEARCH"
3763
+ },
3764
+ {
3765
+ "disabled": true,
3766
+ "field": "PERFORMER_SHIFT_KEY",
3767
+ "type": "STRING_SEARCH"
3768
+ },
3769
+ {
3770
+ "disabled": false,
3771
+ "field": "TRANSPORT_KEY",
3772
+ "type": "STRING_SEARCH"
3773
+ },
3774
+ {
3775
+ "disabled": true,
3776
+ "field": "TRANSPORT_SHIFT_KEY",
3777
+ "type": "STRING_SEARCH"
3778
+ },
3759
3779
  {
3760
3780
  "disabled": false,
3761
3781
  "field": "COST",
@@ -3954,6 +3974,19 @@
3954
3974
  "step": 1.0,
3955
3975
  "type": "FLOAT_RANGE"
3956
3976
  },
3977
+ {
3978
+ "disabled": true,
3979
+ "field": "AVERAGE_ROUNDTRIP_TIME",
3980
+ "type": "DURATION_RANGE"
3981
+ },
3982
+ {
3983
+ "disabled": true,
3984
+ "field": "AVERAGE_ROUNDTRIP_DISTANCE",
3985
+ "max": 1000000000000,
3986
+ "min": 0,
3987
+ "step": 1.0,
3988
+ "type": "FLOAT_RANGE"
3989
+ },
3957
3990
  {
3958
3991
  "disabled": true,
3959
3992
  "field": "ATTRIBUTES",