787 results
-
Learn basic administrative tasks in this basic administration Clarity training, which includes setting up resources, security groups, OBSs, lookups, time reporting periods, fiscal time periods, calendars, jobs, and timeslices. These activities are focused on ongoing support vs. new configuration. Learn how to setup the ModernUX -
A tech trick document that assists you in update Data Source when utilizing the Power BI reports found in RegoXchange. -
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. -
*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
-
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. -
The PPM Data Dictionary Extractor pulls schema and attribute information from each object in CA PPM and places it in a custom object. The following fields provide details information about each attribute in the CA PPM Instance.- Object Name – The name of the object to which the attribute belongs
- Object Code – The external ID of the object to which the attribute belongs
- Attribute Name – The name of the attribute
- Attribute Code – The external ID of the attribute
- Partition Code – The partition to which the attribute belongs
- Table Name – The database table where the attribute is located
- Column Name – The database column name of the attribute
- Data Type – The data type of the attribute
- Data Size – The character limit of the attribute
- Data Scale – The scale of numeric attributes
- Is Active – Specifies if the attribute is active
- Extended Data Type – The extended type of the attribute (ex: lookup, money, etc.)
- Lookup Name – The name of the attribute’s lookup
- Lookup Type – The external ID of the attribute’s lookup
- Default Value – The default value assigned to the attribute
- API Alias – The REST API alias assigned to the attribute
- Max Value – The maximum value accepted by the attribute
- Min Value – The minimum value accepted by the attribute
- Curve Name – The name of the Curve for Time-Scaled value attributes
- Curve Type – The type of the Curve for Time-Scaled value attributes
- Is Custom – Is the attribute a stock attribute or custom
- Is Auto-Numbered – Is auto-numbering enabled for the attribute
- Is Multi-Valued – Is the attribute a multi-valued lookup
- Is DWH Enabled – Is the attribute enabled for export to the data warehouse
- Is Editable – Is the attribute editable or read-only
- Is Required – Is the attribute required
- Is Virtual – Is the attribute a virtual attribute
- Is Private – Is the attribute a private attribute used by the application behind the scenes
-
This training document is a Rego Consulting Quick Reference Guide to assist with General Navigation in Clarity’s Modern User Experience. This doc references version 16.0 views. Doc reviews the Menu Bar and User Tool Bar. -
A Quick Reference Guide to assist in the use of Blueprints/Channels to access external sites, applications or Classic PPM in the Modern UX of Clarity. Reviews the configuraton process. -
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. -
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. -
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)
