This might be applicable to any type of connector going to the Case object, but for the context of this request is related to setting up a ServiceNow connection to Case.
In addition to the problems outlined here:
there’s another glaring issue with the Case connector jobs. Any job requires these 4 fields to be mapped:
Why is this a problem? Beyond the initial case feed, if you have data you want to supplement on your Case records with an additional job, you need to map these fields every time. That means you have multiple fields updating the same fields, which is redundant, unnecessary, and poor design to force.
I have fields in my data schema that do not live on the standard SNOW case object, so I planned to build a job chain with supplementary jobs to add this information in. With these other field requirements, it makes that impractical at best. All I need to do is update some records on a case - I shouldn’t need these 4 fields present every time.