-
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. -
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.
-
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.
-
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.
- 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.
- PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
-
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.
- 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.
- PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
-
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.
- 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.
- PRLock (Timesheets) Record Removal (ID: rego_prlock_rec_rmvl). This process requires PRNAME, PRTABLENAME and PRRECORDID from PRLock Table.
-
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
-
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. -
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.
-
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 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. -
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.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy