RegoXchange
  • The Timesheet Smoothing Process Workflow kicks-off when an individual timesheet is Submitted.  It splits each transaction on the timesheet when total timesheet actuals exceed total weekly availability for the resource.  Total weekly availability is determined by multiplying resource availability rate by the number of workdays in the week.  Non-workdays include weekends, holidays, PTO, and other scheduled days off, as set on the resource calendar.  If timesheet actuals <= total weekly availability, then the timesheet remains unchanged.  But if timesheet actuals > total weekly availability, then the following occurs. Each timesheet transaction is reduced by a calculated percentage that will reduce the total regular hours to equal the total weekly availability.  Then the remaining transaction hours are placed in a “Split” row for that task on that day, with an Input Type Code set based on a process parameter (which parameter can be set within the script action on the process). Note:  If a single day has overtime hours, but the total timesheet actuals <= total weekly availability, no splitting occurs.
  • This Process sends an email to every Action Item Assignee where the Due Date/Time has passed and the Status is either Open, or In Progress.  Users may want to modify this stalker to include Status = Deferred.  In addition, the Resource Manager for the Assignee receives a copy of the email. In order to generate emails, the SMTP gateway must be up and running and Resources must have a valid email address.
  • A process that removes all the group assignments for inactive users after execution of process. The following are removed for all inactive users:
    • Group assignments
    • Instance rights
    • Global rights
    Note: It will not remove the instance rights which are generated automatically (like Project – Manager (Auto), Resource Manager(Auto) etc).
  • This is an automation to adjust the cost in financials (WIP) based on the standard weekly hours for salaried (Exempt) personnel. The process adjusts only the cost in WIP where the hours per week that are posted for a resource are more than the standard work week. The Posted hours in the timesheet and in WIP remain untouched.   For the process to calculate correctly, all time in a given week needs to be accounted for, including all non-project time. The process has three input parameters as explained below:
    • wkStdHour: Standard Weekly Hours; this can be changed in the process gel script. The parameter is based on the organization standard work week. The default is set to 40 hours.
    • xogBatchSize: The XOG batch size.  This is used to upload data in batches to avoid high memory and performance issues. The default batch size is set to 50 records.
    • username: The resource name that the process uses for uploading data. The default is set to admin.
    • It will process all the timesheets in posted state provided the timesheet has not been adjusted earlier by this process and there are no pending transactions to be posted for it. Validation is made based on Notes field, which is populated once adjustment is done by the process.
    • Notes field should not be modified in Script nor should be worked upon by any other process.
    • All the invalid transactions should be cleared and post to WIP should be finished with no pending records.
  • 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 Email Process Instance Errors workflow process will email a selected group within Clarity informing them of process errors that are currently in the system. The selected group is input through a gel parameter so it may be easily changed. This workflow helps to resolve errors quickly by emailing group members of the errors within the system so they may take action immediately.
  • 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.
  • Course Description:   We once had a client refer to the reports they developed as “Fisher-Price” reports. Reports should be built with consistency using graphic design principles. Join a Rego architect and UX designer to learn some fundamental graphic design principles such as grid theory, ink-to-data ratio, flow, balance, and more. Come prepared to be "wowed."
  • Course Description:   Are you struggling to implement Agile tools at your organization alongside Clarity PPM? This class will review best practices for implementing Agile tools in conjunction with Clarity PPM while living in a bimodal world. We will discuss how Clarity PPM can govern both types of work and teams and how Agile tools should interface with Clarity PPM.
  • Course Description:   Does your organization want to implement application portfolio management (APM)? Are you trying to determine the value in implementing APM? Are you struggling to know what tool you should use and what data is important to collect? This session will review specific use cases of companies that have implemented APM and effectively used the data to drive value for the organization.
  • Are you looking for some great examples of dashboards that include metrics/KPIs? This session will review a host of sample metric dashboards in use today that can spark ideas for you to implement in your company.
  • 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
Go to Top