Use this activity to modify information on an Active Recurring Service Program. In this program status the user can change the programs validity period, add recurring service scopes or change the related recurring service scope interval, cycle pattern, request grouping method and validity period. It is also possible to manually add one or more Service Scopes only to a single Schedule Occurrence as long as the schedule line is in status Generable.
When Regenerate the Schedule appears on the program, 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 Scope Location, Cycle Pattern, Occurrence Interval or Scope Valid From/To for any recurring service scope). Use the Generate Schedule command to regenerate the schedule.
If manual changes have been made to the schedule and Generate Schedule is used, the user will be asked if manual changes should be retained or overwritten. Manual changes include changes to the Due Next date, Schedule Status or if one or more scopes has been added to a single Schedule Occurrence line and all changes are flagged as Manually Changed in the Schedule tab.
A Recurring Service Program should exist in status Active.
As a result of this activity, information on Recurring Service Program is changed and the schedule needs to be regenerated in the Schedule tab. This will be indicated by a badge on the Recurring Service Program header.
If the validity period of the program is changed and there are already generated requests which falls outside of new validity 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 the 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 has reached/passed the next Trigger Value. The existing schedule line will be set to Not needed and a new line will be created in status Generable.
When regenerating an Active program schedule and changes are retained, the schedule will be updated from Schedule 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 programs 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.
If the request generation method of the program is changed, Existing requests in the recurring service program will remain the same, but the schedule lines that can generate requests will be adjusted accordingly.