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.

How to add report links to the Monitor Activity workspace

Updated on March 28, 2008

 This presentation is part of the Portals Overview Self-Study Course.


In this scenario, the client would like to add a report to the Monitor Activity tab. 

The steps to take to resolve this requirement include:

  1. Create the Rule-Obj-ListView or Rule-Obj-SummaryView if it does not yet exist.
  2. Determine in which group the report should reside in the work space portion of the portal.
  3. Copy the custom activity called "Reports" that is defined in the Custom tab of the Portal into your RuleSet.
  4. Locate the appropriate model that is called by the custom activity "Reports."  Note that the model name is derived by the purpose of the report plus the string "Reports."   Therefore, the model name would be AssignmentMonitoringReports in this example.
  5. Update the appropriate model that is called by the custom activity "Reports."
  • Note:  Each model is generating an array of reports using the pyInstances(n) property which resides on the MyRules page.   Each report has two properties, the hidden URL which is generated as pyInstances(n).pyInsHandle and the text description of the report displayed on the screen as the link generated as pyInstances(n).pyAdviceText.   To add your report simply append two additional lines to this model.
  • Refresh the Portal display by clicking the refresh icon at the top of the portal.
  • 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