1906 results
-
Hierarchies and Roadmaps are two powerful capabilities that Clarity has brought to the market. While they work great independently, have you experimented with how they can work together, even better? In this session, come and learn how these two capabilities can complement each other by working in concert giving you both planning and execution insights! -
A tech trick document that assists you in update Data Source when utilizing the Power BI reports found in RegoXchange. -
*Note: MUX Migrator v2.0 will only work on Clarity v16.1.0+ 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)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. 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
-
Learn advanced administrative development tasks—including Objects and Fields, Object Portlets, Basic Processes, and XOG. In the last portion of this class we will walk through the high level data model within the Clarity database and walk through some basic NSQL portlets. This is a more technical class focusing on basic configurations - designed for non-technical people. -
The Adoption Dashboard is designed to enhance data integrity and project tracking within Clarity by providing insights into how well users are populating and managing their project and resource data. Features: · Project Data Quality Evaluate the accuracy of project status reporting, risk, issue tracking, and schedule adherence. · Resource Data Quality Assess how well resource managers are managing timesheets, allocations, and actual utilization. · Adoption Scoring View Rate the consistency of data entry across projects and resources on a scale of 0-5, helping identify areas needing improvement. · Variance Analysis View Track discrepancies in project schedules, effort, budgets, and resource commitments. · Compliance Monitoring Ensure that all necessary project and resource data is up-to-date, aiding in more informed decision-making and better project outcomes. -
Evaluate resource allocations, identify bottlenecks, and ensure optimal resource utilization across projects and teams. Report Views include: • Over Allocation • By Project • By People • Project Resource Details • No Allocations by Project • No Allocations by People The main file will access data through custom queries created via Rego Odata connector. -
The Power Filter Sync functionality allows users to define rules for syncing investments to Roadmaps or Hierarchies on a scheduled (and on-demand in Roadmaps only) basis. Users may choose one or more saved views from investments that are allowed on the Roadmap/Hierarchy to define the list of investments they want that Roadmap/Hierarchy to contain. If the option to Keep Synced with Power Filter is set to Yes, then each time the process runs, the Investments returned by the saved views will be added to the Roadmap/Hierarchy if they don’t exist there already, and any investment not found in the saved views will be removed. -
Are you using Clarity's roadmap leveraging some of the best and most common practices found across industries? Come to this session to learn about how the roadmap works, out of the box. We will cover how to configure views, targets, widgets, boards and more! You will leave with great ideas you can bring back to your organization! -
This session will aligning you with some of the best and most common practices for using Clarity's Resource Management capabilities. Come and learn about the cababilities that come out of the box for resource insights like allocations, assignments, availability and more. Additionally, tips and tricks will be discussed leaving you with a toolkit of ideas for your organization! -
A Rego Training deck that reviews the use of Hierarchies in Clarity PPM’s Modern UX.- Hierarchies in Clarity PPM can be used to create one or more hierarchies that define relationships between various investments. Each hierarchy includes an investment tress card made up of multiple cards.
- A parent-child relationship between investment cards help stakeholders understand the dynamics of the investments. Stakeholders can use the Hierarchies page to view all the hierarchies in the organization.
- Hierarchies can include different investment types such as; ideas, projects, and custom investments with configurable cards by investment type.
- Hierarchies can display rolled up aggregation metrics.
- Hierarchies can be exported to PDF.
-
A presentation slide deck from Rego University 2021. This course covered enabling the Modern UX and timesheets, creating a link to the MUX in the classic home menu, creating Blueprints and more. -
Timesheet compliance is a dashboard containing multiple visualizations that shows timesheet compliance data under various scenarios. Dashboard shows count of timesheets grouped by Status and total available timesheets. % Time Compliance – Gauge graph that shows percentage of completed timesheets against overall timesheets. Compliance by Resource Manager – Grid section that shows percent timesheet compliance by resource manager. Timesheet count by Employment type and Timesheet Status – Stacked column chart, each column represents Employment type and sections of the column represent count of timesheets by Status. Count of Timesheets by Months – Stacked column chart, each column represents a month and sections of the column represent count of timesheets by Status. Dashboard also const of two grid sections displaying number of Open timesheets by Organization and Vendor.
