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 Rego Group Rights portlet is a useful list view for functional administrators.  It provides a flat view of all the Global, OBS and Instance rights that have been granted to all the groups in Clarity. It can be further filtered by just the rights type and/or the security group. It is also possible to export out to file in spreadsheet (csv, xlsx) or PowerPoint formats with OOB Clarity functionality.

Rego’s Clarity Adoption Metrics package consists of two sets of metrics: Project metrics, and Resource metrics. Project metrics measure how effectively project managers are using Clarity to manage their projects. Resource metrics measure how effectively resource managers are using Clarity to manage resources. Metrics are scored on a scale of 0 to 5, with higher scores indicating greater adoption and use. All metrics can be viewed numerically or graphically, and can be broken out by OBS. In addition, metric data can display as a 12-month rolling history to help identify trends. Project metrics can also display by lowest / highest adoption rates for a specific resource metric or all resource metrics. There is a variety of way to view the Adoption Metric data, therefore, Rego has made this simple by creating an Adoption Metrics object that contains multiple tabs.  Each tab displays one or more of the Project or Resource Adoption Metrics.  Based on the nature of the Metrics some tabs will allow the ability to use a pull down menu to select a specific Adoption Metric.   There is also a Metrics trending view that pulls monthly snapshots of the metrics. Project metrics consist of the following: Project Status Reporting – Measures how well PMs create and publish project status reports. Project Risk Adoption – Measures how well Risks are being used and managed. Project Issue Adoption – Measures how well Issues are being used and managed. Project Schedule – Measures how well PMs create tasks and keep the project schedule current. Project Baseline – Measures whether or not baselines exist. Project Zero ETC’s – Measures how well the PM assigns resources to tasks with ETCs. Project Past ETC’s – Measures how many improperly scheduled tasks the PM has. Project Milestone / Key Tasks – Measures how well PMs create and manage Milestones / Key Tasks. Project Schedule Variance – Measures how effectively PMs manage their schedules. Project Effort Variance – Measures how effectively PMs manage their project efforts. Project Budget Variance – Measures how effectively PMs manage budgets or cost plans. Project Unfilled Roles – Measures project roles with allocations that are already started or starting within the next 30 days. Project Data Quality – Measures how effectively PMs complete the Description, Stage, Progress, Objective, and Sponsor/Business Owner fields. Project Commitment – Measures the hard allocations for a project over a two week time frame. Resource Metrics consist of the following: Resource Clarity Usage – Measures how often users log into Clarity. Resource Timesheet – Measures if timesheets post in a timely manner. Resource Allocation – Measures how well RMs keep total resource allocations within the expected range for future time periods. Resource Actualy Utilization – Measures how well Resource allocations match actuals. Resource Allocation Date in the Past – Measures how many resources are open for time entry with dates in the past. Resource Data Quality – Measures how well RMs complete the Resource Manager and Primary Role fields and optionally the Skill and Employment Type fields. Resource Commitment – Measures how much resource available time is committed to projects.