Record Producer Routing Checklist

Map only valid target fields

Map producer variables to the created record using backend field names. Validate optional custom fields before setting them, and keep the mapping readable so future changes are safe.

• Use backend names
• Handle empty values
• Validate custom fields
• Keep routing separate from display logic

Centralise assignment logic

When assignment depends on category, subcategory, technology or application, use a maintained mapping table or Decision Table. This is easier to support than a long chain of hard-coded conditions.

Minimum test set

Test every supported combination, an unsupported combination, empty optional values and inactive mappings. Confirm the created incident values, assignment group and user-facing error behaviour.