Actions778
- Acl Role Actions
- App Actions
- App Action Button Actions
- App Administration Snippet Actions
- App Cms Block Actions
- App Flow Action Actions
- App Flow Event Actions
- App Payment Method Actions
- App Script Condition Actions
- App Shipping Method Actions
- App Template Actions
- Category Actions
- Cms Block Actions
- Cms Page Actions
- Cms Section Actions
- Cms Slot Actions
- Country Actions
- Country State Actions
- Currency Actions
- Currency Country Rounding Actions
- Custom Entity Actions
- Custom Field Actions
- Custom Field Set Actions
- Custom Field Set Relation Actions
- Customer Actions
- Customer Address Actions
- Customer Group Actions
- Customer Recovery Actions
- Customer Wishlist Actions
- Customer Wishlist Product Actions
- Delivery Time Actions
- Document Actions
- Document Base Config Actions
- Document Base Config Sales Channel Actions
- Document Type Actions
- Flow Actions
- Flow Sequence Actions
- Flow Template Actions
- Import Export File Actions
- Import Export Log Actions
- Import Export Profile Actions
- Integration Actions
- Landing Page Actions
- Language Actions
- Locale Actions
- Log Entry Actions
- Mail Header Footer Actions
- Mail Template Actions
- Mail Template Type Actions
- Main Category Actions
- Media Actions
- Media Default Folder Actions
- Media Folder Actions
- Media Folder Configuration Actions
- Media Thumbnail Actions
- Media Thumbnail Size Actions
- Newsletter Recipient Actions
- Notification Actions
- Number Range Actions
- Number Range Sales Channel Actions
- Number Range State Actions
- Number Range Type Actions
- Order Actions
- Order Customer Actions
- Order Delivery Actions
- Order Delivery Position Actions
- Order Line Item Actions
- Order Line Item Download Actions
- Order Transaction Actions
- Order Transaction Capture Actions
- Order Transaction Capture Refund Actions
- Order Transaction Capture Refund Position Actions
- Payment Method Actions
- Plugin Actions
- Product Actions
- Product Configurator Setting Actions
- Product Cross Selling Actions
- Product Cross Selling Assigned Products Actions
- Product Download Actions
- Product Export Actions
- Product Feature Set Actions
- Product Keyword Dictionary Actions
- Product Manufacturer Actions
- Product Media Actions
- Product Price Actions
- Product Review Actions
- Product Search Config Actions
- Product Search Config Field Actions
- Product Search Keyword Actions
- Product Sorting Actions
- Product Stream Actions
- Product Stream Filter Actions
- Product Visibility Actions
- Promotion Actions
- Promotion Discount Actions
- Promotion Discount Prices Actions
- Promotion Individual Code Actions
- Promotion Sales Channel Actions
- Promotion Setgroup Actions
- Property Group Actions
- Property Group Option Actions
- Rule Actions
- Rule Condition Actions
- Sales Channel Actions
- Sales Channel Analytics Actions
- Sales Channel Domain Actions
- Sales Channel Type Actions
- Salutation Actions
- Scheduled Task Actions
- State Machine Transition Actions
- System Config Actions
- Tag Actions
- Tax Actions
- Tax Provider Actions
- Tax Rule Actions
- Tax Rule Type Actions
- Theme Actions
- Unit Actions
- User Actions
- User Access Key Actions
- User Config Actions
- User Recovery Actions
- Webhook Actions
- Webhook Event Log Actions
- System Info Health Check Actions
- Bulk Operations Actions
- Document Management Actions
- Asset Management Actions
- Mail Operations Actions
- System Operations Actions
- Customer Impersonation Actions
- Order Management Actions
- Order Address Actions
- Authorization Authentication Actions
Rule Condition → Update Rule Condition
AI-generatedOverview
This node operation updates a Rule Condition in the Shopware system. It is useful for modifying existing rule conditions by specifying their identifier and providing updated details such as type, rule ID, script ID, parent ID, value, position, custom fields, timestamps, and nested rule structures. This operation is beneficial in scenarios where business logic or conditions need to be dynamically adjusted within Shopware workflows or automation rules.
Use Case Examples
- Updating a discount rule condition by changing its type and associated rule ID.
- Modifying a parent rule condition to include new child conditions or update existing ones.
- Adjusting the position or value of a rule condition to change its evaluation order or criteria.
Properties
| Name | Meaning |
|---|---|
| Id | Identifier for the rule_condition, required to specify which rule condition to update. |
| Response | Data format for response, used to specify the response format if needed. |
| Type | Type of the rule condition, required to define the condition type. |
| Rule Id | Identifier of the associated rule, required to link the condition to a specific rule. |
| Script Id | Identifier for the script associated with the condition, optional. |
| Parent Id | Identifier of the parent rule condition, optional for hierarchical conditions. |
| Value | JSON object representing the value or parameters of the rule condition. |
| Position | Numeric position of the rule condition, used to order conditions. |
| Custom Fields | JSON object for any custom fields associated with the rule condition. |
| Created At | Timestamp string indicating when the rule condition was created. |
| Updated At | Timestamp string indicating when the rule condition was last updated. |
| Rule | JSON object representing the nested rule structure associated with the condition. |
| App Script Condition | JSON object representing the app script condition details related to the rule condition. |
| Parent | JSON object representing the parent rule condition structure. |
| Children | JSON array representing child rule conditions nested under this condition. |
Output
JSON
id- Identifier of the updated rule condition.type- Type of the updated rule condition.ruleId- Identifier of the associated rule.scriptId- Identifier of the associated script.parentId- Identifier of the parent rule condition.value- Value or parameters of the rule condition.position- Position of the rule condition.customFields- Custom fields associated with the rule condition.createdAt- Creation timestamp of the rule condition.updatedAt- Last update timestamp of the rule condition.rule- Nested rule structure associated with the condition.appScriptCondition- App script condition details related to the rule condition.parent- Parent rule condition structure.children- Child rule conditions nested under this condition.
Dependencies
- Shopware API with appropriate credentials
Troubleshooting
- Ensure the 'Id' property is provided and correctly identifies an existing rule condition to update.
- Verify that required fields such as 'Type' and 'Rule Id' are included and valid.
- Check JSON formatting for properties like 'Value', 'Custom Fields', 'Rule', 'App Script Condition', 'Parent', and 'Children' to avoid parsing errors.
- Confirm that the API credentials have sufficient permissions to update rule conditions in Shopware.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option or verify the SSL certificate validity.