How Keep When Conditions Work
A Keep When condition evaluates a defined requirement against the current product configuration. When the requirement is satisfied, the configurator retains the associated selection or value according to the configured behavior. When the condition no longer applies, the system's configured rules determine whether the selection is removed, reset, or handled through another validation step.
These conditions help maintain relationships between product features as users change their selections. Rather than treating every option independently, the configurator can use conditional logic to represent compatibility, dependencies, and product-specific requirements.
A practical rule should identify three elements: the selection being retained, the condition that must be true, and the expected behavior when the condition changes. Clear definitions help product engineers and configurator administrators validate the result against manufacturing requirements.
Common Manufacturing Use Cases
Keep When logic is useful wherever a product's available options depend on previous choices or technical specifications. Common applications include:
- Component compatibility: Retain a compatible motor, controller, or accessory when the selected product variant supports it.
- Material selection: Preserve an approved material choice while the configured dimensions or operating requirements remain within the permitted range.
- Feature dependencies: Keep a related option available when another required feature is selected.
- Product variants: Maintain applicable settings when a user switches between supported sizes, models, or performance levels.
- Configuration consistency: Align customer selections with engineering rules that govern which combinations can be manufactured.
These applications can support more consistent quotes and product definitions. The specific implementation should distinguish between retaining an existing value and merely allowing that value to appear as an available choice.
Keep When Rules and Product Data
Conditional rules work alongside product attributes, option definitions, and the configured product structure. A Bill Of Materials Bom describes the components and quantities needed to manufacture an item, while configurator rules determine which options and components apply to a particular customer selection. The resulting configuration should align with the appropriate bill of materials, routing, and production requirements.
Consider a configurable pump offered with standard and high-capacity motors. If the high-capacity option requires a particular power supply, the rule should retain that supply only when the relevant motor and product requirements are satisfied. Engineers should test changes in both directions, including switching from the high-capacity motor back to the standard version, to verify that dependent selections follow the intended logic.
Testing should also cover default values, optional components, incompatible combinations, and changes to upstream attributes. Product teams can document expected results for representative configurations and compare them with actual configurator behavior before releasing rule changes.
Configuration Governance and ERP Integration
In an epicor implementation, configurator behavior should align with the organization's product data and connected ERP workflows. The configuration may influence quotes, sales orders, production planning, component requirements, and cost calculations, depending on the solution and setup. Epicor ERP provides the broader enterprise resource planning context in which product, manufacturing, and business transactions can be managed.
Accurate configuration data also matters to financial processes. The concept of Epicor Integration Finance covers how ERP information connects with finance workflows, while Epicor ERP Modules describes the functional areas that support different operational and business processes. Consistent product identifiers, option details, and transaction values help maintain continuity as configured products move through quoting, ordering, manufacturing, and financial reporting.
For finance automation that operates alongside ERP workflows, the Hyperbots Platform supports company-specific configurations such as ERP integrations, workflows, roles, and general ledger structures through a no-code framework. Its Process Specific Capabilities apply AI automation to defined business processes using domain-relevant data, and Ready to Deploy Capabilities provide pre-trained agents and pre-built ERP connectors for supported finance tasks.
Self Learning Capabilities enable supported workflows to adapt based on human actions, while Human in the Loop supports exception escalation, approvals, and feedback. For customer payment reconciliation and receipt posting, How Hyperbots AI Agents 10x Epicor Finance Operations and Closing Epicor Finance Gaps with Hyperbots AI Agents discuss finance automation that can extend ERP workflows beyond product configuration.
Best Practices for Maintaining Keep When Rules
Keep When conditions should be maintained as part of the product's controlled configuration logic. When engineering changes introduce a new option or alter component compatibility, the associated conditions should be reviewed alongside product structures and downstream processes.
- Use clear condition names that describe the selection and requirement.
- Document the expected result when a user changes or removes a related option.
- Test valid, invalid, and boundary combinations with representative product configurations.
- Check that retained selections agree with engineering specifications and production requirements.
- Revalidate affected rules after product, pricing, or integration updates.
These practices help keep configured products consistent with engineering intent and ensure that sales and production teams work from dependable configuration results.
Summary
Epicor Configurator Keep When is conditional configuration logic that helps retain applicable selections when specified requirements are met. By defining clear dependencies, validating product combinations, and aligning configuration behavior with product data and ERP workflows, manufacturers can support accurate product definitions, consistent quotations, and reliable downstream operations.