Use this activity to modify information on an Active Recurring Service Program. In this program status the user can change the program valid period, add recurring service scopes or change the related recurring service scope interval, cycle pattern and valid period. Additionaly the user can manually add one or more Service Scopes only to a single Schedule Occurrence that are in status Generable.
When the Regenerate the Schedule badge appear on the program header a schedule regeneration is required. This is due to manual changes done in either Recurring Service Program parameters (Program Valid From/To or change of applied Calendar) or Recurring Service Scope parameters (addition of a recurring service scope or change in Cycle Pattern, Occurrence Interval or Scope Valid From/To for any recurring service scope). Use the Generate Schedule command to regenerate the schedule.
When the Generate Schedule command is used the user is prompted to retain manual changes or not. Manual changes that can be retained include change of Due Next date, Schedule Status or if one or more scopes has been added to a single Schedule Occurrence line and will be noted by the Manually Changed badge on the Schedule line.
A Recurring Service Program should exist in status Active.
As a result of this activity, information on Recurring Service Program is changed and schedule needs to be regenerated in the Schedule tab. This will be indicated by a badge on the Recurring Service Program header.
If the valid period of the program is changed and there are already generated requests which falls outside of new valid period, at regeneration of the program schedule the status of those schedule occurrence lines will be set to Not In Current Schedule.
When regenerating the program schedule and recurring service scopes has been added since last regeneration, the recurring service scopes will only be added to Schedule Occurrence lines in status Generable or On Hold according to the Service Scope's Occurrence Interval or Cycle Pattern.
For usage-based recurring service programs in particular, the schedule status will be set to Not needed if a Request is not generated for a program occurrence that has already reached/ passed the current Trigger Value and a measurement/ reading is recorded that reach/pass the next Trigger Value. Here, the existing schedule line will be set to Not needed and a new line will be created in status Generable.
When regenerating the program schedule and the user accepts to retain the changes to an Active program schedule, the schedule will be updated from Schdule Triggers and Scope parameters where changes to manually changed lines are retained. For Schedule lines where the Due Next date is changed to a date inside the Program Valid From/To dates, but would not exist in the regenerated schedule, the Schedule Occurrence lines will be retained as before regeneration and still in status Generable and marked Manually Changed.
For usage-based programs, Generate Schedule command will not prompt the user to continue removing manual changes or not. If the manual changes are to be removed from an Active program, user can either delete the manually added scope, set the status back to Generable from On Hold. When the user performs these actions, the Manually Changed badge will be removed. If the Manual changes are to be removed from a Preliminary program, user can use the Generate Schedule command and all manual changes will be removed.
When regenerating the program schedule and the user does not accept to retain changes the schedule will be generated based on Service Triggers and Scope Parameters only.