Colleague: User Interface (UI) Parameter Screens - WEB

ACWP – Web Access Core Parameters

• Use the Web Access Core Parameters (ACWP) form to enter parameters that are used by Colleague applications for web access.
• The following fields are also used by Colleague Self-Service:

• Valid Address Type - Used for graduation application address updates.
• Address Change Source - Used for address change requests.
• E-mail Return Address - Used as the return address for security notifications.

• Process ID: WCS002

AWWP – FA Award Acceptance Params

• Use the FA Award Acceptance Params (AWWP) form to set up and maintain the institutional parameters for the Accept Reject My Financial Aid Awards workflow. You can define the following:

• Awards and award categories that you do not want to appear on the Accept Reject workflow
• Award periods to include
• Whether you want students to accept/reject their awards at the annual level

• You can also set up action codes and communication codes to assign when a student accepts or rejects their awards at either a default level or a year-specific level.
• If your institution has the Accept/Reject at Annual Level flag set to Yes, only the award periods defined in the Include Award Periods field will be included in the student's annual award amount.
• Process ID: WAP020

BIWP – Banking Information Web Parameters

• Use the Banking Information Web Parameters (BIWP) form to define parameters for Banking Information Self-Service.
• Except for change notification paragraphs, all settings defined on this form take effect the next time the application pool is recycled. Change notification paragraphs take effect immediately.
• Process ID: PASU110

CCWP – Communication Code Web Params

• Use the Communication Code Web Params (CCWP) screen to specify the communication code parameters for documents to be listed in WebAdvisor.
• Process ID: WBCOP01

CEWP – Non-Degree/CE Web Reg Params

• Use this form to set up and maintain parameters related to the "instant enrollment" web workflow (Register and pay for Continuing Education classes). These parameters must be set up in order for the web workflow to be used.
• Process ID: WAP014

CFWP – Financial Web Params

• Use the Financial Web Params (CFWP) form to define parameters for web workflows in the Colleague Finance application.
• Process ID: WBCFP001

CINC – Colleague Integration API Configuration

• Use the Colleague Integration API Configuration (CINC) form to define and maintain parameters required by the Ellucian Messaging Service. These settings control the Ellucian Messaging Adapter's ability to connect to the AMQP message exchanges (defined within the Ellucian Messaging Service) and its ability to call the Colleague Web API to process data change events between Colleague and external systems.
• Process ID: UTS166

CLSP – Catalog Search Parameters

• Use the Catalog Search Parameters (CLSP) form to indicate which catalog search filters you want to hide in Colleague Self-Service Catalog Results or Catalog Advanced Searches. The system displays all by default.
• Process ID: WAP035

CPWP – Course Planning Web Params

• Use the Course Planning Web Params (CPWP) form to set up parameters used by the Plan Courses, Student Educational Planning, and Colleague Student Self-Service workflows. Some of these parameters also affect Academic Planning in Colleague Student Self-Service. If your institution uses the Student Course Planning and Smart Registration optional modules, you can also use this form to require that students use the course planning wizard when planning courses.
• Process ID: WAP030

CSEP – Course Sec E-Learning Param

• WebAdvisor is delivered with the capability to hyperlink from the Section Information form to an e-learning provider such as WebCT. Use this form to set up a rule that determines whether a hyperlink to an e-learning provider will be displayed on the Section Information form.
• Process ID: WAP029

CSWP – Class Schedule Web Parameters

• Use the Class Schedule Web Parameters (CSWP) screen to define the ways your faculty members and students are able to view their class schedule information via the Web.
• Process ID: WAP018

DIST – Distribution

• Use the Distribution (DIST) form to define codes determining the cash account debited for a payment. Distribution codes identify the general ledger (GL) distribution associated with any money received. Examples of distribution codes include those that describe a general operating fund or any number of restricted funds, such as those used for different research grants.
• Each distribution code must have a general ledger account defined for distributing the cash receipt. You can also define different GL accounts for any number of different payment methods. When a distribution code is used with a payment method not explicitly associated with a separate GL account for that code, Colleague debits the cash account.
• For example, for your general operating fund you might define one GL account for cash and another for credit card payments, but not one specifically for checks. When you record a cash receipt in the form of a check associated with this distribution code, Colleague debits the cash account.
• Process ID: EBP005

DMIF – Build Web Registry – Faculty

• Use the Build DMI Registry Faculty (DMIF) process to create or update user information for multiple faculty members. The process will do the following:

• Create records for the user in the Colleague Resource Database. These records store Colleague access and login information.
• If you are using LDAP synchronization, the process will create an LDAP entry with user information including the user ID and password.
• If you are using the ActiveCampus portal and populating it from Colleague, the process will create a SharePoint user profile.

• Individuals with an existing OPERS record will use that OPERS record, not the one specified in the Web Operator Equivalent field on this form.
• The way new user IDs are constructed is determined by the parameters defined on the Web User ID and PIN Options (WUIP) form. The process edits the user ID to ensure that it meets the following criteria:

• Must be all lowercase
• Cannot contain special characters except for dash (-), underscore (_), and dot (.).
• Cannot contain leading delimiters
• Minimum length of 3
• Maximum length of 24

• The process ensures a unique ID by appending a sequential counter, if necessary. For example, suppose Mary Smith is being added as a user and the user ID calculation method specified on the WUIP form is FL (full first and last names). If the user ID mary_smith is already in use, then a counter will be added so that the user ID will be something like mary_smith14.
• The process also checks for an existing user ID for this person. See the Web Administration manual for a description of this part of the process. If they do not have a user record yet, they will be given one using the user ID and their current PIN from the PERSON.PIN file as their Web password. If they do not have a PIN assigned, a new PIN will be generated using the PIN calculation type and length defined on the WUIP form.
• You may optionally produce a report for all people selected, showing their Web user ID and the PIN from the PERSON.PIN file.
• Process ID: FIF060

DMIS – Build Web Registry – Students

• Use the Build DMI Registry Students (DMIS) process to create or update user information for multiple students. The process will do the following:

• Create records for the user in the Colleague Resource Database. These records store Colleague access and login information.
• If you are using LDAP synchronization, the process will create an LDAP entry with user information including the user ID and password.
• If you are using the ActiveCampus portal and populating it from Colleague, the process will create a SharePoint user profile.

• Individuals with an existing OPERS record will use that OPERS record, not the one specified in the Web Operator Equivalent field on this form.
• The way new user IDs are constructed is determined by the parameters defined on the Web User ID and PIN Options (WUIP) form. The process edits the user ID to ensure that it meets the following criteria:

• Must be all lowercase
• Cannot contain special characters except for dash (-), underscore (_), and dot (.).
• Cannot contain leading delimiters
• Minimum length of 3
• Maximum length of 24

• The process ensures a unique ID by appending a sequential counter, if necessary. For example, suppose Mary Smith is being added as a user and the user ID calculation method specified on the WUIP form is FL (full first and last names). If the user ID mary_smith is already in use, then a counter will be added so that the user ID will be something like mary_smith14.
• The process also checks for an existing user ID for this person. See the Web Administration manual for a description of this part of the process. If they do not have a user record yet, they will be given one using the user ID and their current PIN from the PERSON.PIN file as their Web password. If they do not have a PIN assigned, a new PIN will be generated using the PIN calculation type and length defined on the WUIP form.
• You may optionally produce a report for all people selected, showing their Web user ID and the PIN from the PERSON.PIN file.
• Process ID: ACF071

DWEB – Define Account WebConfig

• Any DMI access from an account to the DMI Registry depends upon the data stored in the UT.PARMS record called WEBCONFIG in order to locate the DMI Listener and the associated DMI Registry. This screen allows the system administrator to place or modify data in this record without requiring a DMI Listener to be either running or pointed at this account. No DMI Registry validation takes place in this process. Restrictions to screen access must utilize existing Envision security methods. This screen can be used with both the C-based (DMI 1.0) and Java- based (DMI 2.0) DMI Listeners.
• Process ID: DMS007

EAWP – e-Advising E-mail Web Params

• Use the e-Advising E-mail Web Params (EAWP) screen to enter the e-mail types for the student and faculty to be used by the Student Educational Planning and the E-mail My Advisor(s) workflows, as well as the E-mail Advisor(s) option in the Plan Courses workflow.
• If you leave these fields blank, the e-mail type on the Web Access Core Parameters (ACWP) screen is used.
• Note: If the student or advisor does not have an e-mail type that matches the type entered on the EAWP screen, the system checks the ACWP screen. If the student or advisor does not have an e-mail type that matches the type entered on the ACWP screen, then the first e-mail address on the Name and Address Entry (NAE) screen is used.
• If you want the faculty e-mail address to match the one on the Class Roster and the Student Profile, then the type specified here needs to match the type on the Web Student Profile Params (SPWP) screen.
• Process ID: WAP031

ECPA – e-Commerce Provider Account

• Use the e-Commerce Provider Account (ECPA) form to define information about an account you have with your e-commerce provider. To implement e-Commerce, your institution needs to have at least one e-commerce provider account and, depending on whether or not separate accounts are needed to process different types of payments, you may need to have more than one account.
• For example, you may be required to process credit card payments through one account, and electronic check payments through another account.
• Note: Check with your e-commerce provider and/or merchant bank to determine if unique terminal IDs will be needed to process different payment types. If so, you will need to set up more than one e-commerce provider account.
• For each account you have with your e-commerce provider, you will need to define the following:

• Description. The type of payments to be processed through this account.
• e-Commerce Provider. The e-commerce provider for this account, defined on the e-Commerce Providers (ECPR) form.
• Account Number/Login. The application ID assigned to your Official Payments account, or the login ID assigned to your PayPal or TouchNet account.
• Account Password. The password for the associated account login, if one is required.
• Java Class. The interface between Colleague and the software used by your e-commerce provider to receive and send electronic transactions.

• Depending on your e-commerce provider and the types of transactions being processed through this e-commerce provider account, you may also need to enter a user name.
• Note: For each e-commerce provider account you define, you must have a corresponding payment provider account defined in the Ellucian Payment Gateway.
• Process ID: EBP003

ECPR – e-Commerce Providers

• Use the e-Commerce Providers (ECPR) form to define the information that Colleague needs to communicate with your e-commerce provider. Your institution must have at least one e-commerce provider defined and, depending on your processing needs, may have more than one.
• For example, you may use PayPal to process electronic check payments guaranteed by Telecheck, and use Official Payments (OPC) to process your credit card payments.
• For each e-commerce provider that your institution uses, you must define the following information on the ECPR form:

• Host Address. The domain name server (DNS) or Internet Protocol (IP) address supplied by PayPal, or the URL supplied by OPC or TouchNet.
• Host Port Number. The port number supplied by your e-commerce provider.
• Transaction Timeout. The number of seconds after which certain types of transactions are cancelled.

• Note: Your e-Commerce Provider must also be configured as your Payment Provider in the Ellucian Payment Gateway. Use the information defined on the ECPR form to configure your Payment Provider settings in the Payment Gateway.
• Process ID: EBP002

EDPS – Ethos Data Privacy Setup

• Use the Ethos Data Privacy Setup (EDPS) form to specify the properties you want to secure for data privacy. When the API is run, Colleague reads the data privacy definition and evaluates it to restrict read access to the properties defined on the setup form. You can link properties within an API to specific users, roles, or permission codes.
• Note: You must clear the cache on the application server for the changes to take effect right away.
• Process ID: PASU114

ENWP – Enrollment Request Web Param

• Use the Enrollment Request Web Param (ENWP) form to set up and maintain parameters for enrollment verification requests that students submit online.
• Process ID: WAP012

EPAM – e-Comm Provider Acct Mapping

• Use the e-Commerce Provider Account Mapping (EPAM) form to map processing for all or specific types of e-commerce payments to an e-commerce provider account. Your institution must have at least one e-commerce provider account mapping and, depending on your business practices, may have multiple e-Commerce provider account mappings.
• At a minimum, you must define the following for an e-commerce provider account mapping:

• Description - describes the types of e-commerce payments being processed.
• e-Commerce Provider - defines the e-commerce provider account through which e-commerce payments will be processed.

• If you define only one mapping and do not define any other criteria on the EPAM form, all e-commerce payments for your institution will be processed through a single e-commerce provider account.
• However, if you want specific payments to be processed through separate e-commerce accounts, define one or both of the following:

• Distribution - if entered, maps e-commerce payments recorded with this distribution to this e-commerce provider account. For example, you may want to record and process your e-commerce payments for credit courses and your e-commerce payments for continuing education separately by defining e-commerce mappings for each distribution.
• Transaction Type/Payment Method - if entered, associates a payment method with a specific type of e-commerce transaction. For example, you may want to process the e-commerce credit card payments you receive via mail or telephone (MOTO) and your card-present e-commerce credit card payments (CRDPRES) separately by defining e-commerce mappings for each transaction type.

• You can also optionally assign a convenience fee to be charged for e-commerce transactions processed with a specific mapping. For example, you may want to charge a flat fee for all electronic check payments, but charge a percentage fee for all credit card payments by defining separate e-commerce mappings for different transaction types.
• When an e-commerce payment is recorded, Colleague determines the type of e-commerce transaction, and then maps the payment's processing according to the criteria you define on the EPAM form.
• Process ID: EBP006

EPWP – Ed Plan Web Parameters

• Use the Ed Plan Web Parameters (EPWP) screen to maintain parameters used in the Student Educational Planning and Plan Courses workflows, as well as the course planning wizard on the Web.
• Process ID: WSEPP001

ESSS – DMI Error Messages

• Use the DMI Error Messages Form to list and alter the message text for any DMI error code.
• Process ID: DMS019

FAWP – FA Inst Web Parameters

• Use the FA Inst Web Parameters (FAWP) form to define institutional parameters for Financial Aid forms on the web. The FAWP form allows you to define the following for Award by Term and Award by Year, Shopping Sheets, and Award Letters forms:

• FA years that web users can view for all the forms mentioned above and for which they can accept or reject awards.
• Award periods that web users can view for Award by Term and FA Award by Year. (Detail to the FA Award Acceptance Parameters (AAWP) form to select award periods for which users can accept or reject awards.)
• The eligibility rule to use to determine whether a student has access to the data.
• Which award action categories to include on the forms.
• Whether the Shopping Sheet and Award Letter are viewable on the web.
• The address hierarchy and award letter definition to use.

• From the FAWP form, you can detail to the following parameter forms:

• FA My Loans Web Parameters (FLWP)
• FA Electronic Consent Parameters (FECP)
• FA Award Acceptance Parameters (AWWP)
• Award Letter Definition Rule (ADRL)
• FA Office Web Parameters (FOWP)
• Eligibility Rule Table (AERL)

• Note: There are several fields on the FAWP form that can be overridden at the office level by detailing on the Office Level Settings field to the FOWP form. These settings are:

• The award letter definition rule that determines which subroutine will be used to print award letters.
• Which award action categories are viewable on the forms.
• Whether the Shopping Sheet and Award letter are available on the web.
• The award letter definition rule for the award letter to use.

• Note: The eligibility rule tables can also be overridden at the office level.
• Process ID: WAP007

FECP – FA Electronic Consent Parameters

• Use the FA Electronic Consent Parameters (FECP) form to enter text that will be displayed on the Financial Aid Paper Correspondence Option form in WebAdvisor. This text is intended to explain that students can receive paper copies of their financial aid correspondence in addition to the electronic correspondence they already receive.
• Process ID: WAP050

FIWP – Financial Web Parameters

• Use the Financial Web Parameters (FIWP) form to define the parameters used to process payments through WebAdvisor, and to enable Colleague e-Commerce processing both in WebAdvisor and on Colleague cash receipt entry forms. The FIWP form is also used to set up the account summaries available to students through WebAdvisor.
• The parameters defined on the FIWP form determine the following:

• Whether WebAdvisor users are allowed to make payments.
• Whether WebAdvisor payments and cashier payments recorded in Colleague will be processed through Colleague e-Commerce.
• The content of the acknowledgement notice displayed on the payment acknowledgement form and sent through email after the WebAdvisor user processes a successful payment. You can also specify the person or office at your institution that receives a copy of that email.
• The cashier used for web payments.
• Whether users can specify that payments be applied toward charges for a particular term.
• Whether users can make partial payments on their charges.
• The types of receivables that users can pay.
• The date range or terms used to select the charges that appear on the Account Summary and Pay on My Account forms.
• The types of payment methods available for WebAdvisor payments.

• Note: If you accept payments through WebAdvisor, you must have Colleague e-Commerce licensed and implemented at your institution.
• Note: The setting that you define for accepting Payments by Term must be compatible with the parameter that you define for allocating non-term payments on the AR Defaults and Parameters (ARDE) form. Refer to the Getting Started with Colleague Student manual for information about defining AR defaults and parameters.
• The FIWP form also provides access to the parameter forms used to define settings for the Student Finance Views. Some of the settings that you define on the FIWP form can also be maintained on the Student Finance parameter forms. If you update these settings on the FIWP form, they will also update the corresponding settings on the Student Finance parameter forms, as follows:

• e-Commerce Implemented. This setting can also be maintained on the Student Finance Payment Parameters (SFPP) form.
• Web Cashier. This setting can also be maintained on the Student Finance e-Commerce Parameters (SFEP) form.
• Payments by Term. This setting can also be maintained on the Student Finance Payment Parameters (SFPP) form.
• Accept Partial Payments. This setting can also be maintained on the Student Finance Payment Parameters (SFPP) form.

• Process ID: WAP006

FLWP – FA My Loans Web Parameters

• Use the FA My Loans Web Parameters (FLWP) form to set up and maintain the institutional parameters for the Loan Application and optional Loan Change workflows. On this form, you can set up subsidized and unsubsidized loan parameters, enter the minimum amount for which a student can apply, and whether you allow negative unmet need borrowing. You can also set up whether a student can change the total of his/her loan amount, prevent students from changing a loan amount if the award is accepted, and set up communication codes to assign when a student applies for a loan or changes a loan amount.
• Proper setup of the parameters on the FLWP form is required to successfully run the Loan Application and Loan Change workflows.
• Process ID: WAP015

GAWP – Grad Appl Web Parameters

• Use the Grad Appl Web Parameters (GAWP) form to set up and maintain parameters for graduation applications that students submit through WebAdvisor or Colleague Self-Service.
• Process ID: WAP011

GRWP – Grading Web Parameters

• Use the Grading Web Parameters (GRWP) form to define the ways your faculty members and students are able to view or enter grades online.
• Process ID: WAP003

HLKM – Hyperlink Control Maintenance

• CAUTION: Changes made on the Web Form editor > Overview in Colleague Studio will overwrite changes made on this form. If you make changes to a particular hyperlink on this form, do NOT make changes in the Web Form editor.
• Use the Hyperlink Control Maintenance (HLKM) form to specify institution-specific parameters for hyperlinks defined by Ellucian.
• Hyperlink parameters can be specified on the Web Form editor > Overview as well as on this form. The Web Form editor is intended to be used for creation and maintenance of custom hyperlinks. The HLKM form modifies only the runtime parameters of a hyperlink, not the definition of the hyperlink.
• Process ID: UTHLK

LOGN – Edit Login Paragraph

• Process ID: UTS020

MCWP – Make A Contribution Web Param

• Use the Make a Contribution Web Param (MCWP) form to set up the processing of gifts, pledges, and pledge payments. Also, use this form to set up matching duplicate parameters, which help to prevent duplicate records from being created in Colleague.
• The parameters you define on the MCWP form affect all the Advancement WebAdvisor workflows. In addition you must also set up parameters for each of the different Advancement workflows using additional forms that you can access from the MCWP form.
• Process ID: WCAS03

MDWP – My Documents Web Parameters

• Use the My Documents Web Parameters (MDWP) screen to specify the display and sort parameters for the My Documents workflow in WebAdvisor. You can specify:

• whether or not to display the instance appended to the document description
• the primary and secondary sort options by which document information will be sorted in ascending order
• text you want substituted for blank fields in the Status or Due Date columns.

• Process ID: WBCOP02

MGWP – Make A Gift Web Parameters

• Use the Make a Gift Web Parameters (MGWP) form to set up the processing of gifts submitted through the Make a Gift WebAdvisor workflow, and to set up the processing of the gifts once they've been received.
• Process ID: WCAS09

MPWP – Make A Pledge Web Parameters

• Use the Make a Pledge Web Parameters (MPWP) form to set up the processing of pledges submitted through the Make a Pledge web workflow, and to set up the processing of the pledges once they've been received.
• Process ID: WCAS07

MTXT – Miscellaneous Text

• Use the Miscellaneous Text (MTXT) form to create miscellaneous text records, which you can use with following Colleague interfaces:

• WebAdvisor
• UI
• Workflow Management System (WfMS)
• Self-Service

• For WebAdvisor, the text entered on this form is rendered on a WebAdvisor page according to an XSLT stylesheet, either the default XSLT stylesheet (part of the WebAdvisor theme) or an override defined on the Process Control Template Data (SMD3) form. Use text entered on this form to replace any custom text from an HTML template that was used to render WebAdvisor forms prior to WebAdvisor 3.0. This text is linked to a WebAdvisor page using the SMD3 form.
• For UI, you can create a hyperlink definition to a miscellaneous text record and place that hyperlink definition on a menu. To create a hyperlink to a miscellaneous text record, use the following format: ?TYPE=P&PID=UT-UTMISC&TEXT=misc_textID, where misc_textID is the ID of the miscellaneous text record you want to use (hyperlinks are created using the Hyperlink Global Parameters [HGP] form or the Hyperlink Control Maintenance [HLKM] form). The hyperlink will open in a new WebAdvisor session in a browser window.
• For WfMS, you can display miscellaneous text records as part of a workflow (perhaps to let the user know that they have completed the workflow) or you can include this form in a WfMS workflow.
• For Self-Service, you can define a miscellaneous text record to display at the top of individual Self-Service pages by entering the ID on the page in the Self-Service sitemap. If you define a miscellaneous text record and enter the ID on a menu or submenu in the Self-Service Sitemap, the text is displayed on all subordinate pages of the menu or submenu, unless overridden by a subordinate submenu or page.
• Text entered on this form is stored in the MISC.TEXT file.
• Process ID: UTMTXT

MYWP – Make a Pledge Payment Params

• Use the Make a Pledge Payment Params (MYWP) form to set up the processing of pledge payments submitted through the Make a Pledge Payment web workflow, and to set up the processing of the payments once they've been received.
• Process ID: WCAS08

PLWP – Payment Plan Web Parameters

• Use the Payment Plan Web Parameters (PLWP) form to set up the processing of web payments for existing payment plans as follows:

• Define an optional office code that can limit the payment methods available to the user when paying on a payment plan.
• Define whether users can make partial payments on a scheduled payment.
• Access the Web GL Distributions (WDST) form to define the general ledger distributions that Colleague uses to process web payments.

• Note: These parameters are only applicable if web users are allowed to make payments.
• Process ID: ARP020

PMTH – Payment Methods

• Use the Payment Methods (PMTH) form to define each type of payment accepted by your institution. For example, your cashiers may accept cash, checks, money orders, Visa, MasterCard, American Express, etc. Additionally, your advancement office may accept non-monetary types of payments such as stocks and securities, real property, contributed services, etc.
• For each payment method, you must assign a payment category. The category you assign determines how Colleague processes a particular payment method. For example, if you define your e-check payment method with "Check" as the category, when recording an e-check payment, Colleague will prompt for certain information required to process an e-check payment (for example, routing number, account number, check number, etc.).
• You can also assign the bank code to which the payment will be deposited, as well as the general ledger account number needed to post the payment in Colleague Finance.
• If a payment method is restricted for use to a particular department, you can list individual office codes authorized to use that payment method. For example, your advancement office may accept stocks and bonds as methods of payments, but your cashier's office may not.
• You must indicate for each payment method whether or not it can be used for Web payments, and if so, it must also be enabled for e-commerce processing.
• Process ID: EBP004

PPWP – Physical Plant Web Parameters

• Use the Physical Plant Web Parameters (PPWP) screen to specify parameters for WebAdvisor workflows in the Colleague Physical Plant application.
• These parameters ensure that work orders created through WebAdvisor will have a default Work Order Type and Plant Type. In addition, you can define how the Request Work Order for Maintenance and Repairs workflow handles confirmation e-mails.
• Process ID: PPP006

PRAP – Proxy Access Permissions

• Use the Proxy Access Permissions (PRAP) form to define the proxy access permissions that a user can grant to a proxy. Permissions can be granted to individual pages or workflows, which are organized into proxy access groups. A proxy access group includes similar pages and workflows. For example, there are proxy access groups for Student Finance, Student Planning, Financial Aid, etc.
• For each proxy access group, you define to which pages and workflows a user can grant proxy permission. For example, for a selected proxy access group you can allow your users to grant proxy permission to all pages, to only certain pages, or to none.
• Note: When you update any parameter on this form, Ellucian recommends that you recycle the IIS application pool for Colleague Web API and clear the cache for Colleague Self-Service for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools.
• Process ID: PRXP002

PREP – Proxy Email Parameters

• Use the Proxy Email Parameters (PREP) form to define and maintain the ability to send emails to proxies, and to receive emails from or about proxies. The PREP form allows you to define the following types of email information:

• Name/address hierarchy used to determine the email type used for proxy communications.
• Email addresses used to send emails to proxies, and to receive emails from or about proxies.
• Document codes and paragraphs used in emails sent when proxy access is granted or changed.
• Document codes and paragraphs used in emails sent when proxy reauthorization is required.
• Document codes and paragraphs used in emails sent when duplicate proxy candidates need to be resolved.

• Note: When you update any parameter on this form, Ellucian recommends that you recycle the IIS application pool for Colleague Web API and clear the cache for Colleague Self-Service for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools.
• Process ID: PRXP006

PRXP – Proxy Parameters

• Use the Proxy Parameters (PRXP) form to define and maintain proxy functionality. The PRXP form allows you to define the following types of information:

• Enable proxy functionality. You can determine whether your institution allows users to assign proxy access.
• Proxy access permissions. If you enable proxy access, this information is used to enable or disable proxy access to Self-Service pages and workflows. Access the Proxy Access Permissions (PRXD) form from the PRXP form to define proxy access.
• Addition of new users. You can determine whether users can grant proxy access to persons with whom they do not have an existing relationship defined in Colleague.
• Proxy demographic requirements. If you allow the addition of new users, this information is used when adding a new proxy that does not currently have a relationship with the user in Colleague. Access the Proxy Demographic Requirements (PRXD) form from the PRXP form to define the demographic information required to add a new proxy.
• Proxy email parameters. You can define information that is used to send emails to proxies, and to receive emails from or about proxies. Access the Proxy Email Parameters (PREP) form from the PRXP form to define information used for proxy email processing.
• Proxy login settings. You can override web login settings when logins are created for new proxies.
• Display Text. You can display institution-specific information to the user when proxy access is granted or changed, or when reauthorization is required for continuing proxy access.
• Relationship types. You can use relationships to limit the persons available as proxies.

• Note: When you update any parameter on this form, Ellucian recommends that you recycle the IIS application pool for Colleague Web API and clear the cache for Colleague Self-Service for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling IIS application pool and clearing the cache.
• Process ID: PRXP001

PSCP – Site Create Parameters

• Use the Portal Site Create Parameters (PSCP) form to specify portal-wide parameters for site creation.
• Ellucian provides default values for all parameters on this form. The default will be used unless you enter a value in the adjacent parameter field.
• Process ID: RDP007

PUWP – Purchasing Web Parameters

• Use the Purchasing Web Parameters (PUWP) form to define parameters for requisitions and purchase orders created or displayed through WebAdvisor. These parameter settings do not affect how requisitions and purchase orders are created, maintained, or displayed in Colleague. The PUWP form serves two purposes:

1. To specify default information for each requisition and purchase order created through WebAdvisor.
2. To define selection criteria for displaying requisitions and purchase orders in WebAdvisor.

• The PUWP form is divided into three parts:

• Parameters that apply to both requisitions and purchase orders created in WebAdvisor.
• Parameters that apply only to requisitions in WebAdvisor.
• Parameters that apply only to purchase orders in WebAdvisor.

• All of the fields on the PUWP form are optional.
• Process ID: PUP002

RCWP – Receiving Web Parameters

• Use the Receiving Web Parameters (RCWP) form to define the following parameters for receiving through WebAdvisor:

• The functionality of the Accept All field.
• Whether or not clients must indicate that an MSDS sheet is received with specific items.
• The threshold for fixed asset items.

• Also, use the RCWP form to define a list of e-mail addresses to receive notifications in the following situations:

• When an item is accepted through WebAdvisor.
• When an item is reordered or voided through WebAdvisor.
• When an item is rejected or returned through WebAdvisor.

• These parameter settings do not affect how goods and services are received in Colleague.
• Process ID: WBCFP002

RGWP – Registration Web Parameters

• Use the Registration Web Parameters (RGWP) form to set up and maintain parameters related to registration and registration statements for online processing.

• Note: If you modify the LOCATIONS file or the ACAD.LEVELS file, you must access this form and save to have these changes take effect and be available to online users when they search for sections.
• Process ID: WAP005

RIWP – Request Information Web Param

• Use the Request Information Web Param (RIWP) screen to specify which Colleague codes and descriptions display in the WebAdvisor Request Information workflow.
• Because the code descriptions display on the Request Information forms in WebAdvisor, you can modify academic program, student type, and communication management code descriptions using this screen. If you change a code's description then the change only applies to the Request Information workflow in WebAdvisor.
• In order to use this screen, you must have created the following:

• Term codes using the Reporting Years and Terms (RYAT) screen
• Institution codes using the Institutions (INST) screen
• Communication codes using the Communication Codes (CMC) screen

• In addition, you can create new academic program and student type codes using this screen. If you have already created these codes using the Academic Program (PROG) or Student Type Codes (STTC) screen, then you can add existing codes.
• Process ID: WAP019

RPWP – Reset Password Web Params

• Use the Reset Password Web Params (RPWP) form to specify parameters for the Reset My Password workflow in WebAdvisor.
• Process ID: WBCOF004

SACC – SAML Assertion Cloud Configuration

• The SAML Assertion Cloud Configuration (SACC) form is used to maintain the configuration used by Colleague to access the Ellucian SAML Assertion Cloud Service. That cloud service produces SAML security tokens that allow web applications to authenticate themselves to third-party web sites, providing Single-Sign-On capabilities from web applications (like WebAdvisor) to third-party web sites.
• Process ID: UTS164

SDD – Device Definition

• Use the Device Definition (SDD) screen to identify the terminals, printers, and other devices used for all Envision-based applications on your system. Currently, this screen lets you identify only terminal devices (displays and keyboards). Because all applications share the DEVICES file, you only need to have one device record for your system, regardless of the number of Envision-based applications.
• On this screen, you can specify the following device characteristics:

• Device-level password
• Keyboard definition
• Display definition
• Default security classes for the device

• Computer Access Strategies
• Access to most computer systems follows one of two strategies:

• switch-based system
• port-based system

• A switch-based computer system has an external switching computer or an external network computer that assigns the first available port to an end user trying to access the computer. Usually, the end user logs on to a different port for each session. For these systems, Envision assigns devices according to the end user's operating system login ID to ensure that the end user always has the same device definition, regardless of the port assigned by the switch.
• On a port-based computer system, end users get the same port from the same device every time they log on, regardless of their login IDs. On port-based systems, Envision assigns devices according to the port number of the device, as specified on the Network Definition (SND) screen. This ensures that the Envision display and keyboard tables are compatible with the hardware associated with the device.
• Assigning Devices on a Switch-based System
• Device IDs for a switch-based system correspond to end users' login IDs--one device record for each end user. Each end user can have distinct passwords, keyboard tables, and display tables. An end user has the same device definition regardless of the port assigned by the switch.
• Assigning Devices on a Port-based System
• The device ID for a port-based device relates to the type of device attached to the port and any special characteristics of its location. For example, to define a device record for a generic Wyse 50 terminal, use WYSE50 as the device ID. Define only one device record for generic terminal types. These device definitions can be shared among several ports. If you want to add additional security to a specific terminal on a specific port, define a separate device record for that terminal (for example, SYSADM).
• Combining Features of Switch-Based and Port-Based Systems
• If your computer is a switch-based system with certain ports hard-wired, you can combine the features of both device assignment methods. The port-definition window on the Network Definition (SND) screen lets you assign a hard port for a switch-based system. You can assign the hard-wired ports on your computer to specific device definitions that are active for any end user logging into that port. For that port alone, Envision assigns device characteristics just as it would if the whole system were port-based.
• Device Security
• You can assign process-level security--in the form of security classes--to each device. Assign security classes to device records only for port-based devices. You can then secure specific terminals from running certain processes, regardless of the operator. If you are using switch-based devices, assign security classes to each individual end user instead of to a terminal. Remember that all applications share the same device definitions, so if you assign a security class to a device, you must define it in all applications using that device. Use the Security Class Definition (SCD) screen to define security classes.
• Note: For switch-based devices, the system ignores the security classes defined in the device record.
• When you make changes to an end user's device definition, that end user must log out and log back into the system before the changes take effect.
• Process ID: UTDEVS

SEMS – System Email Settings

• Use the System Email Settings (SEMS) form to define parameters for Envision E-Mail. From this form, you can define the method by which Envision will send all outgoing e-mail. After selecting an e-mail type, you can then specify information about the computer on which the mail server resides. The e-mail service type you select determines which remaining fields you may populate.

• If you select UNIX, you can define the default e-mail handler.
• If you select Java, you can define the SMTP mail host, port (optional), domain name, authentication login, authentication password, and secure method (optional). It is recommended to specify a secure method.

• Process ID: UTF033

SFEP – Student Finance e-Commerce Parameters

• Use the Student Finance e-Commerce Parameters (SFEP) form to define parameters for payments that are processed on the Student Finance Make a Payment view.
• The parameters on the SFEP form define the following:

• Whether payment methods available to students are restricted by office codes.
• The text displayed on the Review Payment Selection view.
• The cashier used for self-service payments.
• The content of the acknowledgement notice displayed on the payment acknowledgement view and sent through email after the self-service user processes a successful payment. You can also specify the person or office at your institution that receives a copy of that email.
• The merchant information displayed on the payment acknowledgement view and sent through email after the self-service user processes a successful payment.

• When you access the SFEP form for the first time, the Web Cashier field is populated with the web cashier currently defined on the Financial Web Parameters (FIWP) form. Any change that you make to the web cashier on the SFEP form will also update web cashier on the FIWP form, and vice versa.
• Process ID: SFP002

SFPP – Student Finance Payment Parameters

• Use the Student Finance Payment Parameters (SFPP) form to define parameters for payments processed on the Student Finance Make a Payment view.
• The parameters on the SFPP form define the following:

• Whether web payments and cashier payments recorded in Colleague will be processed through Colleague e-Commerce.
• Whether students are allowed to make payments on the Make a Payment view.
• Whether term or non-term payments are created.
• Whether students can make partial payments on accounts, payment plans, and deposits due.
• The types of receivables that will be displayed, and whether students can make payments on them.

• When you access the SFPP form for the first time, the fields are populated with any corresponding values currently defined on the Financial Web Parameters (FIWP) form and the Payment Plan Web Parameters (PLWP) form. With the exception of the Self-Service Payments Enabled and the Partial Payments on Deposits Allowed fields (which apply to Student Finance Views only), any changes that you make to the parameters on the SFPP form will also update the corresponding parameters on the other parameter forms, and vice versa.
• Note: When you update certain parameters on the SFPP form, Ellucian recommends that you recycle the IIS application pool for Colleague Student Self-Service in order for your modified settings to take effect immediately. Otherwise, your modified settings will take effect after twenty minutes of inactivity. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pool.
• Process ID: SFP001

SFSP – Student Finance Statement Parameters

• Use the Student Finance Statement Parameters (SFSP) form to define and maintain parameters for your Student Finance Self-Service statements. These parameters determine the types of information included on the statement in addition to how your institution information is displayed on the statement.
• Note: When you update any parameter on the SFSP form, Ellucian recommends that you recycle the IIS application pools for Colleague Web API and Colleague Student Self-Service in order for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools.
• Process ID: SFP003

SFTP – SFTP Configuration

• Use the SFTP Configuration (SFTP) form to define and configure SFTP connections. The records created by this form can be used with the UT subroutine S.EXECUTE.FTP to send SFTP requests.
• Note: Either password or private key file authentication must be defined when using the SFTP form. You must define at least one but not both methods of authentication.
• Process ID: UTS163

SMD – Menu Definition

• Overview - Use the Menu Definition (SMD) form to customize existing menus and to create new ones. You can add any process to any menu, as long as the process and the menu are both in the same application. The same processes can appear on more than one menu. You may also delete any process from any menu.

NOTE: You should not modify the standard menus that are provided with your Ellucian software, because they may be overwritten with future releases. To included Ellucian processes on a menu, either create your own menus and add Ellucian processes to them, or use security classes to restrict the processes to which a group of users has access.

• Defining a New Menu

When you define a new menu, you must first select a mnemonic for the menu. This mnemonic is the same mnemonic that end users enter to access the menu. To prevent your new menu from being overwritten during a subsequent release of the software, the letter "X" should be the first letter of your mnemonic. Ellucian guarantees that a menu or process mnemonic shipped with a general release will never begin with the letter "X."

When you decide on the mnemonic, enter it at the LookUp prompt on the SMD form, then give the menu a title. Finally, specify the processes that should appear on the menu.

After creating a new menu, you should add its mnemonic to another menu using the SMD form. Remember that end users can enter any mnemonic from any menu provided they have the appropriate security rights.

• Adding a Process to a Menu

To add a process to an existing menu, enter the mnemonic for the menu at the LookUp prompt on the SMD form. To add an existing process, enter it in the window in field 3. To add a new process, position the cursor in the window in field 3 and press DETAIL to access the Process Control Maintenance (SMD2) form. Enter the new process on the SMD2 form rather than entering it from the SMD form.

• Removing a Process from a Menu

To keep a process from displaying on a menu, you should restrict its use through the Security Class Definition (SCD) form rather than deleting it through the SMD form.

Ellucian recommends that you change the default menu setup only after a great deal of planning. You should leave the original setup intact and create new menus that reflect any changes. By defining a new menu containing your changes, you preserve its contents from one release to another.

If you need to remove a process from a menu, enter the mnemonic for the menu at the LookUp prompt on the SMD form. At the window in field 3, position the cursor on the item that you want to delete and press DEL twice.

Adding a Custom Program to a Menu

• To add a custom program to a menu, follow the steps below:

• Decide on a mnemonic for your custom program. Remember to begin your mnemonic with the letter "X" to prevent it from being overwritten with a future software release.
• Using the editor, create a paragraph VOC entry named mnemonic for your custom program, as follows:

                                                             001:  PA

                                                             002:  RESET.TERM

                                                             003:  CUSTOM.PROGRAM.NAME

• Line three of the entry should be the name of your custom program. The RESET.TERM command makes sure that your cursor and backspace keys work properly.
• Use the SMD form to add your custom program mnemonic's VOC entry to a menu as a database management system query language statement (type I).

• Process ID: UTMENU

SND – Network Definition

• Use the Network Definition (SND) screen to assign a device ID to the appropriate port. Device IDs are defined on the Device Definition (SDD) screen. The device ID identifies the terminal and keyboard type used for the port, any special security class (es) authorizing access to the system, an optional password associated with the device, and notes about the location(s) of the device.
• Identifying the terminal and keyboard type is critical to properly defining function keys and ensuring accurate screen display. Therefore, each device ID must be correctly defined for the corresponding port. More than one port number can have the same device ID, and all information about the device applies to each port number with that device ID. To assign each device to its correct port, you need a listing or diagram of your setup.
• NOTE: Use this process only with host systems that are port-dependent or host systems that run on a network.
• Process ID: UTNET

SPLP – Student Finance Payment Plan Parameters

• Use the Student Finance Payment Plan Parameters (SPLP) form to define and maintain global Student Finance Payment Plan parameters. The SPLP form provides access to term-specific payment plan requirements.
• To implement Student Finance Payment Plans, you must have already implemented the following:

• Colleague Self-Service: Student Finance
• Colleague e-Commerce
• Colleague Communications Management

• To define payment plan options for your billing terms, access the Student Finance Pay Plan Requirement Definition (SPLD) form from the Req Def field on this form. If you do not define payment plan options for a billing term, AR account holders will not be able to sign up for payment plans for that billing term.
• Note: When you update any parameter on this form, Ellucian recommends that you recycle the IIS application pool for Colleague Web API and clear the cache for Colleague Self-Service for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools and clearing your cache.
• Process ID: SFP011

STFP – Student Finance Parameters

• Use the Student Finance Parameters (STFP) form to determine how information is displayed on the Student Finance Make a Payment and Account Activity views. You can choose to display information by term, or by past, current, and future time periods.
• When you display information by term, Colleague displays the information on the Student Finance Views as follows:

• Make a Payment. Displays student payment amounts due for each individual term, and lists the terms in chronological order (from oldest to newest term). Any payment amounts due that are not term-specific are listed in the other term.
• Account Activity. Displays account activity for the newest term, and provides a drop-down box where the user can select another term to view. Any account activity that is not term-specific is listed in the other term.

• When you display information by past, current, and future time periods, Colleague displays the information as follows:

• Make a Payment. Displays student payment amounts due for past, current, and future time periods. Colleague determines the start and end dates for the current period using the selected basis (term start date, reporting term start date, or current date plus or minus date offsets), and determines the past and future time periods accordingly.
• Account Activity. Displays account activity for the current time period, and provides a drop-down box where the user can select another time period to view. If the student has no current account activity, past or future activity (if any) is displayed.

• Note: If you display information using past, current, and future time periods, you should schedule the Student Finance Term Categorization (SFTC) process to run every day at midnight so that terms are classified correctly. Also, you should run the SFTC process manually if you update the parameters controlling how past, current, and future periods are determined so that terms get categorized immediately.
• The STFP form requires that you define whether credit amounts are displayed on the Make a Payment view as display-only amounts, meaning that they are not deducted from the Total Amount Due displayed at the bottom, but are reflected in the associated term or time period balances.
• You can also choose whether to display deposit balances on Student Finance Views by specifying the types of deposits to display, and the receivable types to which those deposit types would be applied.
• The STFP form provides the ability to define an optional message displayed to students at the top of the Student Finance views. You can also define the default administrative view that is displayed from the Student Finance Admin View (SFAV) form.
• Note: When you update any parameter on the STFP form except for the Admin View Landing Page, Ellucian recommends that you recycle the IIS application pools for Colleague Web API and Colleague Student Self-Service in order for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools.
• Process ID: WAP021

STWP – Student System Web Params

• The Student System Web Params (STWP) screen is the place where you can define business policies for allowing students to access and update information via the Web.
• Process ID: WAP001

SVBP – Servlet Behavior Parameters

• Use the Servlet Behavior Parameters (SVBP) form to enter additional information about a specific servlet. Entries on this form will override the respective entries on the WebServer Parameters (WSPM) form for the selected servlet only.
• Process ID: DMIS005

SVCA – Servlets Config Additional

• Use the Servlet Behavior Parameters (SVBP) form to enter additional information about a specific servlet. Entries on this form will override the respective entries on the WebServer Parameters (WSPM) form for the selected servlet only.
• Process ID: DMIS005

SVCF – Servlets Configuration

• Use the Servlets Configuration (SVCF) form to define configuration parameters for each servlet used with WebAdvisor for this environment.
• Process ID: DMIS003

SVDP – Servlet Display Parameters

• Use the Servlet Display Parameters (SVDP) form to define display parameters for each servlet used with WebAdvisor for this environment.
• Process ID: DMIS012

TRWP – Transcript Web Params

• Use the Transcript Web Parameters (TRWP) form to set up and maintain parameters for transcript requests that students submit online.
• Process ID: WAP00

WAFL – WebAdvisor User Account Forms and Links Config

• When SAML authentication is enabled for WebAdvisor (version 3.2.0 or above), user account management must be handled by the Identity Provider. Because of this, all WebAdvisor user account management forms and links must not be displayed. This form allows you to hide all Ellucian-delivered WebAdvisor user account forms and links.
• Note: if you have custom user account forms or links that need to be hidden, you must remove them manually.
• Process ID: UTS173

WAGM – WebAdvisor GC File Maint

• Use this form to manage the COMO files produced by the WebAdvisor garbage collection background processes.
• Process ID: UTS095

WAPP – Web Acad Program Parameters

• Use the Web Acad Program Parameters (WAPP) form to specify the parameters to be used for program evaluations. Applicants, students, and faculty advisors can perform academic program evaluations in WebAdvisor to assess a student's or applicant's progress toward meeting the requirements of a program.
• A program evaluation is available as an option in the following WebAdvisor workflows:

• My Advisees
• Student Educational Planning
• Plan Courses

• A program evaluation also runs automatically in the course planning wizard in the Smart Registration optional module.
• The "Show My Progress Print Text as Entered" flag only affects My Progress in Self-Service Student Planning.
• Process ID: WAP010

WEIP – Web Emergency Information Parameters

• Use the Web Emergency Information Parameters (WEIP) form to set up the information that can be viewed or is required on the Emergency Information page in Colleague Self-Service.
• Note: When you update any parameter on this form, Ellucian recommends that you recycle the IIS application pool for Colleague Web API and clear the cache for Colleague Self-Service for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools.
• Process ID: WCS021

WFPM – Web Form Parameter Maint

• Use the Web Form Parameter Maint (WFPM) form to specify alternate WebAdvisor rendering criteria. Alternate criteria includes additional hyperlinks, miscellaneous text, alternate text for action buttons, and alternate rows displayed for Envision tables. See help for each field for more information.
• Changes made on this form render in real-time in WebAdvisor. For example, if you change the value in the Alternate Title field, the new value is displayed to WebAdvisor users immediately upon saving from this form, with no downtime for the Web server.
• Data entered on this form is stored in the PRCS.CTL record for the selected WebAdvisor form or menu.
• Process ID: UTS090

WFST – Web Designation Setup

• When Web users enter a gift or pledge, they are asked to choose a designation from a drop-down list. Use the Web Designation Setup (WFST) form to define the designations that display on that drop-down list of options.
• Process ID: WCAS05

WPFP – Web Payment Frequency Setup

• Use the Web Payment Frequency Setup (WPFP) form to identify the payment frequencies you want associated with online pledges made through the "Make a Pledge" workflow. You must also define one of these payment frequencies to be the default payment frequency for WebAdvisor.
• The payment frequencies you specify on this form must already exist in the FREQUENCY.CODES validation code table as defined and maintained on the Validation Codes (VAL) form. When you specify these payment frequencies on the WPFP form, the Web payment frequencies are stored in the WEB.FREQUENCY.CODES validation code table. You can only maintain the WEB.FREQUENCY.CODES validation code table using the WPFP form.
• Your institution may have several payment frequencies (defined on the VAL form) to identify how often a web donor will make pledge payments.
• You may want to limit the number of payment frequencies that web donors can select when making pledges. When selecting your payment frequencies and defining the description to use in the "Make a Pledge" workflow, keep in mind that your web donors may not be familiar with your institution's terminology, so be as clear and descriptive as possible.
• The Web Payment Frequency Description field does not need to be the same as the description defined on the VAL form for the payment frequency code.
• Process ID: WCAS10

WSMS – Web Solicit Method Setup

• When web users enter a contribution, they are asked to choose a solicitation method from a drop-down list. Use the Web Solicit Method Setup (WSMS) form to define the solicitation methods that display on that drop-down list of options.
• Process ID: WCAS06

WSPD – Web Services Parameters

• Use the Web Services Parameters (WSPD) form to define and maintain parameters required by web services or applications that send inbound requests to Colleague, such as requests made by the Colleague Web API.
• Process ID: UTS155

WSPM – WebServer Parameters

• Use the Web Server Parameters (WSPM) form to set up environment-wide parameters for WebAdvisor. The data for these environment wide WebAdvisor parameters are stored in the WEBSERVER.PARMS record in the UT.PARMS file. This data is read by the WebAdvisor servlet when starting a WebAdvisor instance.
• The values entered on this form can be overridden for each WebAdvisor servlet individually using the Servlets Config Additional (SVCA) form.
• Process ID: DMIS006

WSRP – Web Search Parameters

• Use the Web Search Parameters (WSRP) screen to enter the values that will be shown in drop-down lists when the fields on this screen are displayed on Web forms. For example, if you don't want to allow selection of all subjects on the SUBJECTS file when a student is using subject to search, enter the list of subjects that you would like to show.
• Process ID: WAP008

WUIP – Web User ID and PIN Options

• Use this form to enter parameters that define the format of Web user IDs and PINs. These parameters are used when you assign user IDs and PINs to one person (on the DRUS form) or to a group of students, faculty, or other users (on the DMIS, DMIF, or DMIU forms).
• Since this is a parameter screen, any users who are logged in to this account will need to exit their current sessions and start a new session to be sure the new parameter settings have taken effect.
• Process ID: WCS012

WUPP – Web User Profile Parameters

• Use the Web User Profile Parameters (WUPP) form to set up the information that can be viewed on the User Profile page in Colleague Self-Service. You can use this form and additional forms accessible from the WUPP form to indicate which phone, email, and address types are available to the user for viewing and updating. The types specified will be applied to all users who access the Colleague Self-Service User Profile page. You can also specify a message to display to users to explain your institution's policies regarding personal information.
• Note: When you update any parameter on this form, Ellucian recommends that you recycle the IIS application pool for Colleague Web API and clear the cache for Colleague Self-Service for your modified settings to take effect immediately. Otherwise, your modified settings will take effect when your application pools are automatically recycled. Refer to the Self-Service Installation and Administration manual for information about recycling your IIS application pools.
• Process ID: WCS016

WUPR – Web User Password Requirements

• Use this form to define the password complexity requirements for Colleague Web Users. The requirements defined here are enforced when users change their passwords using the WebAdvisor Change Password form, or when the system administrator resets a user's password on the DMI Registry User Setup (DRUS) form. In addition, if the "PIN meets password requirements" option set to Yes on the Web User ID and PIN Options (WUIP) form, then a string will be appended to the generated PIN to ensure compliance with the requirements set on this form.
• When updating the password requirement, you should also update any error messages displayed to users if the password requirements are not met. Use the DMI Error Messages (ESSS) form to override the following errors:

• Error number 30062 - displayed when the password does not meet the length requirement.
• Error number 30069 - displayed when the content of the password violates any of the defined requirements.

• You may also use the DMI Errors form on SA Valet to override these errors.
• Important: After you have updated your password requirement setting, you must restart the application listener (or the listener with an APPS role that is dedicated to WebAdvisor) for the changes to take effect. Update the error messages (mentioned above) as soon as possible to reflect the requirement updates.
• Process ID: WCS015

XTREV – Tran Eval Web Parameters

• Use the XTREV screen to set up and maintain parameters for Tran Eval Request that students submit through WebAdvisor.
• Process ID: XWTR001