RegoXchange
  • The process notifies resource who has been added to investment today and allocation is greater or equal to 100%. The process is on-demand and would require the user to have appropriate rights to run the process. Process should be scheduled as daily once job.
  • This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date.  Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox.  The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date.  Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE:  The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar.  The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account.  For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero.
  • When a task is marked as complete the process looks to any tasks that are dependent on the newly completed task.  If a task is marked as “Not Started” and all of the dependency tasks are marked as complete then the process will change the task status to “Started” and email all resources that are assigned to the task that has started. The process notifies resources that a task is ready to start and saves the project manager the manual effort of updating dependent tasks.  NOTE:  The process relies on task dependencies and is most useful in those environments where task dependencies are managed.
  • The Grant Booking Manager Rights to Book Resources workflow provides a resource’s Booking Manager with the rights to hard book a resource to a project.  This workflow will remove unused rights, and then grant the rights needed to allow for booking of resources. The workflow also has the ability to add rights to not only the resource but also the resource manager, and resources that are assigned as proxies.  If this functionality is not needed, it can easily be removed.
  • 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 Time Tracking Stalker - RM workflow process automatically sends an email to Resource Managers for each one of their resources that have not submitted their timesheet for a prior open time period, thus informing the RM if their resources are submitting their timesheets on time. Project Managers will also benefit since the notifications will help to ensure that time is being posted against their projects in a timely manner, helping to provide them with an accurate view of time expended on the projects.
  • 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 Project Close Process workflow process aides the Project Manager in some routine close out tasks that accompany every project. Marking the project inactive starts the process and it will continue down one of two paths:
    1. Once the project is inactive, the process will then check to see if there is no remaining estimate to complete (ETC) still on the project. If there is ETC leftover, then the process will go into a waiting state for 14 days to allow the project manager to cleanup or to cancel the process if it was done in error. After 14 days, the process will check to see if the project is active. If the project is active, then the process will end. However, if the project is still inactive, the process will continue with the closeout activities even if there is ETC still on the project.
    2. If the project is marked inactive after the initial 14 days of waiting if applicable, then the process will immediately move to the closeout activities.
    The closeout activities include:
    • Turning off time entry for the project, tasks and project members
    • Updates the ETC, proposed ETC, and pending estimates to 0
    • Updates the task status and assignment status to Completed
    • Sets the task, assignment and project finish dates to today’s date only if the finish dates are after the process run date
    • Sets all Risks and Issues to Closed with a resolution of  “## This was closed automatically as part of the project close process ##”
    • Set future hard allocation and allocation finish dates to today when the date is after today’s date
  • 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 Grant Approve Time to Proxy process utilizes the proxy feature within Clarity to assign timesheet approval and edit rights to a proxy for any resources that the user is the current resource manager for. The process, when run, will also remove any timesheet approval and edit rights for any users if the proxy has been removed or the resource manager has changed. This process is used for resource managers that will be out of the office.
    • ITFM Introduction
    • PMO & IT Finance Collaboration
    • Where ITFM and PPM Meet
    • Connecting PPM with ITFM
  • Do you want to know more about building outbound integrations using a flat file placed on an SFTP Server?  Does your organization have an external BI tool like Cognos, Tableau, Domo, or Qlikview? This session will review strategies for getting data into your corporate BI tools.  We will also show Rego's data extraction tool and how it can be used for all outbound file-based integrations to save money and time.
Go to Top