Posts

Showing posts with the label peoplecode

PeopleSoft - PeopleTools Configurations Records or Meta Tables

PeopleSoft - PeopleTools Configurations Records or Meta Tables PeopleSoft records/metadata tables, often referred to as "meta tables," store information about various PeopleSoft objects and configurations.  1. Object Definition Tables: PSRECDEFN : Contains definitions of records (tables) used in the application, including details like record type and description. PSDBFIELD : Stores field definitions, detailing the attributes of each field such as data type and length. PSPNLGROUP : Holds information about components, which are collections of pages that function together. PSPNLDEFN : Contains definitions of pages (interfaces) within the application. PSMENUDEFN : Stores menu definitions, organizing how components are presented to users. 2. Security Tables: PSOPRDEFN : Maintains user profile information, including user IDs and associated roles. PSROLEDEFN : Defines roles that group together permissions for easier security management. PSCLASSDEFN : Holds permission li...

PeopleSoft File Attachments : Converting User Filenames before uploading in the record or server

Converting User Filenames If a user attaches a file through the browser dialog box generated by the AddAttachment function, the filename may be converted before that filename is returned to the AddAttachment call for storage. For example, the file My Resume.doc is returned through the AddAttachment parameter as My_Resume.doc, with the space changed to an underscore. No comparable mapping occurs for user filenames with the PutAttachment function, which requires the user filename as an input parameter rather than an output parameter that is returned to the user. Instead, before storing the ATTACHUSERFILE value, you should invoke code similar to this: &ATTACHUSERFILE = Substitute(&ATTACHUSERFILE, " ", "_"); &ATTACHUSERFILE = Substitute(&ATTACHUSERFILE, ";", "_"); &ATTACHUSERFILE = Substitute(&ATTACHUSERFILE, "+", "_");

Peoplesoft : PeopleCode File Layout - Read and Write a file using File Layout

If your data is hierarchical in nature, or based on existing PeopleSoft records or pages, you want to use a File Layout definition for reading and writing your data, rather than doing it line by line (or field by field.) For example, suppose you wanted to write all the information from a record to a file. You can use the WriteRecord method to write all the data from the record, instead of having to loop through every field, find the value, and write it to the file. In addition, you could write all the information from a transaction (or several transactions) from a page to a file. Each transaction can be considered a  rowset . A rowset can contain more than one record and is generally composed in a hierarchical structure. You could create a File Layout definition that has the same structure as the page (or component), and use the WriteRowset method. If you have a file that contains data in the correct format, you can use the ReadRowset method to read the data from the file to the pa...

PeopleCode MessageBox function | Using PeopleCode MessageBox Features

A. The Basic Version The ‘MessageBox’ function is such a handy piece of code for troubleshooting that you often find yourself using the ‘basic version’ without giving much thought to how the statement really works: MessageBox(0, "", 0, 0, "Display message here"); This post will take a closer look at some of the additional features of ‘MessageBox’, beyond its basic usage above. In particular, we consider each of the parameters in more detail. B. Parameter 1: Message Type The first parameter specifies the type of message you wish to display. In most cases, the parameter is set to a value of ‘0’, which displays a message with an ‘OK’ button only. However, the function comes with a number of other options for setting the message type. These can be entered as either a numeric value (‘0’) or a constant (‘%MsgStyle_OK’): 0 – %MsgStyle_OK 1 – %MsgStyle_OKCancel 2 – %MsgStyle_AbortRetryIgnore 3 – %MsgStyle_YesNoCancel 4 – %MsgStyle_YesNo 5 – %MsgStyle_RetryCancel This means ...