RegoXchange
  • 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.
  • The Timesheet Approval - RM and PM process is an auto-start process that begins once the resource submits his or her timesheet. This process provides a checks-and-balances style to ensure that all resources entering time have entered the 40 hours. Once the timesheet is submitted, the process will lock the user’s timesheet to prevent editing. The process will then select the next action based on three different factors:
    1. The timesheet has less than 40 hours.
    2. The timesheet has 40 or more hours.
    3. The resource’s availability is less than 8hrs/day.
    If the user has submitted a timesheet with less than 40 hours, then the process will email the user informing him/her of issue, unlocks the timesheet, and changes the status to “Returned”. If the user has an availability of less than 8hrs/day or the timesheet has 40 or more hours, then an action item will be sent to the resource manager informing him/her of the timesheet. If the resource manager (RM) AND project manager (PM) approves the action item, then the process will approve the timesheet and unlock the timesheet. However, if the RM or PM selects “Return” on the action item, then the process will return the timesheet, mail the user that informing him/her that the timesheet has been returned, and unlock the timesheet.
  • The Status Report Publish workflow process pushes values from the status report sub-object to the parent project object. The process is started when the user ticks the “Publish” Boolean field on the status report (custom field added). This workflow will update the project object with the overall status indicator, the status comment, the previous overall status, and the as of date. This eliminates the project manager having to update the fields in both the status report and the project overall.
  • The Grant RM Timesheet Edit Rights workflow process can be run through the "Execute a Process" job.  The workflow will execute a query that gives a Resource Manager Timesheet Edit rights for their resources. Timesheet Edit rights are not inherent for Resource Managers when they are named as an individual’s resource manager.
  • The Grant RM Timesheet Edit Rights workflow process can be run through the "Execute a Process" job.  The workflow will execute a query that gives a Resource Manager Timesheet Edit rights for their resources. Timesheet Edit rights are not inherent for Resource Managers when they are named as an individual’s resource manager.
  • The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field.  This process can be modified to grant project edit rights to any user within a project field.
  • The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
  • This grid portlet shows the OBS name and ID along with the associated hierarchy, both as an aggregated view along with each of the levels broken out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Branch Branch of the OBS
    OBS Type OBS to use
    OBS Path Path of the OBS
  • This portlet displays the monthly allocation per resource. The PM can view by the RM or the resource to get the data for monthly resource allocations. The table below describes the available filter fields in the portlet.
    Column Label Description
    Work Effort Manager Manager of the Investment the Work Effort is on
    Work Effort Active Active status of the Investment the Work Effort is on
    Resource Resource’s Name
    Internal Resource ID Resource’s ID
    Zero Allocation Show Allocations that equal zero
    Open for Time Entry Is the Resource Open for Time Entry
    Resource Active Resource’s Active status
    Role Resource’s Primary Role
    OBS Unit Resource’s OBS
    Start Allocation Start Time to filter by
    End Allocation Finish time to filter by
       
  • This Portlet produces a Grid View of Resources using total Resource Allocation from each Project’s Team / Staff, per month; output is expressed as a %.  Users can specify which Resource OBS to use as a Filter (unit and descendants is assumed) as well as a Start/End Date.
  • This Portlet produces a Stacked Chart of Projects using total Resource Allocation from each Project’s Team / Staff, per month.  Users can specify which Resource OBS to use as a Filter (unit and descendants is assumed) as well as a Start/End Date Range.
  • This portlet displays a Pie Chart of a Portfolio’s Realized Benefits partitioned into pie slices by the portfolio’s Investments’ Objectives. Clicking on any pie slice (Objective) drills-down into a portlet that lists the Investments that make up that slice.
Go to Top