Inherit Sample Properties from Job Properties

The job and sample properties are commonly distinct of each other. That is, each property of the sample exists independently from the job. However, there are also valid scenarios where certain sample properties must be tied in or in-sync with the job. CCLAS 6 allows for both scenarios to exist via the PROPAGATE_FROM_JOB_TO_SAMPLE_LIST preference. The preference contains a list of properties defined on the job level that will be inherited on the sample level on submit. For instance, if the original client code for the job was to be changed to another client and that change is persisted (user clicks submit) and client code was one of the properties defined in the preference, then the client code value stored in the samples are also updated to the client code declared on the job. See PROPAGATE_FROM_JOB_TO_SAMPLE_LIST for a list of properties that can be pushed from the job to the samples. If the preference is not present or the property is not declared in the preference, then updating the job record will not impact the sample record for that property.