Configuring schedule behavior

You can configure how schedules behave in Schedule Manager with the following preferences:

• SM_ALLOW_INPROCESS_REMOVAL_OF_SUBSCHEDULE — Prevents removal of subschedules that are started and are in progress. (Note: The values of the SM_PREVENT_DELETE_STATES preference takes precedence over the value of this preference for subschedules.)
• SM_Copy_Schedule_Async — Determines the default selection when the user performs the Save As or Create a Schedule from the Template command. (True == Asynchronous Copy Schedule)
• SM_CriticalPath_Color — Sets the color for display of the critical path.
• SM_Delete_Schedule_Async — Determines if delete schedule behavior is asynchronous (True == Asynchronous Delete Schedule)
• SM_LIMIT_SINGLE_MASTER_SCHED — Limits subschedules to have only one master schedule.
• SM_SCHEDULE_DATE_LINKED_TO_ACTUAL — Default value for linking planned and actual schedule dates. If set to true, all schedules by default have the schedule dates linked to actual. (Note: This preference sets the Are Dates Linked schedule option for all schedules or leaves it up to the schedule coordinator.)
• SM_PV_FILTER_SHOW_SCHEDULES_ON_EMPTY — Determines whether schedule nodes are displayed when no tasks are returned from a filter-only criteria in the Program View.
• SM_Structure_Partial_Context — Specifies the load behavior for loading subschedules in a master schedule context.
• SM_View_CriticalPath — Sets the default display of the critical path.
• SM_SchedulingEngineOptions — Manages the deactivation of scheduling and execution validations.

Business Modeler IDE conditions

You can also configure how schedules behave in Schedule Manager with the following Business Modeler IDE conditions:

• Fnd0SMAbortScheduleNotification — Returns true if the schedule state is aborted.
• Fnd0SMAbortTaskNotification — Returns true if the task state is aborted, the schedule state is not aborted, and the task did not start or should have started.
• Fnd0SMHasTaskStarted — Returns true if the task state is not not started, closed, nor aborted.
• Fnd0SMIsCompletePercent100 — Determines if the task complete_percent is 100.
• Fnd0SMIsCompletePercentComplete — Returns true if the task complete_percent is 100 and the task state is not complete.
• Fnd0SMIsCompletePercentInProgress — Returns true if the task complete_percent is between 0 and 100 and the state is not_started or complete.
• Fnd0SMIsTaskComplete — Returns true if task complete_percent is 100 and the state is complete.
• Fnd0SMIsTaskStatusComplete — Returns true if task state is complete and complete_percent is not 100.
• Fnd0SMIsWorkCompleteInProgress — Returns true if the task work_complete is greater than 0 and the status is not_started.
• Fnd0SMSendAbortNotifications — Determines if notifications are sent when a task or schedule is aborted. The default is true.
• Fnd0SMUseInitActualLogic — Determines if the default Teamcenter logic should be used to initialize actual dates. The default is true.
• Fnd0SMUsePCStatusLogic — Determines if the default Teamcenter logic should be used to enforce setting complete_percent to 100 when the state is complete. The default is true.
• Fnd0SMUseRollupLogic — Determines if the default Teamcenter logic should be used to roll up status changes. The default is true.
• Fnd0SMUseTaskStartedLogic — Determines if the default Teamcenter logic should be used to initialize the status when work starts. The default is true.
• Fnd0SMWorkflowAbort — Returns true if the task state is aborted.
• Fnd0SMIsTaskAssignee — Returns true if the task type is standard, milestone, or gate.
• Fnd0SMIscostDba — This condition returns true if the role of the currently logged-in user is CostDBA.
• Fnd0SMCanLoggedInUserModifySchedulingData — This condition returns true if the currently logged-in user is a coordinator on the schedule.
• Fnd0SMCanLoggedInUserModifyTaskExeData — This condition returns true if the currently logged-in user is a coordinator or participant on the schedule.