This page has moved. Please update your links:This is a continuation of the following posts:
Now, we need to write some code to use the Component Interface. Let’s use the Application Engine program from this step by step post.
This page has moved. Please update your links:This is part one of a multi-part series exploring some quirks in using Component Interfaces with Application Engine programs. If nothing else, hopefully, these will give new developers some insight into how to use a Component Interface. My goal is to expose a bug in the Application Engine tool that maybe Oracle will see and fix.
This first part will simply walk you through creating a Component Interface. This part is just a map to associate the fields on the screen (or really in the component’s buffer) with an API property that can be accessed with code.
First, we create a new definition in Application Designer. You can either use the Ctrl + N keyboard shortcut or the File > New menu. Choose Component Interface from the list:
Next, have no fear — you will see the open dialog making it look like you want to open a component. Really, Application Designer is just asking you which component you want to map. In this example, we will use the “PERSONAL_DATA” component, which is the Modify a Person screen (Workforce Administration > Personal Information > Modify a Person):
Next, Application Designer asks you if you want to default the properties. I almost always say yes to this questions because it will make Application Designer do all the work for you in generating the map. The properties will be given names based on their field names in the buffer:
Now, you should have a new component interface generated for you. Notice that the left side is the Component Structure. It is the same as the Structure tab on the Component itself. The right side is the map of record/field to property name. In this screenshot, I have the component open in the background and I drew a line to show how the structure is the same. Then, I drew a line from the structure to the property generated for one of the fields:
Finally, save the component interface. You can either use the Ctrl + S keyboard shortcut, or you can use the File > Save menu. I gave it the name BLG_PERS_DTA_CI.
While your at it, you may also want to add it to the project. You can use the F7 keyboard shortcut or the Insert > Current Definition Into Project menu.
This concludes creating the Component Interface. Please stay tuned for the next steps …
This page has moved. Please update your links:This post is to address a question posed in one of the comments on another post. The answer is a little too in-depth for a comment reply. Also, I had been wanting to blog more about arrays anyway.
Here is the question:
Hi i have seen your comment on Arrays.
i need your guidence on creating array and using it in Peoplecode App package.
I have some logic written in SQR. Same thing i want create in App Package which can be used.
Let me brief you my requirement.
i have several parameters to be stored in an array which i will get from different validations and SQL tables for employees.which i will store it in a array. After finishing validations for all the employees i have pass those employee id and details some other system so i want to replicate in App package using Array can you guide me how i can design it in App package.
I also decided to use my step-by-step that I just completed. So, this answer will build on that post.
Listening to the requirements, I don’t think that we need to extend the array object like the post that this comment was on. At most, I think we might want to create an employee object that will store all of the fields (or parameters as the requirements call them) needed.
So, I am creating a new Application Package called BLG_BLOGGING. Then, I am inserting a new Application Class called “EmployeeObject”:
Then, I created three properties in that class to hold three parameters relating to an employee. I did not specify the “get” or “set” keywords so I don’t have to create getter and setter methods. This is the easiest way to add properties to a class because you don’t have to write any code for the properties. Here is the code:
class EmployeeObject property string EmployeeID; property string FirstName; property string LastName; end-class;
Then, in the Application Engine program, you have to import your new class. This statement does nothing more than tell the program you are going to use this class later on.
import BLG_BLOGGING:EmployeeObject;
Here are the different variables that we will need.
Local File &log; Local BLG_BLOGGING:EmployeeObject &emp; Local array of BLG_BLOGGING:EmployeeObject &ary; Local number &x;
This code creates an empty array. We need to pass it a copy of the employee object just so it knows what data type will be stored in the array. It will not actually store anything in the array at this point.
&emp = create BLG_BLOGGING:EmployeeObject(); &ary = CreateArrayRept(&emp, 0);
Here is where we load the first employee into the array. We set all of the properties, and then, we use the push() method to insert it into the array.
&emp.EmployeeID = "001";
&emp.FirstName = "Bob";
&emp.LastName = "Tomato";
&ary.Push(&emp);
&log.WriteLine("Added Bob Tomato -- length = " | &ary.Len);
Then, we repeat that with another employee.
&emp = create BLG_BLOGGING:EmployeeObject();
&emp.EmployeeID = "002";
&emp.FirstName = "Larry";
&emp.LastName = "Cucumber";
&ary.Push(&emp);
&log.WriteLine("Added Larry Cucumber -- length = " | &ary.Len);
Finally, we add a third employee just to give us some data.
&emp = create BLG_BLOGGING:EmployeeObject();
&emp.EmployeeID = "003";
&emp.FirstName = "Lunt";
&emp.LastName = "Squash";
&ary.Push(&emp);
&log.WriteLine("Added Lunt Squash -- length = " | &ary.Len);
Then, we need to loop through the array to show what it contains. The Get() method accesses one of the elements in the array. It does not remove the element from the array.
&log.WriteLine("");
&log.WriteLine("Employees: ");
For &x = 1 To &ary.Len
&emp = &ary.Get(&x);
&log.WriteLine(" " | &emp.EmployeeID | ") " | &emp.LastName | ", " | &emp.FirstName);
End-For;
Here is the Application Package, Employee Object:
class EmployeeObject property string EmployeeID; property string FirstName; property string LastName; end-class;
Here is the App Engine Program:
import BLG_BLOGGING:EmployeeObject;
Local File &log;
Local BLG_BLOGGING:EmployeeObject &emp;
Local array of BLG_BLOGGING:EmployeeObject &ary;
Local number &x;
&log = GetFile("c:\temp\log.txt", "W", "A", %FilePath_Absolute);
&emp = create BLG_BLOGGING:EmployeeObject();
&ary = CreateArrayRept(&emp, 0);
&emp.EmployeeID = "001";
&emp.FirstName = "Bob";
&emp.LastName = "Tomato";
&ary.Push(&emp);
&log.WriteLine("Added Bob Tomato -- length = " | &ary.Len);
&emp = create BLG_BLOGGING:EmployeeObject();
&emp.EmployeeID = "002";
&emp.FirstName = "Larry";
&emp.LastName = "Cucumber";
&ary.Push(&emp);
&log.WriteLine("Added Larry Cucumber -- length = " | &ary.Len);
&emp = create BLG_BLOGGING:EmployeeObject();
&emp.EmployeeID = "003";
&emp.FirstName = "Lunt";
&emp.LastName = "Squash";
&ary.Push(&emp);
&log.WriteLine("Added Lunt Squash -- length = " | &ary.Len);
&log.WriteLine("");
&log.WriteLine("Employees: ");
For &x = 1 To &ary.Len
&emp = &ary.Get(&x);
&log.WriteLine(" " | &emp.EmployeeID | ") " | &emp.LastName | ", " | &emp.FirstName);
End-For;
&log.Close();
Here is the final output:
Added Bob Tomato -- length = 1 Added Larry Cucumber -- length = 2 Added Lunt Squash -- length = 3 Employees: 001) Tomato, Bob 002) Cucumber, Larry 003) Squash, Lunt
This page has moved. Please update your links:This is a how-to post that I intend to refer back to from time to time. The goal is to create a simple Application Engine program into which we can drop some PeopleCode and see how it works. Assuming we don’t need any of the online pieces, this is much easier than going through all of the steps to create a page and register it so we can see it online.
In Application Designer, click Ctrl + N or use the File > New menu option. This will open the “New” dialog, and you can choose Application Engine program from the list.
You new program should look like this:
This step is very important. If you don’t disable the restart and your program crashes, you will have to go through a few extra steps before you can rerun it.
First, click on the properties button while your program is in focus (you can also use the File > Definition Properties menu):
This should bring up the Properties dialog. Then, go to the Advanced tab. Check the “Disable Restart” option.
First, click on the “Step 1” step to select it. I usually click anywhere in the gray, and this should turn it black.
Next, click on the Add Action button, or you can use the Insert > Action menu.
Finally, change the type from SQL to PeopleCode.
At this point, you need to save before you can add PeopleCode. You can use Ctrl + S, click on the Save icon on the toolbar, or you can use the File > Save menu.
First, open the PeopleCode program by double clicking anywhere on the gray of the PeopleCode action. Or, you can right click on it and choose the “View PeopleCode” option.
Next, you will probably want to open a file to show output from your PeopleCode testing. You can use this PeopleCode:
Local File &log;
&log = GetFile("c:\temp\log.txt", "W", "A", %Filepath_Absolute);
Then, you can print to that file with the writeline() method. For now, we will just print Hello, World.
&log.WriteLine("Hello, World!");
Finally, you will probably want to close your file:
&log.Close();
Here is what it all looks like:
Make sure to save once you make these changes.
Again, after you have saved, go back to the main program window where you can see the Main section, Step 1, and your new PeopleCode action. Then, click the run icon.
In the dialog, Check the Output log to file and uncheck Run Minimized. The output log to file allows you to see what happened. Otherwise, the window will close before you see what happened. The run minimized isn’t a big deal, but if the program doesn’t run minimized you see it pop up and go away better. When the program goes away, you know it is done running.
Finally, when it is done, check the output. If you used the paths that I did your output should be in the c:\temp directory. You should have two files. The first, is the main output from the program. Check this to make sure the program ran to success:
The second is the log that your PeopleCode created. For now, it should just say, “Hello, World”.
Here is another one of those technologies that I would love to play with but have to wait for a client that actually needs it: JSON. I found Jim’s post on JSON very interesting and would love to have the need to come back to it.
One other solution that might be worth considering is this library for Java. You would have to compile it and place it on the class path, but you could access it from PeopleCode. Or, I wonder if it would be worth implementing the library in a PeopleCode Application Package?
And in conjunction, you can’t mention JSON, without mentioning jQuery.
This page has moved. Please update your links:Jim Marion’s post on JDBC made me think a little more. (By the way, thanks, Jim, for linking me.) The one disadvantage about accessing the PeopleSoft database via JDBC is that you have to supply the password to make the connection.
I have thought about trying to read the password from the application server or batch server configuration file, but if I remember right it only has the connect id and the connect password. With the connect password, I might be able to use it to read the Access id and password from the database, but I have would have to be able to unencrypt it.
One advantage that SQL Server might have is that you can use Window’s security. Assuming that the account running the application server or batch server has access to the database, you could just use the integrated security instead of an actual user name or password.
The advantage that JDBC has is that you don’t have to know the number of fields/columns that you want until run time. With both the SQL object and SQLExec, you have to have a variable for each field you return or a return that contains all of those fields.
For example, I am trying to loop through a group of tables in a linked server and copy all of their fields to a table in the current database. I have a problem using INSERT … SELECT, and I have to read the values in and then write them out. I can’t figure another way to do it other than use JDBC.
Please correct me if I am wrong on any of this. Maybe these thoughts will give someone else an idea that I overlooked.
This page has moved. Please update your links:Today, I came across this interesting tip about editing PeopleCode:
Editing Enhancements for SQR and PeopleCode
I had something like this for gVim, but I need to dig it out again.
They also posted information about shortcuts in the Application Designer PeopleCode editor:
The article references PeopleBooks:
This page has moved. Please update your links:This is a continuation of my virtual PeopleSoft installation. In this step, we will create the database in an already installed Oracle Database system. So, this assumes that the Oracle Database software is already installed. Loading the PeopleTools data will be covered in the next step. To see the complete list of steps, click here.
This page has moved. Please update your links:Before you can use any object you must instantiate it first. This means that you must create the memory for object. See the Wikipedia for more information.
The instantiation applies to both regular PeopleTools objects and custom Application Packages. Here is an exploration or documentation of how you would do it.
This page has moved. Please update your links:We have an interface file that we want to delete for security reasons once we have processed the file. But, deleting it from the Application Engine was not as straight-forward as I would have thought.
This does not work:
RemoveDirectory("c:\temp\mytextfile.txt", %FilePath_Absolute);
So, Java to the rescue — this does:
Local JavaObject &javaFile;
&javaFile = CreateJavaObject("java.io.File", "c:\temp\mytextfile.txt");
&javaFile.delete();
PSST0101 