You can configure to cascade data from parent to child jobs.

Overview

Jobs can be categorized into three types based on their relationship:

Independent – No parent/child relationship with other jobs
Parent – Serves as a template for child jobs, allowing content cascading based on the parent/child settings file
Child – Inherits content from the parent job (based on the parent/child settings file)

A job can be both a parent and a child, resulting in a grandparent or grandchild relationship.

Types of Cascade

Parent-child jobs can be cascaded as follows:

Hard Cascade - Cascades the data from parent to child regardless of the data present in the child-building blocks
Soft Cascade - Cascades the data from parent to child when the child building block is empty or blank
Soft Cascade on Create - Cascades the data from parent to child only when the child job is new
None - No cascade will occur

The parent/child settings file determines how data is inherited, or cascaded from parent to child.

Hard Cascade

Hard cascaded data in a child job is always synchronized with the parent job any time it is updated, including bulleted lists
The hard-cascaded content in a child job is non-editable within the child and can only be updated by cascading from the parent
If an empty parent field is hard-cascaded, it removes the previous parent entries but does not delete content added to that child job
Additional content can be added to the field in the child job and can be edited and managed within the child job after a hard cascade is applied

Soft Cascade

When a child job is initially created, it will inherit the content from the parent job
If a parent job is updated, empty building blocks and bullet lists will be updated from the parent
- For a bullet list, empty is defined as:
  - 0 rows
  - Default Rows - defined as one of the following in the Bullet List Designer:
    - Pre-Defined
    - Override Reference Bullet List
    - Override Expression
- In other content, empty means that there is no data or text in the field
Child content can be edited and the parent job will not update these blocks as long as the block is not empty.

Soft Cascade On Create

When a child job is created, it will inherit the cascaded content from the parent only for the first time
Child job content can be updated, edited, or deleted; parent job never overwrites those fields

Cascading Rules

Applying Cascades to Child Jobs (Hard Cascade and Soft Cascade)

If no action is taken to cascade from a parent to a child job, the child will retrieve the cascaded content when the job is opened in the edit mode and reflect the latest changes in the form.

For detailed information on Manual Cascade, refer to the article, “Cascading Parent Job Data to Children.”
For detailed information on Mass Cascading Jobs, refer to the article, “Mass Cascade Jobs.”

Making an Existing Job as a Parent or Child (Cascade on Save)

When an existing job (that is not in a workflow) is made a parent or child job, cascading is done when the job is saved.

This can be configured in the following property of the business rules:

PromptCascadeOptionWhenSaveParentJob & Auth Settings → CJ_CascadeParentToChildren

Cascading while Importing Jobs

Manual Import

While importing jobs, there is an option to enable cascading.
If this option is set to True, the import process checks the configuration in the parent/child settings file
The cascading rule during job import is:
1. If a parent job is imported, all child jobs will be cascaded
2. If a child job is imported, the parent will be updated and then the child gets the cascade

Remote Tasks

A cascading property is added to the Job Import remote task to support the three types of cascading
If this property is enabled, the import task checks the configuration in the parent/child settings file and applies the cascade

Cascading rules are applicable only while imports managed through JDX. These rules are not applied while importing jobs from third party sites (for example, Workday or Marketpay).

Independent, Parent, and Child Jobs