RegoXchange
  • Installation files are not provided with the download.  While the MUX Migration Tool is free, it does require some time by Rego Technical Staff to install.  Approximately 4 hours is required.  If you are current Rego Customer, this time can be applied against a current project if you choose, or against an Ad Hoc SOW/PO you have in place with us. Please reach out to your friendly Rego Account Director to arrange to have the tool installed.  Installation files are not provided with this download.  They will be installed by our staff. If you are currently not a Rego client, we invite you to reach out to us at info@regoconsulting.com and we can arrange to set up an Ad Hoc bucket of hours for this install and any future work we can do for you.
    *Note:  MUX Migrator v2.0 will only work on Clarity versions 16.1.0 and higher.   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. Source to Target Approach 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 to populate a Staging Table with Source Environments content.  (Blueprints, Views, and Field Level Security)
    After a successful populate, they would navigate to the “MUX Configuration” 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 Configuration” 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. JSON Approach The user would first create an ‘MUX Migrator’ instance and populate the associated details.  They would navigate to the “MUX Configuration” 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 Configuration” sub-object is populated, the user can navigate back to the “Properties” module.  The user can use the Actions drop-down to run the “Export JSON” workflow.  This will run a process that will generate a .txt file located in the “JSON File” attribute.  That file can be downloaded from the Source Environment.  The user can then login to the Target Environment.  The user would first create an ‘MUX Migrator’ instance and populate the associated details.  Once the ‘MUX Migrator’ instance is created, they can upload the JSON File that was downloaded from the Source Environment.  The user can use the Actions drop-down to run the “Import JSON” workflow.  This will run a process that will generate read the file located in the “JSON File” attribute and load the configuration into the Target Environment. View Administration The user would first create an ‘MUX Migrator’ instance and populate the associated details.  They would navigate to the “MUX View Administration” module where they can decide on what views they would like to update the creator of.  They can also reset the “default” view displayed when logged in for a resource(s), Security Group(s), or Resource OBS Node(s). 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
      • oView rights to the MUX Migrator Staging Table Object
      • API-Access
      • Process Start or Process AutoStart – All
  • This Roadmap add-on provides configurable Role-based metrics that can be used in the grid view as targets and constraints. Select your valuable roles in the “targets” and once selected, the “sync” button will bring in any current allocations against projects and allow editing any of the total numbers directly in a scenario.  This will provide deeper insights into impacts of plans on teams/resources in addition to the out of the box money and time constraints.
  • 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.
  • The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again.
  • View Rate Matrix is a grid portlet that provides users a single place to view all the rates defined across multiple rate matrix without going to administration tab. Each Matrix may be defined with different columns (ex: Charge Code, Client, Department, Entity, Input type Code etc). This portlet dynamically brings only the columns associated with that rate matrix and provides the detailed information. User can view information related to one matrix at a time.
  • This Process sends an email to every Action Item Assignee where the Due Date/Time has passed and the Status is either Open, or In Progress.  Users may want to modify this stalker to include Status = Deferred.  In addition, the Resource Manager for the Assignee receives a copy of the email. In order to generate emails, the SMTP gateway must be up and running and Resources must have a valid email address.
  • The portlet displays posted time by project for the logged in user based on time period and date range.  This allows the user to see at a glance their ETC and actuals on the projects. The portlet displays the Total Allocation and Total Actuals to Date for the user on the projects they are allocated/assigned to.  The actuals are displayed per month in the form of TSVs.
  • The Communications Object allows a user to send an html-based email to all users on a project, in a security group, or to individual users directly from Clarity.  An email can be sent by creating a new entry on the Communication List page, upon saving a new entry the email process with trigger and send the email. Auto Start Solution: An email can be sent by creating a new entry on the Communication List page, upon saving a new entry the email process with trigger. On Demand Solution: All emails could be sent together as a broadcast communication by running the process manually from the Organizer. This process could also be scheduled to run on a specific time using Jobs The table below describes the available columns on the object.
    Column Label Description
    From Who the email is coming from
    Sent To Individual users the message should send to
    Send to Group Security groups the message should send to (users within the security groups)
    Message Project Team Should this message be sent to a project team
    Associated Investment If Message Project Team is checked, which project should the team list be pulled from
    Message Subject Subject line of the email
    Message Content Body of the email (html)
    Message date Internal code used by the query
    Either of the on-demand process or auto start process should be active at a time. The package provides two Processes: 1.  Send Notification (ID:rego_send_notification) This is an auto start process. The notification is sent immediately when a new entry is created on the Communication object. Only one email notification will be sent for one entry. Any updates to the same entry will not trigger any new notifications. 2.  Email Communication (ID:rego_email_comm) This is an on-demand process that could be run from the Organizer. This send notification to all the entries on the Communication objects for which a communication was not already sent. This process does not have a Primary object. The processes are designed to work both in Oracle and Postgres environment. If the DB vendor information from Properties.xml is Postgres the SQL query for Postgres will be called. If not, the default SQL is Oracle. Important Note: Either of the processes should be active for an Implementation. If both the processes are active the on-demand process has no effect and will never send any communication. All object entries have a sent flag which will be marked whenever a notification is sent. Both the processes set the same flag on the object instance. Only with admin DB rights this flag could be overwritten. Object Name:Communication Object ID: rego_communication Flag Attribute Name: Sent (Id: rego_sent)
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
  • The Lock Inactive Users workflow process will automatically lock all user accounts when their last login date was more than 60 days ago.  The process can be scheduled to run daily or can be run on demand when resource account cleanup is needed.
  • Portlet to quickly show License Compliance for all license types.  Simply Enter your License Limits in the filter – The portlet will display the three license types in a grid format with compliance chart and RYG Icons.
Go to Top