Service Portlet form
Completing the Portlet tab

Field

Description

Enter the first key part — Applies To — of the service activity.

Enter the second key part —Activity Name — of the service activity.

Optional. Identify the name of an activity (in the same class as the service activity) that can produce and send a ready-to-display HTML page of help information for display in the client portlet.

Complete these fields unless the portlet is to access this Process Commander system as an unauthenticated (guest) user.

Select the application ID data instance (Data-Admin-AppID class) you created for this portlet. The PRPortletService authentication service uses this value to verify the security token that the portlet sends to identify itself to Process Commander.

Leave blank when implementing single sign-on with a custom activity that does not use an Application ID data instance.

For information about the PRPortletService and how application IDs are used by portlets, see Pega Developer Network article PRKB-25110 How portlet services work.

Leave blank. This field provides backward compatibility with single sign-on mechanisms in older Process Commander versions.

Specify the user attribute on the portal server that represents or maps to the value of the pyUserIdentifier property — that is, the Operator ID — of the Data-Admin-Operator-ID data instance in Process Commander.

For example, a typical value for a WebSphere portal server is:

user.business-info.online.email

Optional. Specify the user attribute on the portal server that represents or maps to the value of the pyUserName property of the Data-Admin-Operator-ID data instance. You can use it to display a user's name ("Juan Smith") in the portlet. For example:

username.data

After you save this form, click to view a tree of the components that comprise the service package. See About the Integration viewer.