Format: Queries are to be named using the following format:
XXH_YYYY
XX represents the two-character department code.
H represents the UW-Platteville system assigned code. The third character must be H.
YYYY represents the name of the query.
Examples: The following are examples of valid query names.
ADH_LETTERCOUNT - AD indicates this is an Admissions query
SRH_ATHLETES - SR indicates this is a Student Records query
SFH_AUDIT_STUDENTS - SF indicates this is Student Financials query
FAH_IOWA_Il_STATES - FA indicates this is a Financial Aid query
DLH_ACAD_PLAN - DL indicates this is a Distance Learning query
Process/Report Names:
SQR/App Engine Processes or Reports – Send an email to PeopleSoft Tools Admin for a name from the report tracker.
Fields:
H_fieldname
ex: H_MYFIELD
This is the same if used in run control or other record
Records:
If the record is a data table or view, it will look like this:
Table - {area code}_H_{tablename}_TBL ex: tx_h_book _tbl
View - {area code}_H_{tablename}_VW ex: tx_h_book_vw
Search record - {area code}_ H_{tablename}_srch ex: tx_h_book_srch
Work record - {area code}_H_{tablename}_WRK ex: ad _h_recruit_wrk
Temp record - {area code}_ H_{tablename}_TMP ex: tx_h_book_tmp
Common Attribute Framework - {area code}_H_{tablename}_CAF ex: FAC_H_CHAR_CAF
Query View - {area code}_H_{tablename}_VW ex: pac_h_
If the record is a run control record, it will follow this form:
RUN_H_{area}_CUST[number]
ex: RUN_H_TX_CUST or RUN_H_TX_CUST2
Pages:
For application pages, name the pages as follows:
Classic Pages: {area}_H_{panel name}_PNL ex: TX_H_ADDBOOK_PNL (Note the descriptive name!)
Fluid Pages: {area}_H_{panel name}_PFL ex: TX_H_ADDBOOK_PFL
For run control pages, it includes the process name:
RUN_{process name}_ PNL ex: RUN_TXH501_PNL
Components:
Use the same name as the page, just add a 'G' to the end. So, to use the previous pages, you will get
Classic: TX_H_ADDBOOK_PNLG and RUN_TXH501_PNLG
Fluid: TX_H_BK_INFO_PGFL
Component Interfaces:
{area}_H_{descriptive name}
Menus:
H_{area code}_MENU
Folder:
Top Level:
UWP_{area code}_(Descriptive name)
Internal Folder:
UWP_{area_code}_USE, SETUP, INQUIRE, PROCESS, REPORT
Integration Broker Objects:
Service Node: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text (ex: H_HGH_XXXX)
Service Name: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text (ex: H_HGH_XXXXXXXX)
Service Operation: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text (ex: H_HGH_XXX_XXXXXXX_SO)
Service Operation Handler: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text and end with _HDL (ex: H_HGH_XXXXXX_HDL)
Routing: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text and end with _RTG (ex: H_HGH_XXXX_RTG)
Message Name: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text and end with _MSG (ex: H_HGH_XXXXX_MSG)
URL ID: Start with H_ followed by a three digit area code followed by an underscore and concise descriptive text and end with _URL (ex: H_HGH_XXXX_URL)
Note: Do not start IB object names with XML, xml, digits or characters
Jobs:
Start with “UWP_” followed by an appropriate name (Ex: UWP_XXXX where XXXX is anything appropriate and represents something related to the job being ran)
Longest possible length is 8 characters long string.
JobSets:
Start with “UWP_” followed by two to three characters representing the area followed by the letter H followed by _appropriate name for the job (Ex: UWP_XXXH_COMGEN where XXX is the two or three letter functional area code).
Sql Objects:
Name the sql objects as follows:
{area}_H_{descriptive name}_SQL. Ex: HG_H_RATE_UPDATE_SQL
Application Packages:
H_{area}_{descriptive name}
Application classes should also have names.
File Layouts:
{area}_H_{descriptive name}
Activity Guides:
Templates: {area}H_{descriptive name}
Action Item: {area}H_{descriptive name} {area}_H_{descriptive name}
Page Definition: {area}H_{descriptive name} or {career}_{descriptive name}
Related Content:
Service ID: H_{descriptive name}
Security:
Roles: UWP_{area}_{descriptive name}
Permission List: UWP_{area}_NNNN{component action A:Add, U:Update, L:Update/Display All, C:Correction}
Message Catalog Entries:
Our Custom Message Set should be greater than 24000, preferable 24200-24300
Message Set Number - Area
24200 - AD
24201 – DL
24204 – CC
24205, 25000 – SR
24211 – OT
24213 – UMIS
24214 – SF
24215 – SSWD
24216 – HG
24217 – NSR
24218 -- HPT
25205 – IR
Other
29001 – CAF Validation Error Messages
Object Owner:
For any UWP objects, the "Object ID" should be set to UWP SA Bolton or the code SUWP.