Matching Medical Inquiry record types on Case and Inquiry
Key Takeaway
The record type on Case and the record type on Inquiry must have the same name, Medical Inquiry. Having a record type on each object is not enough for the Medical Inquiry workflows to run as expected.
In Life Sciences Cloud, a medical inquiry is stored as two records that the system creates together: a parent Case and a child Inquiry. To make the pair behave as one, you create a Medical Inquiry record type on both objects with the same name. The matching record types give routing rules, path components, and analytics a single, consistent context.
Why the record type names must match
Every medical inquiry depends on the Case and Inquiry objects working together. The system creates the parent Case and the child Inquiry at the same time. Matching record types on the two objects keep the two records in sync for the user.
Having a record type on each object is not enough. The Case and Inquiry record type names must be the same for the Medical Inquiry workflows to run as expected. So if each object has its own record type and the workflows still don't run as expected, mismatched names are the likely cause. The fix is to make the names the same.