RegoXchange
  • This is a standalone process that can be run by an admin to change the ownership of MUX views from a specified user to another specified user.  The process contains a single custom script, which has the following parameters that must be updated prior to running the process:
    • currentOwnerId (required): Resource ID for the current Owner (unique_name from srm_resources table)
    • newOwnerId (required): Resource ID for the new Owner (unique_name from srm_resources table)
    • viewCode (optional): Code for the specific view to update - leave blank if you want to transfer ownership for all views (odf_ui_views.code)
    The script will update the owner for all views that are marked as shared, as long as the new owner doesn’t have a similar view with the exact same name.  If there are views that can’t be updated, they will be logged in the process log.   To Run:
    1. Navigate to the process called Admin - MUX Views - Change Ownership.
    2. Navigate to the Start Step tab, Click on the Update Owner action, and click the Custom Script Parameters tab.
    3. Enter the Resource ID for the current view owner into the currentOwnerId parameter.
    4. Enter the Resource ID for the new owner into the newOwnerId parameter.
    5. If you want to update a specific view only, enter that in the viewCode parameter.
    6. Run the process via Organizer in Classic.
  • A quick reference guide that reviews all of the icons used in the vertical menu bar and provides a quick explanation on their meaning/use.
  • The Migration Tool for Modern UX Components provides the ability to migrate Blueprints, Views, and Field Level Security between environments.  Previously, the promotion of these components needed to be done manually.  This functionality, to be utilized by an administrator, is available under the Custom Objects Area of Clarity.  The user would first create an ‘MUX Migrator’ instance and populate the associated details.  Once ready, they will use the “Populate Stage Content” action which will run a workflow in the background which populates a Staging Table with Source Environments content.  (Blueprints, Views, and Field Level Security) After a successful populate, they would navigate to the “MUX Migrator Content” module where they can decide on what content they want to migrate between environments.  They can select one to many components they wish to migrate. Once the “MUX Migrator Content” sub-object is populated, the user can navigate back to the “Properties” module.  Once a password is populated, the user can use the Actions drop-down to run the “Migrate Content to Environment” workflow.  This will run a process that will migrate the content from the source environment to the target environment. Installation files are not provided with the download.   See Special Instructions. Prerequisites
    • The user will create the migrator instances/run the processes in the Target Environment they wish to migrate content to (E.g. Run this in PROD to migrate the content from a lower environment to PROD)
    • Any attributes that are part of the Blueprints, Views, or Field Level Security must exist in the target environment
    • The user that is utilizing the content must have the following security rights associated to their account
      • XOG rights to all the associated objects
      • View/edit security rights to the MUX Migrator Object and MUX Migrator Content Object
      • View rights to the MUX Migrator Staging Table Object
      • API-Access
      • Process Start or Process AutoStart – All
    • The requested password used is the Clarity User Password, not an SSO password
    Notes
    • Canvas migration is not supported in this version (Pages and Status Report)
  • The Migration Tool for Modern UX Components provides the ability to migrate Blueprints, Views, and Field Level Security between environments.  Previously, the promotion of these components needed to be done manually.  This functionality, to be utilized by an administrator, is available under the Custom Objects Area of Clarity.  The user would first create an ‘MUX Migrator’ instance and populate the associated details.  Once ready, they will use the “Populate Stage Content” action which will run a workflow in the background which populates a Staging Table with Source Environments content.  (Blueprints, Views, and Field Level Security) After a successful populate, they would navigate to the “MUX Migrator Content” module where they can decide on what content they want to migrate between environments.  They can select one to many components they wish to migrate. Once the “MUX Migrator Content” sub-object is populated, the user can navigate back to the “Properties” module.  Once a password is populated, the user can use the Actions drop-down to run the “Migrate Content to Environment” workflow.  This will run a process that will migrate the content from the source environment to the target environment. Installation files are not provided with the download.  See Special Instructions. Prerequisites
    • The user will create the migrator instances/run the processes in the Target Environment they wish to migrate content to (E.g. Run this in PROD to migrate the content from a lower environment to PROD)
    • Any attributes that are part of the Blueprints, Views, or Field Level Security must exist in the target environment
    • The user that is utilizing the content must have the following security rights associated to their account
      • XOG rights to all the associated objects
      • View/edit security rights to the MUX Migrator Object and MUX Migrator Content Object
      • View rights to the MUX Migrator Staging Table Object
      • API-Access
      • Process Start or Process AutoStart – All
    • The requested password used is the Clarity User Password, not an SSO password
    Notes
    • Canvas migration is not supported in this version (Pages and Status Report)
  • A Rego produced document that shows the stock reports and views in Clarity. Also includes views of Power BI reports available in RegoXchange. 193 pages.

  • A one page comparison of of the two Clarity SaaS platforms. Broadcom's GCP vs the Rego AWS hosting platforms. Compares Cloud Infrastructure, Database Engine, Upgrade Control, Scalability, Performance and more.

  • A Quick Reference Guide to assist in creating or adding Calculated Fields or Measures to a Jaspersoft Report.  Calculated Fields or Measures can be created and added to a new or existing Ad-Hoc view by applying formulas to the measures.
  • A Quick Reference Guide to assist in the process of adding filtering for the data to be presented in a Jaspersoft Report.  If a report output contains more information than desired, Jaspersoft Reporting provides an interactive filtering capability so only the necessary data is displayed. The filtering conditions can include fields, numbers, dates and text.  Filters can be added to reports as they are being created or adding to saved views.  Filters cannot be added to a Report.
  • XOG & Query Bridge (XQ) is a 2-in-1 Clarity PPM toolset that provides enhanced functionality and an improved user experience when retrieving and inserting data to/from Clarity PPM environments. XQ is available as a Web-based application and also as a downloadable desktop version that supports both On-premise and On-demand Clarity PPM implementations.   https://xogbridge.com/
  • A Quick Reference Guide with tips on creating a Dashboard in Jaspersoft.  The document walks through the steps and uses screenshots to show the process.
  • A Quick Reference Guide to assist in the process of creating a chart in Jaspersoft.  The guide walks through the steps using screenshots.
  • A Quick Reference Guide to assist in the process of creating a crosstab in a Jaspersoft Ad-hoc report.  The document uses screenshots to walk you through the process.
Go to Top