RegoXchange
  • This can be used to remove all participants and their corresponding security permissions. NOTE: The ability to remove the right is with the admin only.
  • The PPM Data Dictionary Extractor pulls schema and attribute information from each object in CA PPM and places it in a custom object.  The following fields provide details information about each attribute in the CA PPM Instance.
    • Object Name – The name of the object to which the attribute belongs
    • Object Code – The external ID of the object to which the attribute belongs
    • Attribute Name – The name of the attribute
    • Attribute Code – The external ID of the attribute
    • Partition Code – The partition to which the attribute belongs
    • Table Name – The database table where the attribute is located
    • Column Name – The database column name of the attribute
    • Data Type – The data type of the attribute
    • Data Size – The character limit of the attribute
    • Data Scale – The scale of numeric attributes
    • Is Active – Specifies if the attribute is active
    • Extended Data Type – The extended type of the attribute (ex: lookup, money, etc.)
    • Lookup Name – The name of the attribute’s lookup
    • Lookup Type – The external ID of the attribute’s lookup
    • Default Value – The default value assigned to the attribute
    • API Alias – The REST API alias assigned to the attribute
    • Max Value – The maximum value accepted by the attribute
    • Min Value – The minimum value accepted by the attribute
    • Curve Name – The name of the Curve for Time-Scaled value attributes
    • Curve Type – The type of the Curve for Time-Scaled value attributes
    • Is Custom – Is the attribute a stock attribute or custom
    • Is Auto-Numbered – Is auto-numbering enabled for the attribute
    • Is Multi-Valued – Is the attribute a multi-valued lookup
    • Is DWH Enabled – Is the attribute enabled for export to the data warehouse
    • Is Editable – Is the attribute editable or read-only
    • Is Required – Is the attribute required
    • Is Virtual – Is the attribute a virtual attribute
    • Is Private – Is the attribute a private attribute used by the application behind the scenes
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
  • The Action Item Reassignment – Workflow provides the ability to reassign an action item(s) that has been sent out to a resource.  You first choose the resource who currently has the action item(s) sitting in their queue.  Next, you choose the resource you want to reassign the action item(s) to.  Finally, you select one to many action items you want to re-associate before running the process.  After all the fields are set, the process can be run which will re-associate the action items from one resource to the other.
  • 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 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
Go to Top