RegoXchange
  • This Excel document provides a template for mocking up and validating portlet requirements.  The template is important to use to help end users visualize the final output of a portlet. Template Defines:
    • Portlet Name
    • Portlet Purpose
    • Portlet Description
    • Portlet Security
    • Portlet Placement
    • Portlet Filter Fields/Layout
    • Portlet Grid Fields/Layout
  • The Communications Portlet - Simple portlet provides a simple mechanism to communicate with Clarity users.  The content of the porlet can be edited easily through the Portlet administration screens within Clarity. This is a very beneficial method of delivering messages to your Clarity users all at the same time.
  • The Communications Portlet - Simple portlet provides a simple mechanism to communicate with Clarity users.  The content of the porlet can be edited easily through the Portlet administration screens within Clarity. This is a very beneficial method of delivering messages to your Clarity users all at the same time.
  • This tech trick demonstrates how to use Microsoft Excel to map data to XOG files by using the Developer tab in Excel 2010+.  Using a standard XML XOG file as provided by CA the guide and walkthrough video shows off the power of Excel and the ease in which object instance values can be directly inserted into or updated in Clarity.
  • This technical trick provides a supported method for removing team members from a project programmatically.  This is a XOG-based solution that might be called by a gel script in a process workflow.  Limitation is that the resource must NOT have actuals booked.
  • Looking for metrics that you can implement immediately in CA PPM? This class will be a working session to review all of the content available out of the box and within the CA and Rego content packs.  This will provide you the options for metrics the represent industry best practice without the costs to develop them.
  • This tip with show you the html needed to add a JasperSoft report to a CA PPM HTML portlet.
  • Styles can be applied to reports in two ways. The first is to select the item and apply a style directly to it.  The other is to apply a style to an entire report. When an item has had a style directly applied to it the application of a style to the entire report will not change the styles with manual styles applied. The manual styles override the entire report style application. This trick shows you how to find and remove manual styles.
  • JasperSoft as two font databases – one for display and one for pdf exporting. Not all fonts in the display database are in the exporting database. If you find you are not getting the proper fonts when exporting to PDF from JasperSoft this tech trick will show you how to add the missing font so your report exports as expected.
  • Over time notifications can build up in the CA PPM system and should be purged, so as not to hinder performance. The SQL statements mentioned in the tech doc can be implemented within a process in CA PPM to either purge notifications on an ongoing basis or remove all of them at once.
  • Changing the report programming language can allow the report developer to use other languages (such as Groovy or Javascript) instead of Java methods in expressions.  This can be useful in debugging report code.
  • In order for Jaspersoft Studio to interact with your Clarity instance, Jaspersoft Studio needs information to connect to your Clarity instance’s Jaspersoft repository.  This Tech Trick provides Instructions on how to get this information from within your Clarity Admin menu.
Go to Top