clsScheduleManager.PreSaveProcessing PostSaveProcessing

Apply schedule-driven transitions, DEF printing, and DEF notification.

Field	Value
Operation ID	schedule-save-processing
Trigger	Schedule workflow saves a schedule row.
Inputs	Current manager state, current claim/case context, and workflow-specific parameters or collections.
Outputs	Updated collections, messages, or side effects specific to the operation.
Primary components	clsScheduleManager.PreSaveProcessing / PostSaveProcessing
Entry point	SAIF.Application.Claim.Legal\LegalNet\clsScheduleManager.vb

Steps

1. Apply file-location, LCE, and case-status transitions driven by the schedule state.
2. Compute the DEF hold date as the next Friday, adding a full week when the current day is already Friday.
3. Resolve the attorney manager email through pk80001_LEGALNET.get_atty_mngr_email, falling back to ISClaimsAppsSupport@saif.com when the function returns blank.
4. Outside production, redirect DEF email to DPI.UserID & "@saif.com" instead of the resolved recipient.

Process flow

The following diagram visualizes this operation's control flow.

flowchart TD
  Start([Trigger]) --> S1[Load current state]
  S1 --> S2[Apply workflow rules]
  S2 --> D{"Validation or security<br>issue?"}
  D -->|Yes| EndErr(["Return message or block<br>action"])
  D -->|No| EndOk(["Return updated workflow<br>state"])

Failure and edge-case behavior

• DEF email is redirected in non-production even when a real manager email exists.
• Function-body behaviour for get_atty_mngr_email remains unavailable because the Oracle package body is not in this repository.

Related documentation

• Index
• Operations and processes
• Business rules
• Security and authorization
• Database tables
• SQL catalog
• Procedures
• API reference

Sources

• SAIF.Application.Claim.Legal\LegalNet\clsScheduleManager.vb