Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

PMF 6.1.1 - Sending and enabling Direct Feedback

Updated on June 10, 2020


When connectivity is set up between a Process Commander V 6.1 SP1 application server and the Project Management Framework to track project activity, you can also enable and use the Direct Feedback feature. This allows application users, testers and developers to record and submit bugs, issues, ideas, and proposed solutions directly to PMF.

When enabled, a pushpin icon appears on the user portal. Users can drag and drop the icon on the desktop, enter a text note, capture a screenshot and send it as a message to PMF. The framework creates a work object and screenshot, URL, and correspondence attachments for review and follow up action. An email with feedback detail is sent to the email address of the sender.

This article describes:

  • How users send and review direct feedback
  • How system architects enable and configure direct feedback options in the application server and the framework


Sending Direct Feedback

    1. Click and drag it to the area on the screen you want to reference in the feedback.

User Tip: To capture the feedback for entry fields correctly, place the on read only text.

    1. In the pop-up window:
  • Check the Include Screenshot box when you want to include a screenshot in the feedback message.
  • The email address in your operator profile populates the From field. If you want to send a copy of the feedback message to yourself and another person, enter the email address of the person in this field.
  • Enter your feedback text and select a feedback category.


    1. Click Send. A feedback message is sent to the Project Management Framework.

When the feedback is received and processed by the framework, an email is sent to your email address and the address entered in the From field. The email text includes the ID of the item created in the framework and the feedback text.

Receiving and Reviewing Feedback

When the feedback is received by the framework, a bug item is created and routed to the ProjMgmtApprovals workbasket where it can be reviewed and triaged.

It also captures and displays the build information from the sending application including the application name, version, and build ID.

The attachments tab can contain up to four attachments created by the process:

    • The screenshot of the problem or issue
    • A copy of the email to the sender
    • A copy of the email sent to the address entered in the From field, if different from the sender
    • A link to the harness or section rule on which the was placed


Enabling Direct Feedback

Enabling direct feedback is a task performed by users who have access to the Designer Studio.

To enable feedback, follow the setup tasks for the application server sending the feedback and PMF.

In the Application Server

  1. Connectivity must be setup between the application server and the framework.
  2. The application server sending the feedback must be installed on Process Commander Version 6.1 SP1.
  3. In the Application rule for each application you want to send feedback:
    • The Built on Application and Version fields on the General tab must reference an application layer that is built on PegaRULES Version 06.01.01. This is usually the topmost application in the stack.
    • Check the Enable Project Management box on the Advanced tab

  4. Add the access role PegaRULES:Feedback to the access group of operators you want to send feedback.

  5. Check the Show Pin box located on the Tools menu of the User Preferences menu. This box defaults to checked when you install Process commander V6.1 SP1 and accessible only from the developer portal.

    Note: This checkbox toggles the display of the on and off when the PegaRules:Feedback role is present in the user's access group. In installations where users have access to their preferences, they can individually control the display of the icon. If not, the display is controlled by checking the Enable Project Management box on the application rule and adding the access role to the access group.


In the Project Management Framework

When installed, the framework is configured to:

  • Create a bug item from the feedback message
  • Route it to the ProjMgmtApprovals workbasket
  • Link it to a default project
  • Determine whether or not to send an email
  • Send email to the feedback sender and the email address entered in the From field with the ID and details of the item it creates
  • Send email to feedback sender

Follow the steps below if you want to change these options.


Change the Default Project

This option uses a decision tree to map feedback from the sending application to default projects using property values.

    1. Save the DetermineInitialGroup decision tree to your RuleSet.
    2. On the Decision tab, update the logic for the sending application.
    3. On the Results tab, update the property mapping and linking logic.

    The following is a list of feedback properties you can use to evaluate the incoming message in your mapping logic.

        • .GenericWorkForInt.BuildData.ApplicationName
        • .GenericWorkForInt.BuildData.ApplicationVersion
        • .GenericWorkForInt.BuildData.BuildID
        • .GenericWorkForInt.Category
        • .GenericWorkForInt.ReportedByDivision
        • .GenericWorkForInt.ReportedByOrg
        • .GenericWorkForInt.ReportedByWorkgroup
        • .GenericWorkForInt.Reason

          • See

        HelpAbout Decision Tree rules

          • for information about this rule form.

        Add Email Exceptions

        This option uses a decision tree to determine whether or not to send an email based on the email address of the sending operator.

          1. Save the ValidEmailAddressesforCorr decision tree to your RuleSet.
          2. On the Decision tab, update the logic for the email address of the sending operator.

          Returning a value of true sends an email

            • See

          HelpAbout Decision Tree rules

            • for information about this rule form.


          Change the PMF Work Object the Feedback Creates

          This option uses a decision table to map the feedback message (FDBK work type) to a work type in PMF.

            1. Save the DetermineTargetClass decision table to your Ruleset.
            2. On the Table tab, update the condition statement for the FDBK work type.

              • See

            HelpAbout Decision Table rules

            • for information about this rule form.


            This article links to the following articles describing features and functions of the PMF 6.1.1 release.

            What's New

            Installing and Upgrading the Framework

            Setting Up the Framework

            Setting Up Connectivity to Development Systems

            Using the Administrative Functions

            Navigating the Project Portal

            Tracking Bugs and Issues

            Tracking Development Activity in a Project

            Documenting Project Progress

            Integrating PMF with External Systems

            Select one of the following links to connect to a group of articles specific to working with Scrum or SmartBPM projects in PMF.

            Creating Scrum Projects

            Creating SmartBPM Projects


            Return to About the Project Management Framework

            • Previous topic PMF 6.1.1 - Navigating the project portal
            • Next topic PMF 6.1.1 - Setting up connectivity to development systems

            Have a question? Get answers now.

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

            Did you find this content helpful?

            Want to help us improve this content?

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

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

            Close Deprecation Notice
            Contact us