- PeopleSoft 5.1.11
- PeopleSoft 5.1.10 - funcrel
- PeopleSoft 5.1.9 - funcrel
- PeopleSoft 5.1.8 - funcrel
- PeopleSoft 5.1.7 - funcrel
- PeopleSoft 5.1.6 - funcrel
- PeopleSoft 5.1.4 - funcrel
- PeopleSoft 5.1.3 - funcrel
- PeopleSoft 5.1.2 - funcrel
- PeopleSoft 5.1.1 - funcrel
- PeopleSoft 5.1.0 - funcrel
- PeopleSoft 5.1.0 - alpha 1
PeopleSoft 5.1.11
N/A
PeopleSoft 5.1.10 - funcrel
Customer Ticket Id | Details |
|---|---|
| 18113 | False positive for rule "In an INSERT statement, define explicitly the values for all the table columns (PeopleSoft)" - QR ID = 1600292 |
| 24358 | Wording hardcoded -> hard-coded changed in documentation for the rules 1600840 - Avoid using hardcoded usernames (PeopleSoft) and 1600200 - Don't use hardcoded message (PeopleSoft). |
PeopleSoft 5.1.9 - funcrel
| Internal ID | Ticket ID | Summary | Affects Version/s |
|---|---|---|---|
| PPSFT-217 | 17430 | Missing CR in the description of the rule "PeopleSoft: Avoid using the SQLExec statements in the PeopleCode" | 5.1.4-funcrel |
| PPSFT-222 | 17481 | Explanation are missing in rule "PeopleSoft: Avoid using comments in SQL queries" | 5.1.4-funcrel |
| PPSFT-229 | 17483 | Spelling mistake + precision missing for rule "PeopleSoft: Avoid tables having indexes with a too large index definition" | 5.1.4-funcrel |
| PPSFT-249 | - | Review implementation of rule 1600200 - "Don't use hardcoded message (PeopleSoft)" | 5.1.7 |
| PPSFT-256 | 22371 | The PeopleSoft extraction using 5.1.8 extractor is not extracting the German translations with Value set to DEU | 5.1.8 |
| PPSFT-257 | 22509 | Check rule "All new Record must have a SYNCID (PeopleSoft)": QR description should be enhanced to provide this info : the QR is not applicable for all Peoplesoft applications | 5.1.7 |
| PPSFT-259 | 23230 | Insufficient documentation for the rule id 1600520 : "IN vs EXIST Use IN when the subquery is the most selective" | 5.1.7 |
| PPSFT-261 | 23416 | Need to modify the format of the remediation steps given as it is difficult to understand | 5.1.7 |
PeopleSoft 5.1.8 - funcrel
| Internal ID | Ticket ID | Summary | Affects Version/s |
|---|---|---|---|
| PPSFT-215 | 16825 | Incomplete quality rules description on technologies.castsoftware.com and dashboard | 5.1.4-funcrel |
| PPSFT-216 | 17433 | Wrong reference for rule "PeopleSoft: Child records must share all keys as the parent record, plus one or more keys that uniquely identify each row." | 5.1.4-funcrel |
| PPSFT-219 | 17474 | [Perm Fix] "2.3" in the rule description of the rule "PeopleSoft: Using DISTINCT, GROUP BY or UNION clause in a View implies that ..." | 5.1.4-funcrel |
| PPSFT-220 | 17477 | [Perm Fix]Output missing for rule "PeopleSoft: Avoid unlimited occurs on grids" | 5.1.4-funcrel |
| PPSFT-221 | 17479 | [Perm Fix]Description, rationale, ... missing for "PeopleSoft: Avoid PeopleCode Event with High Cyclomatic" and a few others rules | 5.1.4-funcrel |
| PPSFT-225 | 17476 | Rationale, description and remediation missing for rule PeopleSoft: In an INSERT statement, define explicitly the values for all the table columns | 5.1.4-funcrel |
| PPSFT-227 | 17480 | Explanation are missing in rule "PeopleSoft: Write UNION ALL instead of UNION statement" | 5.1.4-funcrel |
| PPSFT-230 | 17484 | Description, remediation, ... missing for a few PeopleSoft rules (2 x 2 QRs+ 2 x 4 QRs) | 5.1.4-funcrel |
| PPSFT-239 | 18834 | [PeopleSoft] Extraction is failing because the versions are not defined correctly in the .bat peoplesoft file | 5.1.7 |
| PPSFT-241 | 19302 | PeopleSoft extraction is failing when accessing Oracle Database using Service name | 5.1.7 |
| PPSFT-243 | 20425 | Wrong count of violation for the QR of ID 1600504 | 5.1.7 |
| PPSFT-244 | 20423 | Wrong count of violations- Do not define a recordField EFFDT or EFF_STATUS without the other (PeopleSoft) | 5.1.7 |
| PPSFT-248 | QR "Field label item must have a translation into another language (PeopleSoft)” is hardcoded for FRA. Need to expand to other languages | 5.1.7 |
PeopleSoft 5.1.7 - funcrel
| Internal ID | Ticket ID | Summary |
|---|---|---|
| PPSFT-218 | 17473 | "n" missing in the rule description for rule "PeopleSoft: Using DISTINCT, GROUP BY or UNION clause in a View implies that ..." |
| PPSFT-224 | 17475 | Spelling mistake for rule "PeopleSoft: Avoid modification of lenghts or types of Fields" |
| PPSFT-226 | 17478 | Spelling mistake in the rule named "PeopleSoft: Record Table should have a Description Long" and a few others |
| PPSFT-228 | 17482 | Spelling mistake in rule "PeopleSoft: Avoid using count(*) syntax". |
| PPSFT-234 | 17943 | Multiple errors during analysis of PeopleSoft Vanilla using PeopleSoft Extension v5.1.6-funcrel |
PeopleSoft 5.1.6 - funcrel
| Internal ID | Ticket ID | Summary |
|---|---|---|
| PPSFT-82 | 7887 | Snapshot was completed but the discrimination of Vanilla objects in the dashboard did not occur. |
| PPSFT-132 | 12053 | Peoplesoft offline Extraction - Performance issue |
| PPSFT-180 | 11999 | Peoplesoft Packaging fails as host name is getting truncated - "Unknown host specified" |
| PPSFT-181 | PORTING: PSOFT_DISCRIMINATION_DATA - more than one row returned by a subquery used as an expression | |
| PPSFT-182 | - | Error in the Master Files for metric 7124: Metric 7124, inconsistent name for parameter #1, name 'Minimum Functional Evolvability' does not match 'Maximum Functional Evolvability' |
| PPSFT-195 | - | Fix typos in metric names. 1600484:
1600572
|
| PPSFT-197 | 13952 | Schema Installation with Peoplesoft 5.1.4 is not supported by Server Manager. |
| PPSFT-211 | 16465 | Temp fix: The DMT does not list a 'PeopleSoft' package type when using PeopleSoft v5.1.5-funcrel |
PeopleSoft 5.1.4 - funcrel
| Internal ID | Ticket ID | Summary | Comments |
|---|---|---|---|
| PPSFT-171 | 13242 | New defect in v5.1.3 on code in comment with pattern REM | A bug has been found in previous releases which was causing false violations to be listed for code commented with the REM and/or /* */ patterns . This bug has now been fixed and after an upgrade to PeopleSoft 5.1.4 and the generation of a post-upgrade consistency snapshot on unchanged source code, results may change: there may be less violations providing improved accuracy. |
| PPSFT-172 | 13241 | False positives on code in comment with pattern /* */ | |
| PPSFT-175 | 13283 | Dashboard is not showing latest snapshot data for peoplesoft | - |
| PPSFT-173 | - | PeopleSoft v5.1.0 to 5.1.3 do not install correctly the 38 measures | - |
PeopleSoft 5.1.3 - funcrel
| Internal ID | Call ID | Description | Situation | Symptoms | New behaviour |
|---|---|---|---|---|---|
| PPSFT-169 | - | No metrics for MA | When running a PeopleSoft analysis and looking at the log file and rule results. | An error is listed in the Metrics Assistant log: Failed to parse xml file: C:\ProgramData\CAST\CAST\Extensions\com.castsoftware.peoplesoft.5.1.2-funcrel\configuration\Languages\PeopleSoft\PeopleSoftCastMetrics.xml (line=608, col=1)). This leads to incorrect results for rules calculated by the Metrics Assistant: there are no violations for approximately 25 PeopleSoft rules and their grade is set to 4. | The issues are fixed. |
| PPSFT-161 | 12918, 12919, 12922 | Issues with the rule 1600110: PeopleSoft: Check existence of "Update", "Insert" & "Delete" Statements using SQLExec function. | When running a PeopleSoft analysis and looking at the results of the rule 1600110: PeopleSoft: Check existence of "Update", "Insert" & "Delete" Statements using SQLExec function. |
| The issues are fixed. |
PeopleSoft 5.1.2 - funcrel
| Internal ID | Call ID | Description | Situation | Symptoms | New behaviour |
|---|---|---|---|---|---|
| PPSFT-163 | - | Compatibility of DMT plugins with 8.2 | Using the package for existing extractions with AIP 8.2 | When you run the package action, an error message "An error has occurred during command processing" is displayed. In the details, you can see : | MDA files specific to CAST AIP 8.2.x are now delivered with the extension and must be activated manually. |
| PPSFT-82 | 7887 | Snapshot completed but the discrimination of Vanilla objects in the dashboard does not occur. | When running a snapshot and looking at the results in the CAST Dashboards. | Snapshot completed but the discrimination of Vanilla objects in the dashboard does not occur. | Discrimination is now showing. |
PeopleSoft 5.1.1 - funcrel
| Internal ID | Call ID | Description | Situation | Symptoms | New behaviour |
|---|---|---|---|---|---|
| PPSFT-160 | - | Discrimination fails with a PSOFT-108 sql error | Using version 5.1.0-funcrel | The snapshot is computed but empty. The log for end application shows the error message PSOFT-108 | The computation is good after the execution of the analysis |
PeopleSoft 5.1.0 - funcrel
| Internal ID | Call ID | Description | Situation | Symptoms | New behaviour |
|---|---|---|---|---|---|
| PPSFT-85 | - | Extraction error "Invalid identification group value: null, row skipped" for links on Component: Many error messages "Invalid identification group value: null, row skipped" | The extraction was done with the config file corresponding to the one included on the version 5.0.x | Many error messages displayed in the log: "Invalid identification group value: null, row skipped". | All error messages corresponding to components are removed. |
| PPSFT-144 | - | Events are not counted in LOC: | Using PeopleSoft extension 5.0.x to compute the snapshot. | The number of lines of code is very low. | The number of lines of code reflects the peoplecode which has been modified or added. |
PeopleSoft 5.1.0 - alpha 1
None: alpha release.
