Atlas — Standard Models

Naming convention

By convention, Process Commander includes a standard model named pyDefault for most standard concrete classes and several standard abstract classes. For example, the Data-Admin-Operator-ID.pyDefault model provides initial values for about 25 properties in the Operator ID data instance.

This is not a reserved name and has no special characteristics. You may create models with this name or other names in any class or RuleSet.

Models that apply to classes derived from Work-

Whenever a new work object is created, Process Commander uses the pyFlowName property in the object to identify a flow rule to start.

If you create a model named pyDefault with the Applies To key part class derived from the Work- base class, include a value for the pyFlowName property. In most cases, select the Call SuperClass model checkbox to apply the ancestor pyDefault models also.

Set the value of this property to the Flow Type key part of a flow rule. When a user starts a new flow in the context of that Work- class, the system uses this value, with rule resolution to find the flow rule to run.

Applies To	Model	Purpose
Work-	pyCopyDefault	Determines which properties are copied when a user copies a work object. See Harness rules — How to copy a work object.
Work-	pyDefault	Provides default initial values for properties in new work objects.
Work-Cover-	pyDefault	Provides default initial values for properties in new work objects that are covers.
Work-Folder-	pyDefault	Provides default initial values for properties in new work objects that are folders.
Work-.RuleCheckin	pyDefault	Provides default initial values for properties in new work objects for the rule check-in flow.
PegaSample-Scanned	pyDefault	Demonstrates ScanStation facilities.
PegaSample-SimpleTask	pyDefault	Demonstrates entry of a Simple Task work object, not part of a cover.
PegaSample-CustomerRequest	pyDefault	Demonstrates entry of a cover work object.
PegaSample-Task	pyDefault	Demonstrates entry of a covered work object.

Models that apply to System-User-MyRules class

By default, the order and link labels for reports in the Monitor Activity workspace are controlled by model rules with System-User-MyRules as the Applies To key part. Override these standard model rules and then modify your rule to reference and label reports as desired.

Applies To	Model	Purpose
System-User-MyRules	AssignmentMonitoring Reports	Determines the order and labels of reports (that are available to all users) in the Monitor Assignments area of the Monitor Activity workspace. See Reports in the Monitor Process Assignments category.
System-User-MyRules	DataReports	Not used in V6.1.
System-User-MyRules	PerformanceAnalysis Reports	Determines the order and labels of reports (that are available to all users) in the Analyze Performance area of the Monitor Activity workspace. See Reports in the Analyze Process Performance category.
System-User-MyRules	RuleReports	Not used in V6.1.
System-User-MyRules	WorkAnalysisReports	Determines the order and labels of reports (that are available to all users) in the Analyze Process Quality area of the Monitor Activity workspace. See Reports in the Analyze Process Quality category.
System-User-MyRules	WorkMonitoringReports	Determines the order and labels of reports (that are available to all users) in the Monitor Processes area of the Monitor Activity workspace. See Reports in the Monitor Processes category.

Other standard model rules

Applies To	Model	Purpose
(various)	pyTrackSecurityChanges	Affects data retained in history for data objects or rules. See How to enable security auditing for rule or data changes.

About Model rules
Atlas home