RegoXchange
  • The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date).
  • The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date).
  • The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date).
  • The Dashboard: Open Risks portlet gives an overview of all risks that are not closed or resolved for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet sorts the risks first by priority and then by target date.  It displays the name, owner, target date, probability impact, and priority.
  • The Dashboard: Open Risks portlet gives an overview of all risks that are not closed or resolved for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet sorts the risks first by priority and then by target date.  It displays the name, owner, target date, probability impact, and priority.
  • The Dashboard: Open Risks portlet gives an overview of all risks that are not closed or resolved for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet sorts the risks first by priority and then by target date.  It displays the name, owner, target date, probability impact, and priority.
  • The Dashboard: Phase Gantt portlet gives an overview of all WBS level 1 tasks or milestones for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet displays the name, and a graphical representation of the timeline for the phases. The date range may be configured by day, month, year, or quarter. The start date may also be configured to any date or a relative date (start of current month, start of next year, etc).
  • The Dashboard: Phase Gantt portlet gives an overview of all WBS level 1 tasks or milestones for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet displays the name, and a graphical representation of the timeline for the phases. The date range may be configured by day, month, year, or quarter. The start date may also be configured to any date or a relative date (start of current month, start of next year, etc).
  • The Dashboard: Phase Gantt portlet gives an overview of all WBS level 1 tasks or milestones for a single project.  The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab.  The portlet displays the name, and a graphical representation of the timeline for the phases. The date range may be configured by day, month, year, or quarter. The start date may also be configured to any date or a relative date (start of current month, start of next year, etc).
  • The Give PM Collaboration Manager Rights workflow process can be run through the "Execute a Process" job.  The workflow will execute a query that gives a Project Manager the Collaboration Manager rights to their projects. Often times, PMs are not set as Collaboration Managers when the project is created. This script can be run to automatically give a PM the Collaboration Manager rights to their projects, without having to go through the projects one by one.
  • The Give PM Collaboration Manager Rights workflow process can be run through the "Execute a Process" job.  The workflow will execute a query that gives a Project Manager the Collaboration Manager rights to their projects. Often times, PMs are not set as Collaboration Managers when the project is created. This script can be run to automatically give a PM the Collaboration Manager rights to their projects, without having to go through the projects one by one.
  • The Give PM Collaboration Manager Rights workflow process can be run through the "Execute a Process" job.  The workflow will execute a query that gives a Project Manager the Collaboration Manager rights to their projects. Often times, PMs are not set as Collaboration Managers when the project is created. This script can be run to automatically give a PM the Collaboration Manager rights to their projects, without having to go through the projects one by one.
Go to Top