-
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 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 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 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 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 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 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 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.
-
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.
-
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.
-
*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 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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy