RegoXchange
  • This process pulls in the total hours tracked, by resource, by task, for a given project for the weekly time period that ended. The information is sent to the Project Manager listed on the project. This process can be scheduled via the Execute a Process job.
  • The Populate Prior Periods Forecast From Actuals in Cost Plans process updates Cost Plans for Active Projects, it updates the Forecast for previous months = Posted Actuals, to remove variances from past periods.   This is an On Demand process in Clarity named Populate Prior Periods Forecast From Actuals in Cost Plans and can be manually executed from the Organizer or scheduled through the “Execute a Process” job. If there are number of processes in the Organizer – Available Processes, this process can be filtered and then checked to Start. When the process is started it will be seen in the Initiated on the Processes tab. The process status can be monitored from Running to the Completed stage. The process is very flexible and supports Cost Plans with any given grouping and it also works without any dependency on timeslices or other jobs. The process fetches Cost plan of records for all active projects in the system that have Actuals transactions in WIP table. It then process those cost plans to update all of the prior monthly forecast periods with the corresponding monthly Actuals.
  • A Resource Calendar sub-object is populated by a non-object-specific process, executed by the “Execute a Process” job, which can be scheduled. The first 7 rows of the sub-object display the standard week from the base calendar, including columns for Day of Week, Is Workday (checked/unchecked), Shifts, and work Hours available. The remaining rows display calendar exceptions, including columns for Day of Week, Exception Date, Is Exception (checked), and work Hours available.  If exception changes to a workday, Is Workday column is checked, and Shifts also display.  If exception changes to a non-workday, Is PTO column is checked. Resource Calendar object is filterable by Calendar Entry Type (All, Calendar Exception, Day of Week), Day of Week, Exception Date Range, Is Workday, Is Exception, Is PTO, and power filter.
  • The Populate Timesheets process converts task level ETC into time entered on the timesheet. The process relies on the resource “opting in” to the process by checking a new attribute called “Auto Populate Timesheet?”, as well as the project manager “opting in” at the project level via a new attribute called “Auto Populate Timesheet?” Once the resource opts in and the PM opts in, the process will create a timesheet for the resource, pulling in the ETCs for the tasks that week and moving them to the actual hours. Once the process runs, an email will be sent to the resource letting them know the hours have been applied.
  • Part of the Business Transformation Package, this portlet displays the portfolios with hierarchy (child portfolio(s)). The portlet displays the basic portfolio fields like – manager, stakeholder, etc. A Metrics subpage can be created with the fields on the “Properties – Metrics.”.   The fields: Overall Health, Goal Alignment, Innovation Level, Probability of Success are custom fields and can be configured on a subpage.
  • The portlet shows which investments within a portfolio has a cost plan and those that do not. For the ones which do have a cost plan, the Cost Plan? Field shows a Green checkmark.  For the ones which do not have a cost plan, the Cost Plan? Field shows a Red cross.
  • Part of the Business Transformation collection, this pie chart portlet displays realized benefit, grouped by category for portfolio investments. It uses System Provider: Portfolio Investment Provider.
  • Part of the Business Transformation collection, this pie chart portlet displays realized benefit, grouped by type of project, for portfolio investments. It uses System Provider: Portfolio Investment Provider.
  • Summarize an ad hoc list of investments or leverage your defined hierarchies to visualize and evaluate the performance of your portfolios, including financial data analysis. Report Views include: • Change Requests • Cost Trend • Cost • Effort Trend • Effort • Hierarchy Summary • Investment Drill Thru • Investment Gantt • Issue Summary • Milestones • Risk Summary • Staff • Status Report Summary • Tasks Demo Video - https://www.youtube.com/watch?v=UNByLAWJ2Nw&list=PLXJ5ktuWV0jiS9CvBpHvBIwpKPmA9uvwK&index=4 The main .rpt file will access data through the Data Warehouse. For clients on Rego’s AWS hosting, we have versions that work with Oracle and Postgres DB and access the live database, if the Rego Odata connector is being used.
  • The Portlets and NSQL Queries portlet displays portlets built from queries.  The portlet provides the administrator with the ability to search queries developed in the past that may have a certain attribute within it.  This is helpful during upgrades when CA makes data model changes.
  • Portlets on Pages displays portlets located on each page within Clarity. This portlet is useful for administrators to determine which users have customized their pages and if they are not seeing a certain portlet, or if a user has placed a portlet on another page and needs help locating it. It also shows the portlet code, name, page the portlet resides on, tab type, who created the tab, source type, and the object/query.
  • The process is built to clear the random timesheet locks that happens occasionally.  There are three Processes and one lookup component and one job definition in the package.
    • PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
      • The Lookup PRLock Check (Timesheet) (Id: REGO_PRLOCK_CHECK) should be used to update the GEL parameters for the above process.
    • PRLock (Timesheets) Record Removal All (ID: rego_prlk_rc_rmv_all) This deletes ALL prtimesheet locks.
    Or
    • Rego Remove Timesheet Locks (ID: rego_rmv_ts_locks). This process is run as a job “PrLock Clear for Timesheet Locks” which performs the same functionality as the above two processes. The process and job definition are separate XOG files.
Go to Top