Reading the Program Subtab - Example 2
This example is for a customer on a six-monthly minor-major Program.
"projectrules": [{
"//": "6 Mth Minor Major Alternating - Minor",
"project": [46],
"interval": 12,
"create": true,
"case": {
"type": 27,
"details": "${project.comments}",
"custevent_nxc_department": "${project.department}",
"assigned": 5
}
},{
"//": "6 Mth Minor Major Alternating - Major",
"project": [46],
"interval": 12,
"offset": 6,
"create": true,
"case": {
"type": 28,
"details": "${project.comments}",
"custevent_nxc_department": "${project.department}",
"assigned": 5
}
}]
The Program creates alternating minor and major cases at six-monthly intervals, starting on August 6, 2023.
In the Program sublist, the Program Date column displays six-monthly cases starting on August 6 and alternating between minor and major every six months. In the Case column, the minor and major cases are created. However, there's a gap on August 6, 2024 for a minor case. The Program resumes on February 6 and August 6, 2025, but the case start dates are for 2024, not 2025.
Information under the Related Records tab helps to explain the logic of the Program subtab.
This example shows how the matching logic described in How the Program Subtab Matches Cases to the Planned Schedule works in practice.
In this example, there's a major case on August 15 and then another one on February 6, 2024. The chronological order of the case types is Minor, Major, Major, Minor. An additional major case (number 468) was probably created manually by a user at some point. Consequently, Case 468 on August 15 has been slotted in by the Program as a major case. The Program then looks at the next existing case and finds that it's another major case (number 466), so it matches it against the next available major case program date, which is on February 6, 2025. This results in a gap, as there's no minor case before it. Then, the next case is a minor one, but it has to be scheduled chronologically after the February 6, 2025 case. The next available slot is August 6, 2025, so the case for August 6, 2024 is matched against it.
This example demonstrates the risks and potential confusion that can occur after the Program for a Project is changed partway through, or after additional manual cases are created.