CTMS 11.0 ER016-005: Difference between revisions
From Calidus HUB
(Created page with "<!-- MEDIA LANDSCAPE YES --> {{#vardefine:System|CTMS}} {{ERHeader |SystemVersion=CTMS 11.0 |ERNumber=ER016-005 }} {{ERTableHeader}} {{ERTableRow |DP_REPORTS.sql |Reports Packa...") |
(No difference)
|
Latest revision as of 17:03, 27 July 2015
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER016-005
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks | Reporter |
| DP_REPORTS.sql | Reports Package | 5.31 | 328343 | - | 3 | The urgent order messages will be processed if they are still required for the current delivery type of the order: if the delivery type is no longer urgent then a message will not be generated.
All of the current recipient types can be listed for selection in the Message Maintenance screen. The urgent order messages will be processed via an EDI process with the following report values: Title: Package Name Name: PROCESS Value: DP_REPORTS.P_PROCESS_URGENT Title: Parameter Name: p_process Value: URGENT |
Paul Roscoe |
| MSG_MAINT.fmx | Message Maintenance Form | 2.26 | " | " | " | " | " |
| MSG_JOB.sql | Message Jobs database package | 5.8 | " | " | " | " | " |
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks | Reporter |
| DP_REPORTS.sql | Reports Package | 5.32 | 328770 | - | 3 | Duplicated content based on mutliple delivery locations. Code amended to prevent duplicated content DESPATCH_EMAIL set to N, emails will only be generated when trips are despatched using MCS | Suzanne Woodcock |
| New Parameters | |||
| Parameter Name | Config Level | Setting Value | Result |
| DESPATCH_EMAIL | SYSTEM | N | |
