-
The Projects Marked for Deletion portlet displays information about projects that are currently pending deletion but excludes templates and programs. This portlet provides an easy way to view all projects that are marked for deletion before the background job actually erases them. The portlet provides all necessary information as well as the project manager in case there are questions about why the project was marked for deletion. -
The Projects That Should Be Closed portlet displays all projects that have been created before the specified filter date and has had no new time, tasks, or risks/issues updated after the dates specified in the filter. This can assist in identifying projects that are completed or cancelled and should be closed. The table below describes the available columns in the portlet. Column Label Description Project Name Name of the project PM Manager of the project Created Date Created Date of the project Start Start Date of the project Finish Finish Date of the project Created Date Check Identifies if the project meets the Created Before (Days) filter Risks/Issues Check Identifies if the project meets the Risk/Issues – Days Back filter Task Check Identifies if the project meets the Task – Days Back filter Time Check Identifies if the project meets the Time – Days Back filter Project Check Identifies if the project meets the portlet filter Criteria id Internal code used by the query -
The Projects That Should Be Closed portlet displays all projects that have been created before the specified filter date and has had no new time, tasks, or risks/issues updated after the dates specified in the filter. This can assist in identifying projects that are completed or cancelled and should be closed. The table below describes the available columns in the portlet. Column Label Description Project Name Name of the project PM Manager of the project Created Date Created Date of the project Start Start Date of the project Finish Finish Date of the project Created Date Check Identifies if the project meets the Created Before (Days) filter Risks/Issues Check Identifies if the project meets the Risk/Issues – Days Back filter Task Check Identifies if the project meets the Task – Days Back filter Time Check Identifies if the project meets the Time – Days Back filter Project Check Identifies if the project meets the portlet filter Criteria id Internal code used by the query -
The Projects That Should Be Closed portlet displays all projects that have been created before the specified filter date and has had no new time, tasks, or risks/issues updated after the dates specified in the filter. This can assist in identifying projects that are completed or cancelled and should be closed. The table below describes the available columns in the portlet. Column Label Description Project Name Name of the project PM Manager of the project Created Date Created Date of the project Start Start Date of the project Finish Finish Date of the project Created Date Check Identifies if the project meets the Created Before (Days) filter Risks/Issues Check Identifies if the project meets the Risk/Issues – Days Back filter Task Check Identifies if the project meets the Task – Days Back filter Time Check Identifies if the project meets the Time – Days Back filter Project Check Identifies if the project meets the portlet filter Criteria id Internal code used by the query -
The Resource Rights portlet displays information for all global, OBS, and instance-based rights that are present in the system. This portlet can easily determine who has certain rights and what is causing them to retain a certain license status (creator, studio developer, etc). -
The Resource Vacation Details portlet allows a resource manager, or administrator, to see a resource’s calendar at a glance, displayed by week or month for a selected time period. This portlet shows the Resource Name, Resource Manager, Calendar, H (holiday), and V (vacation) hours for the select time frame. -
The Resource Vacation Details portlet allows a resource manager, or administrator, to see a resource’s calendar at a glance, displayed by week or month for a selected time period. This portlet shows the Resource Name, Resource Manager, Calendar, H (holiday), and V (vacation) hours for the select time frame.
-
The Resource Vacation Details portlet allows a resource manager, or administrator, to see a resource’s calendar at a glance, displayed by week or month for a selected time period. This portlet shows the Resource Name, Resource Manager, Calendar, H (holiday), and V (vacation) hours for the select time frame.
-
The Resources in Security Groups portlet shows security group information for resources. (Note: the information displayed is dependent on what the user has security rights to view.) The portlet displays the Group, Group ID, if the Group is active, Resource, User Name and User Status. This portlet also includes the ability to filter on a specific group or resource, by whether the group is active, by user status or OBS. -
*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 Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again. -
The Update Email Ids workflow sets all users’ email addresses to non-working by appending a “ZZZZ” to the end of the email address. This process is used for when there are refreshes to your Development or Testing environments and do not want emails going to users. When complete, the log will display the total amount of email addresses updated. A second process is included in this workflow that will revert the email addresses to remove the “ZZZZ” added in the first workflow. In some instances, the process may be run in error, or you may want to send emails from a Development or Testing environment; using this second process you will be able to enable all emails again.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy