-
The Milestone Task Dependency portlet shows the milestone task dependency count and has a drilldown to the details. The portlet looks at the dependency impact on milestones, and is not limited to just dependencies that are on different projects. The lag days calculation is based off of the maximum dependency impact and the drilldown portlet (Milestone Task Dependency Details :::: rego_milestone_dependency_det)shows the details for each. -
The Missing Time report provides insight into timesheet compliance by comparing available hours, entered hours, and missing hours for each resource over a selected time period. It can be grouped by resource manager or OBS level and offers flexibility to calculate missing time based on timesheet status or resource availability. The report includes summary charts showing timesheet completion rates and total hours, highlighting completed, partial, and missing timesheets as well as overages across reporting periods. -
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 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 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. -
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. -
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. -
*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)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
-
The My Action Items portlet displays all action items that are assigned or created by the logged in user. This portlet contains action item data including due date and a health stoplight to indicate when action items are late. -
The My Allocations portlet will display the allocations for the logged in user - pulling data from the timeslices. It is used as a quick reference for the users to view their allocations across all of the projects where their allocation is greater than 0 for the specified date range the user wants. This will display both active and inactive projects. -
The My Assignments portlet will display the assignments for the logged in user - pulling data from the timeslices. It is used as a quick reference for the users to view their assignments across all of the projects. The portlet also displays work posted against the task, expressed in Actuals, and remaining work to be done, expressed as an Estimate to Complete (ETC). The Effort Variance reflects what the ETC variance is compared to the last current baseline of the project. -
The My Documents on Projects portlet displays all of the documents the user has uploaded to projects. This portlet provides the user a single place to view documents across multiple projects without having to go into each project individually. This is efficient and time saving for the user. The filter allows the user to narrow their search by Project, File Name, Active Projects and Description. You may also narrow the view to display documents with a created date within a certain date range. Note: In v13, clicking the file name will link to the collaboration tab where the document resides.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy