1906 results
-
The Missing Time report is a transaction based Jaspersoft report that does not require the Load Jaspersoft Datawarehouse job to be run. The report will pull real-time data from the transaction tables in Clarity. This report can be run from either the Advanced Reporting or Reports and Jobs area within Clarity. The Missing Time report displays resource available hours, timesheet hours entered, and timesheet hours missing by resource and time period. The report can be grouped by resource manager or OBS level. The report also has an option to calculate missing time based on timesheet status or resource availability. The charts include a summary of timesheets across the periods included in the report. The Timesheet Count Summary displays the number of timesheets that are completed, partially completed, or missing for the time periods. The Timesheet Hours Summary displays the number of hours grouped by resource availability, timesheets entered, timesheets missing, and overage. -
The Missing Time by OBS portlet displays all missing or late timesheets for resources staffed within a specific OBS. Resources will be included if they are open for time entry, have the track mode of ‘Clarity’ and have a timesheet that is not posted. The portlet accommodates for hire and termination dates. Also, the portlet only shows resources that the active user has the security rights to view. Administrators and the Project Management Office may use this portlet to determine the timesheet status of all resources within a specific OBS in open time periods. This portlet allows a user to quickly search by OBS and view all timesheets under that area. After selecting the OBS, the user can also filter on time period start date, Resource Manager and/or Project Manager. The portlet will display a ‘Stop Light’ indicator based on timesheet status, the status, period start, Resource Name, Resource Manager and any actual hours entered for the timesheet. -
The Missing Time by OBS portlet displays all missing or late timesheets for resources staffed within a specific OBS. Resources will be included if they are open for time entry, have the track mode of ‘Clarity’ and have a timesheet that is not posted. The portlet accommodates for hire and termination dates. Also, the portlet only shows resources that the active user has the security rights to view. Administrators and the Project Management Office may use this portlet to determine the timesheet status of all resources within a specific OBS in open time periods. This portlet allows a user to quickly search by OBS and view all timesheets under that area. After selecting the OBS, the user can also filter on time period start date, Resource Manager and/or Project Manager. The portlet will display a ‘Stop Light’ indicator based on timesheet status, the status, period start, Resource Name, Resource Manager and any actual hours entered for the timesheet.
-
The Missing Time by OBS portlet displays all missing or late timesheets for resources staffed within a specific OBS. Resources will be included if they are open for time entry, have the track mode of ‘Clarity’ and have a timesheet that is not posted. The portlet accommodates for hire and termination dates. Also, the portlet only shows resources that the active user has the security rights to view. Administrators and the Project Management Office may use this portlet to determine the timesheet status of all resources within a specific OBS in open time periods. This portlet allows a user to quickly search by OBS and view all timesheets under that area. After selecting the OBS, the user can also filter on time period start date, Resource Manager and/or Project Manager. The portlet will display a ‘Stop Light’ indicator based on timesheet status, the status, period start, Resource Name, Resource Manager and any actual hours entered for the timesheet.
-
Missing Time by OBS report displays Resource whose timesheets are missed. There is Clustered Column Chart which displays Timesheets count by Resource. Also, there is table view of Resource, Resource Manager, Time Period Start and Finish Dates, Total Hours and Timesheet status. User can narrow their search by OBS Type & Path and Project Manager, Resource Manager, Resource, Timesheet Status and Time Period Start Date (Relative or Specific Date Range). -
The Missing Time by PM portlet displays all missing or late timesheets for resources staffed on a project where the logged in user is the project manager. Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Project managers may use this portlet to determine the timesheet status of resources staffed on their projects. You may narrow the results by filtering by resource manager, period start, resource name, or status. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet. -
The Missing Time by PM portlet displays all missing or late timesheets for resources staffed on a project where the logged in user is the project manager. Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Project managers may use this portlet to determine the timesheet status of resources staffed on their projects. You may narrow the results by filtering by resource manager, period start, resource name, or status. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet.
-
The Missing Time by PM portlet displays all missing or late timesheets for resources staffed on a project where the logged in user is the project manager. Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Project managers may use this portlet to determine the timesheet status of resources staffed on their projects. You may narrow the results by filtering by resource manager, period start, resource name, or status. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet.
-
Missing Time by PM report displays Resources whose timesheets are missed by Project Manager. There is Clustered Column Chart which displays missed timesheets count by Project Manager. Also, there is table view of Project Manager, Resource, Time Period Start and Finish Dates, Total Hours and Timesheet status. User can narrow their search by OBS Type & Path and Project Manager, Resource Manager, Resource, Timesheet Status and Time Period Start Date (Relative or Specific Date Range). -
The Missing Time by RM portlet displays all missing or late timesheets for resources for which the logged in user has resources (logged in user is the RM). Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Resource managers may use this portlet to determine the timesheet status of all resources in open time periods. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet. -
The Missing Time by RM portlet displays all missing or late timesheets for resources for which the logged in user has resources (logged in user is the RM). Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Resource managers may use this portlet to determine the timesheet status of all resources in open time periods. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet.
-
The Missing Time by RM portlet displays all missing or late timesheets for resources for which the logged in user has resources (logged in user is the RM). Resources will be listed if they are open for time entry, have a track mode of Clarity, and have timesheet that is not posted (accommodates for hire and termination dates). Resource managers may use this portlet to determine the timesheet status of all resources in open time periods. The portlet will display an indicator based on timesheet status, the status, period start, resource name, and actual hours for the timesheet.
-
Missing Time by RM report displays Resources whose timesheets are missed by Resource Manager. There is Clustered Column Chart which displays missed timesheets count by Resource Manager. Also, there is table view of Resource Manager, Resource, Time Period Start and Finish Dates, Total Hours and Timesheet status. User can narrow their search by OBS Type & Path, Resource Manager, Resource, Timesheet Status and Time Period Start Date (Relative or Specific Date Range). -
MITRE will discuss the recent revival of Clarity enabled by an upgrade and elimination of on-premise, non-compliant customizations and their success story. The project leader will address the steps to execute this transformation and the approach taken towards organizational change management. -
MITRE will discuss the recent revival of Clarity enabled by an upgrade and elimination of on-premise non-compliant customizations and their success story. The project leader will address the steps to execute this transformation and the approach taken towards organizational change management. -
Broadcom’s Laureen Knudsen and Noël Rodriguez discuss the current and evolving state of the PMO. -
A presentation slide deck from Rego University 2022. This document is course material for an Advanced Admin class for Clarity’s Modern UX. Focus on this class was on Blueprints.- A presentation slide deck from Rego University 2022. This document is course material for an Advanced Admin class for Clarity’s Modern UX. Focus on this class was on Blueprints.
- Pages
- Modules - Channels
- Rules
- Fields Level Security
- Actions
- A presentation slide deck from Rego University 2022. This document is course material for an Advanced Admin class for Clarity’s Modern UX. Focus on this class was on Blueprints.
-
A presentation slide deck from Rego University 2022. This document is an outline of the basic administration of Clarity’s Modern User Experience.- Introduction
- First time setup
- Activating Modern UX and Timesheets
- Creating a Link to the Modern UX in the Classic Home Menu
- Navigation and modules
- Blueprints
-
Transitioning to the modern UX or implementing Clarity for the first time? Learn how to configure Modern UX: - First time setup - navigation and modules - Blueprints (basic) - Personalize the UI/Announcements -
Clarity's Modern Experience has been a game changer for end-users, but did you know there are some fantastic capabilities for admins? Come to this session to learn about how to set up the modern experience, the module capabilities, blueprints, fields/attributes, and how to personalize your experience. -
Clarity's Modern Experience has been a game changer for end-users, but did you know there are some fantastic capabilities for admins? Come to this session to learn about how to set up the modern experience, the module capabilities, blueprints, fields/attributes, and how to personalize your experience. -
This Tech Trick covers instructions for modifying the default colors of a Chart in Jaspersoft Studio Reports using a dynamic expression. It includes step-by-step instructions for an example bar chart color change. -
Monthly Actuals - Admin is a standard calendar view of actuals posted by a user on each day of the selected month. Actuals also includes timesheets that haven’t been submitted/posted yet. Actual hours on the report are tied to user's availability i.e. when user has 0 availability (Saturday/Sunday/Holiday) then actuals are also greyed out. -
Monthly Actuals -User View is a standard calendar view of actuals posted by logged in user on each day of the selected month. Actuals also includes timesheets that haven’t been submitted/posted yet. Actual hours on the report are tied to user's availability i.e. when user has 0 availability (Saturday/Sunday/Holiday) then actuals are greyed out. -
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in. -
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in.
-
The Move Role to Team/Assignment process takes the role from the resource object and pushes that information into the team and assignment objects when the role is NULL on the team and assignment objects. This happens normally, assuming a resource has their primary role populated. This process is needed if a resource or set of resources were added to projects without having their primary role filled in.
-
Aligning work to organizational strategy is a fundamental requirement in today’s ever-changing marketplace. High-performing organizations, however, are moving beyond basic connections to introduce strategic hierarchies that are tied at various levels to real measurements of business value via Objectives and Key Results (OKRs). Join our Guides as they present key concepts, best practices, and the evolution of strategic alignment. -
The Cost Type field was introduced in CA PPM 13.3, but had some limitations because it wasn’t available in certain financial areas. The CA PPM 14.3 release includes the addition of Cost Type in the Cost/Rate Matrix, Chargebacks, Transactions and WIP Adjustments. This Technical Trick assists you in moving from Charge Code to Cost Type. -
Many organizations want to transition to a more product-centric delivery model but struggle with how to get started. This session discusses key success factors of Broadcom’s own project-to-product transition with an aim to resolve issues facing your organization. -
The Multi-Value Filter in Query-Based technical trick document provides an overview of how to create a multi-value lookup in a portlet filter, where the field is a parameter within the query. If the query imbeds the parameter normally, the portlet will only be able to have a single selection of that parameter. This technical solution will enable you to make these parameters multi-selects. -
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)
-
*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
-
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.
-
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.
