Defining Custom Conditions
This section provides an overview of custom conditions and discusses how to define custom condition processes.
A condition table provides a solid structure for condition expansion, including condition processes. You can create custom conditions based on demographic data and existing student record data, as well as criteria such as eligibility to enroll, completion of a specific test, or some unique combination of conditions required for enrollment in a specific course.
Because only certain conditions (such as GPA, student group, academic plan, academic program, milestone, and external and internal degree) are delivered with Academic Advisement, you can create additional conditions as needed.
Every institution can create unique conditions to meet specific needs. For example, you might need to establish a minimum age requirement for a wine tasting course by creating a condition based on minimum age and attaching that condition to an enrollment requisite for the wine tasting course. As another example, a custom condition might verify that a student is not only in a program, but eligible to enroll in that program.
Your programmer can write a new Cobol program to set up customized processes using this table. The person who writes the program should be experienced in how PeopleSoft software handles Cobol. Pass parameters entering the custom program using the copybook SRCUCOND. (The bind and select variables in the stored statements must also match, otherwise the program stops running, usually with a remote call error.) The only values that you pass to the custom program are condition status, condition status message, condition code, condition effective date, and condition line sequence number. The custom program should only return the condition truth value, either T or F. Here is the actual Cobol code from SRCUCOND.cbl:
02 COND-STATUS PIC X(01).
02 COND-STATUS-MESSAGE PIC X(50).
02 COND-STATUS-SPEC PIC X(06).
02 EFFDT PIC X(10).
02 COND-LINE-SEQ PIC S9(04).
02 COND-TRUTH-VALUE PIC X(01).
88 COND-TRUE VALUE 'T'
88 COND-FALSE VALUE 'F'
If you need any other values, they must be linked to the custom program as an external copybook. Here is the code from the custom program SRPCU001.cbl that shows how the ID was passed into the custom program:
01 CADAE EXTERNAL. COPY SRCCADAE.
LINKAGE SECTION
01 SQLRT. COPY PTCSQLRT.
01 CUSR1. COPY SRCUCOND.
PROCEDURE DIVISION USING SQLRT
CUSR1.
Depending on the condition that you want to create, you may want to copy the external array SRCCACDD into the working storage area of the new condition program. If you copy the external array SRCCACDD into the working storage area, it should look like this:
01 CACDD EXTERNAL. COPY SRCCACDD.
Note: The linkage section should look like that of the three demo programs: SRPCUSR1, SRPCUSR2, and SRPCUSR3.
The linkage section and procedure division should look like this:
LINKAGE SECTION
01 SQLRT. COPY PTCSQLRT.
01 CUSR1. COPY SRCUCOND.
PROCEDURE DIVISION USING SQLRT,
CUSR1.
Note: Do not copy external arrays other than SRCCACDD into working storage, because other parameters may be modified in future releases. However, information in array SRCCACDD is to be supported in future releases.
To create custom conditions:
With the assistance of a developer, create a customized process.
Create a new condition process identifier using the Define Condition Processes page.
Enter the effective date, status, descriptions, logical process type, logical name, process key format, and requirement key count (if appropriate) for the condition process identifier.
Use this condition process identifier as a user programmable condition on the Define Dynamic Condition page.
Set up the condition line sequence detail as appropriate. The fields that are available for your entry in the Condition Line Details group box depend on the process key format value that you selected on the Define Condition Processes page. Also, the number of condition line detail sequences that you define must correspond with the required key count that you identified on the Condition Processes page.
Page Name |
Definition Name |
Navigation |
Usage |
---|---|---|---|
Define Condition Processes |
CONDITION_PROC_TBL |
|
Establish custom condition processes. |
Access the Define Condition Processes page (
).Image: Define Condition Processes page
This example illustrates the fields and controls on the Define Condition Processes page. You can find definitions for the fields and controls later on this page.
To create a custom condition, establish a new condition process identifier that you use to create a new condition specification. Once you create a condition specification, it may be referenced as a precondition or condition requirement by academic and enrollment requirements, as well as academic and enrollment requirement groups.
Field or Control |
Definition |
---|---|
Condition Process Identifier |
An arbitrary number that is unique for each condition process identifier. You can use this condition process identifier as a precondition or condition requirement. |
Note: These condition process identifiers are delivered with the system: 0001 Milestone Check, 0002 Internal Degree Check, and 0003 External Degree Check. Delivered field values are numbered from 1 through 500. Added values should be numbered above 500.
Field or Control |
Definition |
---|---|
Effective Date |
The latest effective date that you entered for the condition process identifier is used during analysis. |
Description and Short Description |
Enter descriptions for the condition process identifier that you want to establish. None of these values appear on the audit reports. These fields are used for documentation purposes only. |
Logical Process Type |
Select the process. Currently, the only field value available is Cobol Process. |
Logical Name |
Enter the logical name of the program that is called for this specific condition process identifier. |
Process Key Format |
Select the process key format that controls what fields are available on the Define Dynamic Condition page. This field value also determines which logical name is called. Values are: TYP1 Program Key: Provides the keys (values) needed to run the program. This is the default value. TYP2 Milestone Key: Provides the keys (values) needed to define and validate a milestone. TYP3 Internal Degree: Provides the keys (values) needed to define an internal degree as required. TYP4 External Degree: Provides the keys (values) needed to define an external degree as required. |
Ignore Key Count |
Select if the number of key values (or rows) on the Define Dynamic Condition page is irrelevant. The Required Key Count field becomes unavailable for edit. |
Required Key Count |
Enter the number of key values (or rows) that must be entered in the Condition Line Details group box on the Define Dynamic Conditions page. If you do not enter a key count value, then no entries are permitted. For example, suppose that the required key count is 4, then there must be four rows (condition line detail sequences) on the corresponding Define Dynamic Condition page. |