Actions16
- Сборочные Задания DBS Actions
- Метаданные DBS Actions
Overview
This node interacts with a specific API related to "Метаданные DBS" (DBS Metadata) and performs an update operation named "Put Dbs Orders Meta Imei By Orderid". The main purpose of this operation is to update or set the IMEI (International Mobile Equipment Identity) value for a given order identified by its Order Id. This can be useful in scenarios where you need to associate or correct device identifiers with assembly or production orders in a database or system.
Practical examples include:
- Updating the IMEI number for a manufacturing order after quality control.
- Correcting or adding missing IMEI information to existing orders in a logistics or inventory system.
- Synchronizing device metadata between different systems using order IDs as references.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly or production order to update. |
| Imei | The IMEI number to assign or update for the specified order. |
The Order Id is a required numeric input representing the order to modify. The Imei is a required string input representing the device's IMEI number to be associated with that order.
Output
The node outputs JSON data reflecting the result of the update operation. Typically, this would include confirmation of the update, such as success status, updated fields, or error messages if the operation failed.
No binary data output is indicated or expected from this node.
Dependencies
- Requires access to the WB API (Wildberries API or similar), which must be configured with appropriate credentials (e.g., an API key or token).
- The base URL and API schema are derived from a bundled OpenAPI specification (
04-orders-dbs_modified.json). - The node uses standard HTTP headers for JSON content type and accepts JSON responses.
Troubleshooting
Common issues:
- Invalid or missing Order Id or IMEI values will cause the request to fail.
- Authentication errors if the API key or credentials are not properly configured.
- Network or connectivity issues preventing communication with the API endpoint.
- API schema mismatches if the backend service changes without updating the node's OpenAPI spec.
Error messages:
- Errors related to missing required parameters ("Order Id" or "Imei") should be resolved by providing valid inputs.
- Authorization errors require checking and updating the API authentication credentials.
- HTTP errors like 404 or 500 indicate issues on the server side or incorrect resource paths.
Links and References
- No direct external links provided in the source code.
- For more details on the WB API or DBS metadata operations, consult the official API documentation or the OpenAPI specification file used (
04-orders-dbs_modified.json).