krishnamraju

In reviewing my statistics, I found that one common search was “basics steps to create an appengine in PeopleSoft”.  I hope the person(s) found what they were looking for on my blog.  Nonetheless, that gave me the idea to write a simple overview on creating a new Application Engine program. This post can’t cover everything but I do plan to cover: ·          Creating a new Application Engine definition ·          Setting program properties ·          Understanding program flow ·          Inserting new sections, steps, and actions ·          Loops/logic ·          State records ·          Adding programs to projects ·          Where to go from here Creating a new Application Engine Definition Application Engine programs are definitions that are created and edited within Application Designer.  So, open Application Designer and log in.  Next, either use the File > New menu, press Ctrl + N, or click on the “New” icon on the toolbar. File > New / Ctrl + N:

Dynamic Prompts in PeopleSoft In real business applications, very frequently we will encounter situations where the prompt for some fields needs to be controlled based on the values on other fields or based on the logged in user. PeopleSoft has delivered built-in mechanisms to handle dynamic prompting. Most of the readers will be already aware of this as this is one of the basic lessons in People Tools. However recently I had an interaction with PeopleSoft developer community, where most of them shared the same experience. People either don’t know dynamic prompting or they are not sure about the underlying technology to be used. I thought it will be worth explaining it over here so that people who are new to PeopleSoft may get a fair understanding on dynamic prompting. There are widely two different techniques used for generating dynamic prompting. 1.     First method is using DERIVED record fields or popularly known as Edit Table method. 2.   The second popular meth