Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Viewing methods for a service package

Updated on April 6, 2022

After completing or updating the service rules in the service package, confirm that all the services rules you expect are present and accessible before you deploy. For Service REST rules, you can also view and delete the invocation history.

Before you begin:
  1. Create a service package. For more information, see Creating a service package.
  2. Define the processing mode, access group, and authentication for the service package. For more information, see Defining processing and authentication for service packages.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Integration-Resources category, and then click Service Package.
  3. On the Context tab, in the Methods section, click Refresh to refresh the list of methods.
    The system searches the PegaRULES database and lists rules (of the selected service rule type) with the package name as the first key part. If you provided an access group in the Service access group field, the display includes only rules of the selected service type that are visible to a requestor with that access group.

    If you did not provide a service access group, the display includes only rules (of the selected service type) that are visible to your ruleset list. This field uses a search to list the results, and does not update any rules.

  4. To review a list of the methods (each defined by a service rule) in the package, in the Service type field, select one service rule type. Save the form and click Refresh methods.
    For example: Rule-Service-REST
  5. Click Save on the rule form and then click Refresh.
  6. In the Service monitoring field, click the Gear icon to configure whether to monitor this rule, and if monitoring, whether to include the clipboard state.
    This field is displayed when the service type is Rule-Service-REST. You can configure monitoring at the service level only if the service/EnableGlobalMonitoring dynamic system setting is set to Deferred.
    1. In the Edit service monitoring window, in the Select service monitoring field, select whether to enable monitoring for this rule.
    2. Optional: To configure monitoring at the individual service level by clicking As defined on the service rule.
    3. If you turn on monitoring, in the Capture clipboard state field, select whether to include the state of the primary data page in the monitoring results.
    4. Click Submit.
  7. To immediately delete the invocation history for all rules in the service package, click Clear invocation history.
    Note: This field is only displayed when the service type is Rule-Service-REST.
  8. In the Method name column, click the service rule to open it.
    Each service rule found in the service package is listed in the column. Each row lists the service version.
  9. If your service type is REST, click the service rule in the Resource path column to open it.
  10. In the Ruleset column, click the name of the ruleset to open it.
  11. In the Test endpoint, click Test to open a dialog box where you can enter values for the variable components of the URI template.
    The dialog box does not open if the endpoint only contains literal components.
  12. To view the invocation history for an individual rule, click View Invocation History.
    Result: The Service request invocation history dialog box displays information about each invocation of the rule. You can view the URI template, request and response data, the clipboard state (if configured), and attachments that are included in the request and response.
  13. Click Save.

Tags

Pega Platform 8.6 Data Integration

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us