Local JavaObject &loginMgr = CreateJavaObject("com.greysparling.asterisk.PSoftLoginManager", &host, &user, &pswd);
Local JavaObject &loginEvt = &loginMgr.challengeUser(&userID, &phone, &pinCode, &channel, &context, &exten);
If &loginEvt.isSuccess() Then
Warning ("Successfully validated user " | &userID);
Else
Warning ("Off with " | &userID | "'s head!");
End-If;

[challenge-psft-user]
exten => 7189,1,Answer()
exten => 7189,2,Playback(vm-intro)
exten => 7189,3,NoOp(Authenticating user ${PSFTUSERID})
exten => 7189,4,Authenticate(${PIN},j)
exten => 7189,5,NoOp(Successful login ${PSFTUSERID})
exten => 7189,6,UserEvent(PSoftLogin|userId: ${PSFTUSERID}|result: SUCCESS)
exten => 7189,7,Hangup()
exten => 7189,105,NoOp(Unsuccessful login ${PSFTUSERID})
exten => 7189,106,UserEvent(PSoftLogin|userId: ${PSFTUSERID}|result: FAILURE)
exten => 7189,107,Hangup()

    -- Executing [7189@challenge-psft-user:1] Answer("IAX2/123456789-2", "") in new stack
  -- Executing [7189@challenge-psft-user:2] Playback("IAX2/123456789-2", "gs-demo-login") in new stack
  --  Playing 'gs-demo-login' (language 'en')
  -- Executing [7189@challenge-psft-user:3] NoOp("IAX2/123456789-2", "Authenticating user PTDMO") in new stack
  -- Executing [7189@challenge-psft-user:4] Authenticate("IAX2/123456789-2", "4554|j") in new stack
  --  Playing 'agent-pass' (language 'en')
  --  Playing 'auth-thankyou' (language 'en')
  -- Executing [7189@challenge-psft-user:5] NoOp("IAX2/123456789-2", "Successful login PTDMO") in new stack
  -- Executing [7189@challenge-psft-user:6] UserEvent("IAX2/123456789-2", "PSoftLogin|userId: PTDMO|result: SUCCESS") in new stack
  -- Executing [7189@challenge-psft-user:7] Hangup("IAX2/123456789-2", "") in new stack
== Spawn extension (challenge-psft-user, 7189, 7) exited non-zero on 'IAX2/123456789-2'
  -- Hungup 'IAX2/123456789-2'

package com.greysparling.asterisk;

import org.asteriskjava.manager.event.UserEvent;

public class PSoftLoginEvent extends UserEvent {
 private String userId;
 private String result;

 public PSoftLoginEvent(Object source) {
  super(source);
 }
 
 public String toString() {
  return "PSoftLogin for " + getUserId() + " (" + result + "),"
   + super.toString();
 }
 
 public boolean isSuccess() {
  return "SUCCESS".equals(result);
 }

 public void setResult(String result) {
  this.result = result;
 }

 public String getUserId() {
  return userId;
 }

 public void setUserId(String userId) {
  this.userId = userId;
 }

 private static final long serialVersionUID = 1L;

}

package com.greysparling.asterisk;

import java.io.IOException;
import java.util.HashMap;

import org.asteriskjava.manager.AuthenticationFailedException;
import org.asteriskjava.manager.ManagerConnection;
import org.asteriskjava.manager.ManagerConnectionFactory;
import org.asteriskjava.manager.ManagerEventListener;
import org.asteriskjava.manager.TimeoutException;
import org.asteriskjava.manager.action.OriginateAction;
import org.asteriskjava.manager.event.ManagerEvent;
import org.asteriskjava.manager.response.ManagerResponse;

public class PSoftLoginManager implements ManagerEventListener {

 private ManagerConnection connection;
 private boolean keep_running = true;
 
 private String userId;
 private PSoftLoginEvent event;
 
 static final String USERID = "PSFTUSERID";
 static final String PIN = "PIN";
 
 public PSoftLoginManager(String host, String user, String pswd) throws
   AuthenticationFailedException, TimeoutException, IOException {
  
  ManagerConnectionFactory factory =
   new ManagerConnectionFactory(host, user, pswd);
  
  connection = factory.createManagerConnection();
  connection.addEventListener(this);
  connection.registerUserEventClass(PSoftLoginEvent.class);
  connection.login();
 }

 public PSoftLoginEvent challengeUser(String userId, String phone,
    String pinCode, String channel, String context, String exten)
   throws InterruptedException, TimeoutException, IOException {
  
  this.userId = userId;
  this.event = null;
  
  HashMap vars = new HashMap();
  vars.put(USERID, userId);
  vars.put(PIN, pinCode);
    
  OriginateAction action = new OriginateAction();
  action.setChannel(channel + "/" + phone);
  action.setContext(context);
  action.setVariables(vars);
  action.setExten(exten);
  action.setPriority(new Integer(1));
  
  ManagerResponse response = connection.sendAction(action, 30000);
  System.out.println(response.getResponse());

  while (keep_running)
   Thread.sleep(100);
  
  return this.event; // caller can check isSuccess()
 }
 
 public void onManagerEvent(ManagerEvent event) {
  if (event instanceof PSoftLoginEvent) {
   PSoftLoginEvent login_event = (PSoftLoginEvent)event;
   System.out.println("Login event: " +  login_event);
   if (userId.equals(login_event.getUserId())) {
    System.out.println("Matched user");
    this.event = login_event;
    this.stop();
   }
   else {
    System.out.println("User was " + login_event.getUserId());
   }
  }
  else {
   System.out.println("Event: " + event);
  }
 }
 
 public void stop() {
  keep_running = false;
 }
 
}

Labels: 2008, Java, PeopleCode, Security, Telephony

REM Connectivity to Asterisk server. ;
REM Assumes that &user has been granted access to Asterisk Manager API;
Local string &host = "192.168.1.200";
Local string &user = "asterisk_user_id";
Local string &pswd = "asterisk_password";

REM Asterisk information for how we will be originating phone calls;
Local String &voip_provider_acct = "123456789";
Local string &channel = "IAX2/" | &voip_provider_acct;
Local string &context = "challenge-psft-user";
Local string &exten = "7189";

REM The phone number that we will be calling;
REM This would normally come out of the user's profile;
Local string &phone = "15105551212";

REM The PeopleSoft userID of the person to call;
Local string &userID = "PTDMO";

REM This PIN could be autogenerated or stored in the DB;
Local string &pinCode = "4554";


REM ******** No more user variables below here *********** ;
Local string &base = "org.asteriskjava.manager.";
Local JavaObject &connectFactory = CreateJavaObject(&base | "ManagerConnectionFactory", &host, &user, &pswd);

Local JavaObject &connection = &connectFactory.createManagerConnection();
&connection.login();

Local JavaObject &originateAction = CreateJavaObject(&base | "action.OriginateAction");
Local JavaObject &vars = CreateJavaObject("java.util.HashMap");
&vars.put("PIN", &pinCode);
&vars.put("PSFTUSERID", &userID);
&originateAction.setChannel(&channel | "/" | &phone);
&originateAction.setContext(&context);
&originateAction.setVariables(&vars);
&originateAction.setExten(&exten);
&originateAction.setPriority(CreateJavaObject("java.lang.Integer", 1));

Local JavaObject &originateResponse = &connection.sendAction(&originateAction, 30000);
Warning (&originateResponse.getResponse());

  == Parsing '/etc/asterisk/manager.conf': Found
== Manager 'asterisk_user_id' logged on from 192.168.1.11
-- Call accepted by 64.85.163.184 (format ulaw)
-- Format for call is ulaw

      > Channel IAX2/123456789-2 was answered.

[challenge-psft-user]
exten => 7189,1,Answer()
exten => 7189,2,Playback(gs-demo-login)
exten => 7189,3,NoOp(Authenticating user ${PSFTUSERID})
exten => 7189,4,Authenticate(${PIN},j)
exten => 7189,5,NoOp(Successful login ${PSFTUSERID})
exten => 7189,6,Hangup()
exten => 7189,105,NoOp(Unsuccessful login ${PSFTUSERID})
exten => 7189,106,Hangup()

    -- Executing [7189@challenge-psft-user:1] Answer("IAX2/123456789-2", "") in new stack
  -- Executing [7189@challenge-psft-user:2] Playback("IAX2/123456789-2", "gs-demo-login") in new stack
  --  Playing 'gs-demo-login' (language 'en')
== Manager 'asterisk_user_id' logged off from 192.168.1.11
  -- Executing [7189@challenge-psft-user:3] NoOp("IAX2/123456789-2", "Authenticating user PTDMO") in new stack
  -- Executing [7189@challenge-psft-user:4] Authenticate("IAX2/123456789-2", "4554|j") in new stack
  --  Playing 'agent-pass' (language 'en')
  --  Playing 'auth-incorrect' (language 'en')
  --  Playing 'auth-incorrect' (language 'en')
  -- Executing [7189@challenge-psft-user:105] NoOp("IAX2/123456789-2", "Unsuccessful login PTDMO") in new stack
  -- Executing [7189@challenge-psft-user:106] Hangup("IAX2/123456789-2", "") in new stack
== Spawn extension (challenge-psft-user, 7189, 106) exited non-zero on 'IAX2/123456789-2'
  -- Hungup 'IAX2/123456789-2'

    --  Playing 'agent-pass' (language 'en')
   --  Playing 'auth-thankyou' (language 'en')
   -- Executing [7189@challenge-psft-user:5] NoOp("IAX2/123456789-3", "Successful login PTDMO") in new stack
   -- Executing [7189@challenge-psft-user:6] Hangup("IAX2/123456789-3", "") in new stack

Labels: 2008, Java, PeopleCode, Security, Telephony

Labels: 2008, Java, PeopleCode

Labels: 2008, PeopleCode

Labels: 2007 Oracle OpenWorld Version_Control, PeopleCode, SQR

So, you have a journal with several hundred lines in it, and you want to find the lines that hit a particular account, fund code, and program code. You have a query that tells you it's there, but you want to pull up the journal entry itself to review it there.

This is the culmination of the last two posts with a few extra tidbits, such as array handling, rowset handling, and using variables to pick the field you want to use.

This posting shows how to pass any chartfield combination on the URL for accessing the journal entry page, allowing the navigation to the journal line(s) that contain those chartfield values. The code is written against Financials 8.9, but should work for previous versions.

Using a variable as a field reference?

Yes. One of the key items in the solution is the ability to evaluate a variable to get a fieldname in a record.field reference (this is how I'm able to take the list of chartfields from the BU_LED_CF_VW and use them). For those who aren't familiar with this, you can use @("RECORDNAME." | &VariableName) to do this. We often wrap this syntax with GetRecord or GetField to make it more error-proof in some of our other products.

Solution to the problem

The code does the following:

• It matches up the valid chartfields with parameter names passed on the command line
• It determines whether the journal is editable.
• If it is editable, then it uses the SetCursorPos function
• If it isn't editable, then it sets the work fields that the adjust_line_scroll() function uses

Here's the code (it should be added in the page activate Peoplecode after the PeopleSoft-delivered page activate PeopleCode in the JOURNAL_ENTRY2_IE page).

Labels: Drilling, PeopleCode

For those who are familiar with our demo and posting that discusses how to drill from a report into a page (blog posting here), you may or may not notice a limitation in what was presented. The example showed drilling from a financial report to the journal entry where the number came from. Unfortunately, drilling to the journal is just not granular enough to tell you exactly where the number came from (journals can have hundreds of lines, and a number in a financial report is governed by the chartfield values that are used).

This means that what you really want to do is to drill to items that are at scroll level 1 or greater in the page. Because the standard URLs to PeopleSoft pages are driven by the search records for those pages, you need to be able to (1) pass parameters to identify what values you want to navigate to, and (2) write code to do the navigation.

Sounds interesting, so how do you do it?

Well, the first part was answered in this posting on how to add parameters to your PeopleSoft pages.

The second part can be acoomplished in multiple ways (depending on the following):

• Whether the page or scroll items are read only.
• Whether the data to be navigated to is chunked by application code or by PeopleTools.

Using the SetCursorPos PeopleCode Function

The first approach we will discuss is using the SetCursorPos function. This works by iterating through the data in the component buffer until you find the row you want to be on, and setting the focus (or cursor position) to a field on that row. Because you can't navigate to fields that are grayed out (or are read only), this only works when that occurs. Also, since you are navigating through what's already in the component buffer, if the only loads a subset of the data at a time into the component buffer, then you may be navigating through a small part of the data you want to search. Navigating to a posted journal entry in PeopleTools is a perfect example of where both of these conditions would prevent this from occurring.

Here is an example of code you would use for a page with updatable data where the component buffer contains the full data set you want to search

Local Rowset &rsJrnlLines = GetLevel0().GetRow(1).GetRowset(Scroll.JRNL_LN);

Local number &j;
For &j = 1 To &rsJrnlLines.ActiveRowCount


Local Row &rowTest = &rsJrnlLines.GetRow(&j);

If &rowTest.GetRecord(Record.JRNL_LN).GetField(Field.ACCOUNT).Value = &sAcctNum Then

&rowTest.GetRecord(Record.JRNL_LN).GetField(Field.ACCOUNT).SetCursorPos(%Page);

Break;
End-If;

Adding a navigation element to the grid

If all the items in the scroll are read-only (or grayed out), then another option is to put a push button or other element in the grid that isn't grayed out to set focus to. It's actually as simple as that. You add the item, and then set the cursor position to it. Of course, this gets into customizing the page itself, which can be an issue at upgrade time.

Leverage selection code written into the page

This approach can be used very effectively in inquiry pages or even pages where there search logic is used written by application developers to populate the scroll. The journal line page is a great example of this. There's a link in the Financials 8.9 journal entry page that allows you to enter search criteria for your journal lines. This page actually displays fields in the JRNL_PANELS_WRK record, which is in the componenet buffer for the page. By merrely setting the values of chartifelds in this work record and calling the adjust_line_scroll function, you can use parameters to restrict the set of journal lines displayed in the page (ultimately drilling to those values).

Here is the code to do that.

Declare Function adjust_line_scroll PeopleCode FUNCLIB_GL.JOURNAL_LINE FieldFormula;

/* Code to drill to row with account number passed in as a parameter */

Local string &sAcctNum = %Request.GetParameter("ACCOUNT");
If All(&sAcctNum) Then

If JRNL_HEADER.JRNL_HDR_STATUS = "D" Or
JRNL_HEADER.JRNL_HDR_STATUS = "P" Or
JRNL_HEADER.JRNL_HDR_STATUS = "U" Then

/* Journal is read only */
JRNL_PANELS_WRK.ACCOUNT = &sAcctNum;
adjust_line_scroll();

End-if;

One last item of note: if there is already Page Activate PeopleCode, you will probably want to put yours at the end for the navigation (this ensures that all other logic has already been executed). The JOURNAL_ENTRY2_IE page is an example of this.

Labels: Drilling, nVision, PeopleCode

So, you want to navigate to a PeopleSoft page, passing the parameters to open a specific item. But now, you want to pass a parameter that does something within the page:

• Populate the search items in an inquiry page and search based on the parameter.
• Set the vendor to be used in the voucher page
• Navigate to a row in a grid in the page

These are but a few examples

You can really do that?

Of Course! It's actually pretty straightforward. The key to this is the Request object (it's actually documented in PeopleBooks as part of the Iscript class, but is available for standard pages as well).

So, all you need to do to add a parameter to your page is to write code in the page activate peoplecode that looks for a parameter in the request object with the name you want (or a set of names). Once you have those parameters, you can use them in different ways (as listed above.

Because you can look for any parameter, regardless of whether it's actually passed, you have a lot of flexibility (and you can look for as many as you want). Therefore, you could actually go through and look for every chartfield on the URL and use the combination of the ones you found to do some logic.

The next posting will show how this technique can be used to fix limitations in drilling to pages that were glossed over in the following posting.

Labels: Drilling, PeopleCode

Labels: 2007, Events, PeopleCode

• nVision Drilling Snap-On
• Report Explorer
• PSIDE Helper Snap-On
• Desktop Single Signon
• nVision Context Helper Snap-On

• Financial Services Industry User Group
• Alliance Conference (Higher Education User Group, State and Local User Group, Federal User Network)
• Northern California PeopleSoft User Group
• Mid-Atlantic User Group
• Quest Mid-West
• Oracle OpenWorld
• UK Oracle User Group
• Santa's Helpers User Group (just seeing if you're still reading!)

• Marion Crkon
• Dan Iverson
• Jim Marion

• Most Unusual blog entry. Who would have thought about integrating instant messaging with PeopleTools? Chris, of course!
• Most Humorous blog entry. Before it was posted on YouTube, the top link to see SAP's take on Larry Ellison was from our site.
• Most Historical blog entry. Think scoping a PeopleSoft release took lots of analysis and effort? It did, but if certain features made it in, the world may actually have come to an end.
• Best Fusion Preparation series (Java and PeopleCode 1, Java and PeopleCode 2, Java and PeopleCode 3). J2EE and Web 2.0 your PeopleSoft application, because that's a big part of Fusion!
• Most popular blog entry that almost didn't get written. Is anybody really thinking about Setids and Business Units any more? Apparently Yes!

• Best Sales story. At Oracle Open World, we literally had a PeopleSoft customer come up to our booth on the first day and ask us how quickly we could generate an invoice for our Desktop Single Signon product. We did a remote install using the Open World wireless, and they were using the product live within 2 weeks for their 2007 Open Enrollment. Initial contact to Production in less than 2 weeks!
• Runner-Up Sales story. At the FSIUG in New York after demonstrating the nVision Drilling Snap-on, we did a remote installation of a trial version at a customer. This customer was able to use WebEx to show it to end-users who were not at the conference, and decide to purchase it right then and there.
• Best Cheapskate story. This had to be at the Alliance Conference, where we discovered how expensive it would be to rent an additional table for our booth for the 3 days the exhibition hall was open. Bert Laws of BearingPoint (a local of Nashville) was kind enough to make a run to Costco and buy a table for us (yes, it was significantly less expensive to buy a table than to rent it). We ended up giving the table to the folks at the Dell booth next to ours at the end of the conference (it would have been too difficult to check with our baggage).
• Best Clueless travel story. As good interenet users, we used Google Maps to print driving directions for all the places we were going in the UK while we were there for the UKOUG (knowing that Chris's mobile account for his Blackberry wouldn't work there). I don't remember the last time I had to look at a map to get where I needed to go in the states. This didn't work too well in the UK, and we ended up getting hopelessly lost many times on the trip. We ended up buying a map to help us make it through the trip.

• 2007 Northern California Training Day
• 2007 Alliance Conference
• 2007 EMEA Conference
• 2007 Collaborate
• 2007 Open World

From an engineering perspective, we've got two new products that we're partnering with customers to build in the first half of the year:

• nVision Bolt-on. This will address most of the outstanding nVision issues that we had hoped to address while we were still at PeopleSoft.
• Workflow Notifications. This is a product requested by a long-time Higher Education customer who saw our email notification functionality in our report distribution product, and are currently grappling with the best way to deploy workflow with eProcurement and HCM applications.

We also have plans to add some new features to our existing products, so if you've already licensed something from us, you'll probably hear from us soon.

Labels: 2006, Events, nVision, PeopleCode, PeopleSoft, Reporting, Security, User

&jBufImage = &jImageIO.read(CreateJavaObject("java.io.File", &sSourceFileName));

&jReadArgTypes = CreateJavaObject("java.lang.Class[]", &jIOFileClass);
&jReadMethod = &jImageIOClass.getDeclaredMethod("read", &jReadArgTypes);
&jReadArgs = CreateJavaObject("java.lang.Object[]", CreateJavaObject("java.io.File", &sSourceFileName));
&jBufImage = &jReadMethod.invoke(&jImageIO, &jReadArgs);

&jImageIOClass = GetJavaClass("java.lang.Class").forName("javax.imageio.ImageIO");

Labels: PeopleCode, User

Local String &sMyValue = %Request.GetParameter("myvalue");
If All(&sMyValue) Then
 rem Do something with &sMyValue - like filtering the data on the page;
End-if;

Labels: PeopleCode, User

Labels: PeopleCode, User

document.write("<style>#PAGEBAR { display: none; }</style>");

Labels: PeopleCode, Security, User

Labels: PeopleCode

Labels: PeopleCode

package com.greysparling.demo;

public class JavaPeopleCode1 {
 
   public static boolean IsObjectNull(Object test1) {
       if (test1 == null) {
           return true;
       }
       else {
           return false;
       }
   }

   public static boolean IsStringNull(String test2) {
       if (test2 == null) {
           return true;
       }
       else {
           return false;
       }
   }
 
}

Local String &sClassName, &sPeopleCodeString;
Local JavaObject &demo;

&sClassName = "com.greysparling.demo.JavaPeopleCode1";
&demo =  GetJavaClass(&sClassName);
&sPeopleCodeString = "Testing";

Warning (&demo.IsObjectNull(&sPeopleCodeString));
Warning (&demo.IsObjectNull( Null));

Warning (&demo.IsStringNull(&sPeopleCodeString));
Warning (&demo.IsStringNull( Null));

False
True
False
False

Labels: PeopleCode