RegoXchange
  • 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.
  • 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.
  • The Process Instance Errors portlet will show all processes that error. This portlet will assist the administrator with determining which processes are in error and whether to skip, retry, or cancel. It will display the process name, code, start date, and who initiated the process. You may also filter by any of the criteria listed in the grid.
  • For each process, the Process Run Metrics portlet shows the Process Name, Process Code, Description, # Running, # Completed, # Errored, and Last Run Date. This portlet is ideal for system administrators and support staff needing to monitor the health of the environment. Viewers of this portlet can get a sense of the complexity & health of the environment with the # of processes running and visibility into processes that errored out. The table below describes the available filter fields in the portlet.
    Column Label Description
    Process Name Name of the process
    Start Date Start date of the process’s last ran date
    End Date End date of the process’s last ran date
    Description Description of the process
    Process ID ID of the process
  • 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.
  • The Program Costs portlet looks like a cost plan.  It will summarize all cost plans from projects within the program and display the totals.
  • The Program Dashboard Sub-Project Change Requests portlet gives the ability to view all change requests of sub-projects of a program. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by status, in descending order, and then by target date. It displays the sub-project name, change request name, owner, status, target date, approved by, and the priority.
  • The Program Dashboard Sub-Project Open Issues portlet gives the ability to view issues on sub-projects of a program that are not closed or resolved. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the sub-project name, issue name, owner, target date, status and priority.
  • The Program Dashboard Sub Project Action Items portlet display Action Items of Sub Projects in a Program.  The portlet will pull the "Action Items" from all the sub projects in the Program, and this information is placed on the Dashboard tab. This portlet displays each Project, name of the Action Item as mentioned in the Subject, and the resource who Created this Action Item. Assigned To field will display the resource to whom the Action Item has been Assigned. Due Date mentions the date the Action Item will be completed and the Priority level of the Action Item is a stoplight showing red, yellow and green for the different levels of priority. The table below describes the available columns in the portlet. The first 6 are configured in the default view:
    Column Label Description
    Project Name of the Project
    Subject Defines the name for Action Item
    Created By Resource who created the Action Item
    Assigned To Resource who the Action Item is Assigned to
    Due Date Date the Action Item is due for completion
    Prty Specifies the priority level of the Action Item
    Action Item ID Internal ID used by the query
    Created By ID Internal ID used by the query
    Created Date Date the Action Item was created
    Days Open No. of days the Status of Action Item has remained opened since it was created
    Priority Name Based on high, medium, or low priority with corresponding red, yellow, or green stoplights
    Project DB ID Internal ID used by the query
    Project ID Unique ID of the Project within Clarity
    Project Manager Project Manager
  • The Program Dashboard Sub-Project Open Risks portlet gives the ability to view all risks on the sub-projects of a program that are not closed or resolved. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the dashboard tab. The portlet sorts the issues first by value, in descending order, and then by target date. It displays the sub-project name, risk name, owner, target date, status, probability, impact and value.
Go to Top