PROPAGATE_FROM_JOB_TO_SAMPLE_LIST

This is a preference that defines the allowed properties that can be inherited from a job to its underlying samples.

When a job is updated, then:

If empty (default on deploy), or the preference is missing, or contains no valid job scheme attributes, then if any of the listed attributes on the job are changed, then there is no impact to the job's samples.
If not empty, then, for each valid job attribute in the list, if the value of the attribute is changed on the job, then the value is pushed to the related attribute on each of the job's samples.

Typically the preference is not set at role or user level.

STRING, comprising a comma-separated list of job attributes, including:

Job update screen label	Preference setting	CCJob.update attribute	CCSample.update attribute	CCJOB field (multiple fields are kept in sync)	CCSAMPLE field (multiple fields are kept in sync)
Primary Details tab > Agreed On	agreedDate	agreedDate	agreedDate	AGREED_DATE	AGREED_DATE
Primary Details tab > Authorisation User Group Code	authUserGroup	authUserGroupCodeauthUserGroupId	authUserGroupCodeauthUserGroupId	AUTH_USER_GROUP_ID	AUTH_USER_GROUP_ID
Status tab > Authorised By	authorisationUser	authorisationUserCodeauthorisationUserId	authorisationUserCodeauthorisationUserId	AUTHORISATION_USER_ID	AUTHORISATION_USER_CODE AUTHORISATION_USER_ID
Status tab > Authorised On	authorisedDate	authorisedDate	authorisedDate	AUTHORISED_DATE	AUTHORISED_DATE
Primary Details tab > Contact Code	clientContact	clientContactCodeclientContactId	clientContactCodeclientContactId	CLIENT_CONTACT_CODE CLIENT_CONTACT_ID	CLIENT_CONTACT_ID
Primary Details tab > Client Code	client	clientCodeclientId	clientCodeclientId	CLIENT_LAB_CODE + CLIENT_CODE CLIENT_ID	CLIENT_ID
Primary Details tab > Project Code	clientProject	clientProjectCodeclientProjectId	clientProjectCodeclientProjectId	CLIENT_PROJECT_CODE CLIENT_PROJECT_ID	CLIENT_PROJECT_ID
Primary Details tab > Client Submission #	clientSubmissionNumber	clientSubmissionNumber	clientSubmissionNumber	CLIENT_SUBMISSION_NUMBER	CLIENT_SUBMISSION_NUMBER
Primary Details tab > Contract	contract	contract	contract	CONTRACT	CONTRACT
Primary Details tab > Contract Submission #	contractSubmissionNumber	contractSubmissionNumber	contractSubmissionNumber	CONTRACT_SUBMISSION_NUM	CONTRACT_SUBMISSION_NUM
Primary Details tab > Cost Centre Code	costCentre	costCentreCode + costCentreLaboratoryCodecostCentreId	costCentreCode + <missing in service>costCentreId	COST_CENTRE_LAB_CODE + COST_CENTRE_CODE COST_CENTRE_ID	COST_CENTRE_ID
Primary Details tab > Discount	discount	discount	discount	DISCOUNT	DISCOUNT
Status tab > Finalised By	finalisedUser	finalisationUserCodefinalisationUserId	finalisationUserCodefinalisationUserId	FINALISATION_USER_ID	FINALISATION_USER_CODE FINALISATION_USER_ID
Status tab > Finalised On	finalisedDate	finalisedDate	finalisedDate	FINALISED_DATE	FINALISED_DATE
Primary Details tab > Fixed Price	fixedPrice	fixedPrice	fixedPrice	FIXED_PRICE	FIXED_PRICE
Fixed Price Currency	fixedPriceCurrency	fixedPriceCurrencyId	fixedPriceCurrencyId	FIXED_PRICE_CURRENCY_ID	FIXED_PRICE_CURRENCY_ID
Primary Details tab > Auto Receive (template and schedule jobs only)	autoReceive	isAutoReceive	isAutoReceive	IS_AUTO_RECEIVE	IS_AUTO_RECEIVE
Primary Details tab > Auto-validate Job?	autoValidate	isAutoValidate	isAutoValidate	IS_AUTO_VALIDATE	IS_AUTO_VALIDATE
Primary Details tab > Is Fixed Price?	isFixedPrice	isFixedprice	isFixedprice	IS_FIXED_PRICE	IS_FIXED_PRICE
Primary Details tab > Authorise Job?	requiresAuthorisation	isRequireAuthorisation	isRequireAuthorisation	IS_REQUIRE_AUTHORISATION	IS_REQUIRE_AUTHORISATION
Status tab > Last Report	lastReport	lastReportId	lastReportId	LAST_REPORT_ID	LAST_REPORT_ID
Status tab > Last Reported On	lastReportedDate	lastReportedDate	lastReportedDate	LAST_REPORTED_DATE	LAST_REPORTED_DATE
Status tab > Owner Changed On	ownerChangedDate	ownerChangedDate	ownerChangedDate	OWNER_CHANGED_DATE	OWNER_CHANGED_DATE
Primary Details tab > Owner By	ownerUser	ownerUserCodeownerUserId	ownerUserCodeownerUserId	OWNER_USER_ID	OWNER_USER_CODEOWNER_USER_ID
Primary Details tab > Possible On	possibleDate	possibleDate	possibleDate	POSSIBLE_DATE	POSSIBLE_DATE
Primary Details tab > Price Book Code	priceBook	priceBookId	priceBookCodepriceBookId	PRICE_BOOK_ID	PRICE_BOOK_ID
Primary Details tab > Priority	priority	prioritypriorityInSecond	prioritypriorityInSecond	PRIORITYPRIORITY_IN_SECOND	PRIORITYPRIORITY_IN_SECOND
Primary Details tab > Quote Code	quote	quoteCodequoteId	quoteCodequoteId	QUOTE_ID	QUOTE_ID
Primary Details tab > Received On	receivedDate	receivedDate	receivedDate	RECEIVED_DATE	RECEIVED_DATE
Primary Details tab > Received By	receptionUser	receptionUserCodereceptionUserId	receptionUserCodereceptionUserId	RECEPTION_USER_ID	RECEPTION_USER_CODE RECEPTION_USER_ID
Primary Details tab > Required On	requiredDate	requiredDate	requiredDate	REQUIRED_DATE	REQUIRED_DATE

When a job is updated, then:

If empty (default on deploy), or the preference is missing, or contains no valid job scheme attributes, then if any of the listed attributes on the job are changed, then there is no impact to the job's samples.
If not empty, then, for each valid job attribute in the list, if the value of the attribute is changed on the job, then the value is pushed to the related attribute on each of the job's samples.

Typically the preference is not set at role or user level.

Related Processes

Configuring Preferences for Registration