-
Resource Availability by Skill over Time is a grid portlet that provides Resource Managers a single place to view Resources’ skill sets along with their availability (hrs.) over a period of time. This report also displays the assigned Investments to date and the Actual hours to date for the Resource on those respective Investments. Users can further narrow their search by Skill Name, Resource Name, Project Manager, Start Date, End Date and Period Recurrence. -
Resource Availability by Skill over Time is a grid portlet that provides Resource Managers a single place to view Resources’ skill sets along with their availability (hrs.) over a period of time. This report also displays the assigned Investments to date and the Actual hours to date for the Resource on those respective Investments. Users can further narrow their search by Skill Name, Resource Name, Project Manager, Start Date, End Date and Period Recurrence.
-
Resource Availability by Skill over Time is a grid portlet that provides Resource Managers a single place to view Resources’ skill sets along with their availability (hrs.) over a period of time. This report also displays the assigned Investments to date and the Actual hours to date for the Resource on those respective Investments. Users can further narrow their search by Skill Name, Resource Name, Project Manager, Start Date, End Date and Period Recurrence.
-
This is a list of 12 typical maintenance items that should be completed for Clarity on an annual basis. There is also a short list of items that should be completed periodically depending on client policies. -
This training document is a Rego Consulting Quick Reference Guide to assist with Time Entry Administration Settings for Timesheets. This doc references version 16.0.3 views. Document provides detail on Timesheet Options for the Modern UX and how to enable end user column configuration. Detail is also provided on how end users may configure their timesheet view. -
Manage default views for new users based on security groups or publish a view to all users in a specified security group. For more details, please refer to the detailed documentation.
-
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)
- Navigate to the process called Admin - MUX Views - Change Ownership.
- Navigate to the Start Step tab, Click on the Update Owner action, and click the Custom Script Parameters tab.
- Enter the Resource ID for the current view owner into the currentOwnerId parameter.
- Enter the Resource ID for the new owner into the newOwnerId parameter.
- If you want to update a specific view only, enter that in the viewCode parameter.
- 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
- 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
- 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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy