Service Portlet form - Completing the Portlet tab
Identify the service activity that displays the home page of the portlet and the values used to authenticate the portlet users.
| Field | Description |
|---|---|
| Processing | |
| Activity Class | Enter the first key part — Applies To — of the service activity. |
| Service Activity Name | Enter the second key part — Activity Name — of the service activity. |
| Help Activity Name | 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. |
| Authentication | Complete these fields unless the portlet is to access this Pega Platform system as an unauthenticated (guest) user. |
| Application ID |
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 the
Pega Platform.
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 Community article How portlet services work. |
| Cost Center Number | Leave blank. This field provides backward compatibility with single sign-on mechanisms in older Pega Platform versions. |
| User Identifier Attribute |
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 the
Pega Platform.
For example, a typical value for a WebSphere portal server is: |
| User Name Attribute |
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:
|