Building your URL

First, consider a situation where the agency is using single sign on for Infor Public Sector. Assuming the agency has installed Infor Public Sector on a server called IPSServer, this URL would be used to send a work order:

http://IPSServer/InforPS/HFrame.htm?monk=Hansen.WorkManagement.
WorkOrderViewerApplet&ki=1969&isQuery=false&hasMenu=false
&showHeader=false

The first part of the URL, up to the question mark, is the same address that you would normally use to log in to Infor Public Sector. (HFrame.htm is the default content page for Infor Public Sector, and is optional in the URL. Because this page is the default for the Infor Public Sector site, Internet Information Services will load it automatically if you don’t include it in the address.)

Following the question mark is the query string, which gives the details that Infor Public Sector needs to find and display the correct information. The query string consists of a series of name/value pairs separated by ampersands. The query string can include these parts:

• monk: Moniker of the applet that you want to open.

  See Finding the moniker.

• ki: Specifies the primary key of the record that you want to load.

  You might need to query your data source to determine the primary key, because the key doesn’t always appear in Infor Public Sector. For example, the identification number that appears in the Work Order InfoViewer is the same as the primary key, but assets in Infor Public Sector are identified by unit IDs that are different from their primary keys.

• ks: This is an alternative to the ki parameter in cases where a record’s primary key is a string rather than an integer.
• id: With some types of records, this parameter can be used as an alternative to the ki parameter to load a record by its ID.

  For example, you can use this to load an asset based on its unit ID. You can also use the id parameter with parcels, parts, billing accounts, and applications, licenses, and cases in the CDR modules.

• The isQuery, hasMenu, and showHeader parameters are required for the applet to be displayed correctly.

If the agency is using Web Services to get a ticket rather than using single sign on, then the ticket must also be included in the query string. Enter ticket= and then enter the string returned by the LoginService, such as:

ticket=NxdbM5TzebCPRvbcclFAxCEd8yssVmb9yuYL/WHkWb2KnU9YTF64ufAOyKLkSrZ
sRGK3sMsyXZTr0Qj3S8I5FV9XufW8r5rCrhRYoruD0l1PTRq22IEJzIQrxq533HIXPh
Bk9goig80jpnYTeerDq2F2Mhv2qcIF/4SXgBND00BOWrZhuDYXcq4T71GyswlPFHiRq
mqTtY2R2pRq9JszeC8x2vx6Q0hgOSgjCUR1imvUP2pNAdrP0BUIH7CTF8+meTXTZuzS
fxJMPq1Tu//wcBuQ+1eoU1iGcS30SluhiutmZExYyaqqDJ6vDAOwqgYo