-
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. -
The My Issues portlet displays all issues within active project that the logged in user is assigned to. The portlet provides the logged in user a single place to view issues across multiple projects without having to go into each project individually. The filter then allows the user to narrow their search by Issue ID, Issue Name, Project ID, Project Name, and Issue Status. You may also narrow the view to display issues with a target resolution date within a certain date range. -
The My Missing Time portlet displays all open time periods for which the logged in user (assuming they are open for time entry with a track mode of Clarity) has a timesheet that is not posted (accommodates for hire and termination dates). The portlet is used as a quick reference for users to view their missing time. -
The My Resource Count by Project portlet displays project information, total team count and the current user’s resource count assigned to each project. The user may narrow the results by filtering on project name, manager, status, team count, managed resource count or percentage managed resource count. Using this portlet, resource managers can quickly identify which projects their resources are allocated to without having to navigate to each resource individually. Not only does this portlet display the overall team count on the project (team count), but it also displays the managed resource count (logged in user’s number of resources allocated to the project) as well as the percentage of managed resource count to team count. -
The My Resource Vacation portlet allows a resource to view the current logged in users' annual vacation allowance, as set by the resource manager, against the resource vacation calendar hours and actual posted timesheet hours. The portlet is useful for determining the amount of hours a resource has requested off and has remaining. The portlet also ensures the resource has accounted for all annual vacation allowance hours in the calendar and has posted time for all past calendar request hours. -
The My Resource Vacation Details portlet returns the logged in users calendar at a glance by week or month for a selected time period. It shows the Resource Name, Resource Manager, Calendar, H (holiday), and V (vacation) hours for the select time frame. -
The My Resources’ Time by Quarter and Type portlet displays all subordinate resources’ time by type for each quarter. The portlet is able to display either actuals or estimates for each resource. This portlet allows the resource manager to see how each of his or her resources’ time is utilized by project type. The user may filter on a specific date range (quarter) and resource OBS.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy