This page describes the content of this Service Release and contains the following sections:
Service Release-Specific Installation Instructions describes additional installation instructions (supplementing the standard service release installation instructions) that are specific to this service release.
Database Changes describes any structural changes that were made to the GC3 database and migration notes, if applicable.
Integration Changes summarizes changes to the standard GC3 XML interfaces.
Corrections describes defects that were reported and fixed in the release.
Enhancements lists all the enhancements in this release (excluding those that were customer-specific and not included in the core product).
Updated Files lists all files that have changed.
Next Service Release shows the date of the next scheduled service release.
Customer Support provides contact information if you need assistance with this service release.
Service Release are cumulative in their content and any corrections/enhancements from previous service releases are also included. You should also review previous release notes for release-specific installation instructions as well.
There are no service release-specific installation instructions for this release. Refer to the standard service release installation instructions.
DENIED_PARTY_MATCH |
Column |
Data Type |
Nullable? |
denied_party_match_gid |
VARCHAR2(101) |
NOT NULL |
denied_party_match_xid |
VARCHAR2(50) |
NOT NULL |
object_gid |
VARCHAR2(101) |
NOT NULL |
object_type |
VARCHAR2(50) |
NOT NULL |
involved_party_qual_gid |
VARCHAR2(101) |
NOT NULL |
involved_party_contact_gid |
VARCHAR2(101) |
NOT NULL |
com_method_gid |
VARCHAR2(101) |
NOT NULL |
itl_denied_party_gid |
VARCHAR2(101) |
NOT NULL |
is_manually_approved |
VARCHAR2(1) |
NOT NULL |
approving_gl_user_gid |
VARCHAR2(128) |
|
approval_comments |
VARCHAR2(4000) |
|
screen_date |
DATE |
|
domain_name |
VARCHAR2(50) |
NOT NULL |
Insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
DOCUMENT_DEF_TEXT |
Column |
Data Type |
Nullable? |
document_def_gid |
VARCHAR2(101) |
NOT NULL |
text_template_gid |
VARCHAR2(101) |
NOT NULL |
is_mandatory |
VARCHAR2(1) |
NOT NULL |
domain_name |
VARCHAR2(50) |
|
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
DOCUMENT_TEXT |
Column |
Data Type |
Nullable? |
document_gid |
VARCHAR2(101) |
NOT NULL |
text_template_gid |
VARCHAR2(101) |
NOT NULL |
is_fixed |
VARCHAR2(1) |
NOT NULL |
is_disabled |
VARCHAR2(1) |
|
item_context_type |
VARCHAR2(50) |
|
item_context |
VARCHAR2(500) |
|
text_override |
VARCHAR2(4000) |
|
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
DOCUMENT_USE_PROFILE |
Column |
Data Type |
Nullable? |
document_use_profile_gid |
VARCHAR2(101) |
NOT NULL |
document_use_profile_xid |
VARCHAR2(50) |
NOT NULL |
is_allowed_upload |
VARCHAR2(1) |
NOT NULL |
is_trusted_upload |
VARCHAR2(1) |
|
max_upload_size |
NUMBER |
|
is_browser_virus_protected |
VARCHAR2(1) |
NOT NULL |
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
OMR_D_LINE_REFNUM |
Column |
Data Type |
Nullable? |
omr_d_gid |
VARCHAR2(101) |
NOT NULL |
sequence_no |
NUMBER(8) |
NOT NULL |
om_refnum_qual_gid |
VARCHAR2(101) |
NOT NULL |
om_refnum_value |
VARCHAR2(101) |
NOT NULL |
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
OMR_D_LINE_REMARK |
Column |
Data Type |
Nullable? |
omr_d_gid |
VARCHAR2(101) |
NOT NULL |
sequence_no |
NUMBER(8) |
NOT NULL |
remark_sequence |
NUMBER(8) |
NOT NULL |
remark_qual_gid |
VARCHAR2(101) |
|
remark_text |
VARCHAR2(4000) |
NOT NULL |
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
OMR_D_LINE_STATUS |
Column |
Data Type |
Nullable? |
omr_d_gid |
VARCHAR2(101) |
NOT NULL |
sequence_no |
NUMBER(8) |
NOT NULL |
status_type_gid |
VARCHAR2(101) |
NOT NULL |
status_value_gid |
VARCHAR2(101) |
NOT NULL |
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
ORDER_MOVEMENT_REMARK |
Column |
Data Type |
Nullable? |
order_movement_gid |
VARCHAR2(101) |
NOT NULL |
remark_sequence |
NUMBER(8) |
NOT NULL |
remark_qual_gid |
VARCHAR2(101) |
|
remark_text |
VARCHAR2(4000) |
|
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
VARCHAR2(128) |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
SHIP_UNIT_TEXT |
Column |
Data Type |
Nullable? |
ship_unit_gid |
VARCHAR2(101) |
NOT NULL |
text_template_gid |
VARCHAR2(101) |
|
domain_name |
VARCHAR2(50) |
NOT NULL |
insert_user |
DATE |
NOT NULL |
insert_date |
DATE |
NOT NULL |
update_user |
VARCHAR2(128) |
|
update_date |
DATE |
|
voyage_stowage_mode is now Stowage_mode.
ITL_DENIED_PARTY_SCREEN
ITL_DENIED_PARTY_SCREEN_MATCH
Table |
Column |
DataType |
ACCESSORIAL_COST |
PAYMENT_METHOD_CODE_GID |
VARCHAR2(101) |
ACCESSORIAL_COST_UNIT_BREAK |
MIN_COST |
NUMBER |
|
MIN_COST_CURRENCY_GID |
VARCHAR2(101) |
|
MIN_COST_BASE |
NUMBER |
|
MAX_COST |
NUMBER |
|
MAX_COST_CURRENCY_GID |
VARCHAR2(101) |
|
MAX_COST_BASE |
NUMBER |
RATE_GEO_COST |
PAYMENT_METHOD_CODE_GID |
VARCHAR2(101) |
RATE_GEO_COST_UNIT_BREAK |
MIN_COST |
NUMBER |
|
MIN_COST_CURRENCY_GID |
VARCHAR2(101) |
|
MIN_COST_BASE |
NUMBER |
|
MAX_COST |
NUMBER |
|
MAX_COST_CURRENCY_GID |
VARCHAR2(101) |
|
MAX_COST_BASE |
NUMBER |
HAZMAT_GENERIC |
IS_NOS |
VARCHAR2(1) |
|
IS_MARINE_POLLUTANT |
VARCHAR2(1) |
|
IS_TOXIC_INHALATION |
VARCHAR2(1) |
|
IS_PASSENGER_AIRCRAFT_FORBID |
VARCHAR2(1) |
|
IS_COMMERCIAL_AIRCRAFT_FORBID |
VARCHAR2(1) |
|
TOXIC_INHALATION_HAZARD_ZONE |
VARCHAR2(10) |
|
ERG |
VARCHAR2(25) |
|
ERG_AIR |
VARCHAR2(25) |
|
EMS |
VARCHAR2(25) |
ORDER_RELEASE_LINE |
HAZ_IS_NOS |
VARCHAR2(1) |
|
HAZ_IS_MARINE_POLLUTANT |
VARCHAR2(1) |
|
HAZ_ERG |
VARCHAR2(25) |
|
HAZ_ERG_AIR |
VARCHAR2(25) |
|
HAZ_EMS |
VARCHAR2(25) |
LANE_SUMMARY |
FIRST_TIME_PERIOD |
NUMBER |
P_BID |
SOURCE_DESC |
VARCHAR2(128) |
|
DEST_DESC |
VARCHAR2(128) |
DATA_QUERY_TYPE |
SUPPORT_AGENT |
VARCHAR2(1) |
|
SUPPORT_TEXT |
VARCHAR2(1) |
CONSOL |
HAZMAT_TYPE |
VARCHAR2(50) |
|
ITINERARY_PROFILE_GID |
VARCHAR2(101) |
JOB |
CONSOL_GID |
VARCHAR2(101) |
CONTACT |
IS_EMAIL_VIRUS_PROTECTED |
VARCHAR2(1) |
DOCUMENT_CONTENT |
IS_AWAITING_VIRUS_CHECK |
VARCHAR2(1) |
DOMAIN |
DOCUMENT_USE_PROFILE_GID |
VARCHAR2(101) |
GL_USER |
DOCUMENT_USE_PROFILE_GID |
VARCHAR2(101) |
TEXT_TEMPLATE |
IS_MODIFIABLE |
VARCHAR2(1) |
Table |
Column |
DataType |
TEXT_TEMPLATE |
DATA_QUERY_TYPE_GID |
VARCHAR2(101) |
ITL_DENIED_PARTY |
ADDRESS_LINE_1 |
VARCHAR2(128) |
|
ADDRESS_LINE_2 |
VARCHAR2(128) |
|
ADDRESS_LINE_3 |
VARCHAR2(128) |
|
DENIAL_CODE |
VARCHAR2(4) |
|
AGENCY_CODE |
VARCHAR2(10) |
|
RULING_VOLUME |
VARCHAR2(6) |
|
RULING_PAGE_NUMBER |
VARCHAR2(6) |
ORDER_RELEASE |
INSPECTION_NUMBER |
VARCHAR2(128) |
|
LOC_NUMBER |
VARCHAR2(128) |
|
LOC_ADVISING_NUMBER |
VARCHAR2(128) |
|
LOC_CONFIRMING_NUMBER |
VARCHAR2(128) |
|
IMPORT_LICENSE_NUMBER |
VARCHAR2(128) |
INVOICE |
VESSEL_CODE |
VARCHAR2(101) |
NFRC_RULE_INV_PARTY_CRITERIA |
OBJECT_TYPE |
VARCHAR2(50) |
Table |
Old Column Name |
New Column Name |
STOWAGE_MODE_PREFERENCE |
VOYAGE_STOWAGE_MODE_GID |
STOWAGE_MODE_GID |
CHARTER_VOYAGE_STOWAGE |
VOYAGE_STOWAGE_MODE_GID |
STOWAGE_MODE_GID |
CONSOL |
VOYAGE_STOWAGE_MODE_GID |
STOWAGE_MODE_GID |
ORDER_RELEASE |
DEFAULT_VOYAGE_STOWAGE_MODE |
DEFAULT_STOWAGE_MODE |
TEXT_TEMPLATE |
REPORT_TYPE |
DATA_QUERY_TYPE_GID |
Changes to the integration processing logic can be found below in their respected correction or enhancement description.
Changes to the XML schema are as follows:
Added Text element to Release.ShipUnit
element (50533)
Note: element is valid only when the ShipUnit is in the Release element
Added Status element to OrderMoveReplace element (49924)
Changed schema notes for
OrderMoveReplace element (49924)
Changed the logic for determining the TimeZoneGid when not specified.
The following properties have been removed:
glog.integration.OrderMoveReplace.defaultTimeZoneSource
gog.integration.OrderMoveReplace.defaultTimeZone
Added the following elements
to ACCESSORIAL_COST_UNIT_BREAK_ROW element (50161)
MIN_COST, MIN_COST_CURRENCY_GID, MIN_COST_BASE
MAX_COST, MAX_COST_CURRENCY_GID, MAX_COST_BASE
Added the following elements
to RATE_GEO_COST_UNIT_BREAK_ROW element (50161)
MIN_COST, MIN_COST_CURRENCY_GID, MIN_COST_BASE
MAX_COST, MAX_COST_CURRENCY_GID, MAX_COST_BASE
Updated schema notes for LetterOfCreditNum element (49925/50539)
Added PAYMENT_METHOD_CODE_GID element to ACCESSORIAL_COST_ROW element (50536)
Added PAYMENT_METHOD_CODE_GID element to RATE_GEO_COST_ROW element (50536)
Added IsNos element to HazmatGeneric element (51377)
Added IsMarinePollutant element to HazmatGeneric element (51377)
Added IsToxicInhalation element to HazmatGeneric element (51377)
Added IsPassengerAircraftForbid element to HazmatGeneric element (51377)
Added IsCommercialAircraftForbid element to HazmatGeneric element (51377)
Added InhalationHazardZone element to HazmatGeneric element (51377)
Added ERG element to HazmatGeneric element (51377)
Added ERGAir element to HazmatGeneric element (51377)
Added EMS element to HazmatGeneric element (51377)
Added support for ReleaseLineHazmatInfo.HazmatCommonInfo.IsNos element (51377)
Added support for ReleaseLineHazmatInfo.HazmatCommonInfo.IsMarinePollutant element (51377)
Added ERG element to ReleaseLineHazmatInfo element (51377)
Added ERGAir element to ReleaseLineHazmatInfo element (51377)
Added EMS element to ReleaseLineHazmatInfo element (51377)
Added StowageModeGid element
to ReleaseHeader element (49755)
Deprecates VoyageStowageModeGid element
For the duration of Release 5.0, both elements will be sent on outbound
Added StowageModeGid element
to CharterVoyageStowage element (49755)
Derecates VoyageStowageModeGid element
For the duration of Release 5.0, both elements will be sent on outbound
Added StowageModeGid element
to BookLineAmendDetail element (49755)
Deprecates VoyageStowageModeGid element
For the duration of Release 5.0, both elements will be sent on outbound
Added CharterVoyageGid element to Consol element (49755)
Added FlightInstanceId element to Consol element (49755 and 49732)
Added StowageModeGid element to Consol element (49755)
Added HazmatType element to Consol element (49755)
Added ItineraryProfileGid element to Consol element (49755)
Added CharterVoyage element
to Consol element (49755)
Note: The CharterVoyage element is not output when the Consol is within
the CharterVoyageStowage element.
Added Consol element to GLogXMLElement element (49755)
Added ConsolGid element to Job element (49755)
Added Text element to Document.
Revised Text element to allow inbound specification of text templates.
Revised Text element to allow inbound/outbound override of template
text.
Revised Text element to allow inbound/outbound specification of line-item
text for a document.
Added Billing element to ChildPayments element (51521)
Added Refnum element to OrderMoveReplaceDataLine element (51260)
Added Remark element to OrderMoveReplaceDataLine element (51260)
Added Status element to OrderMoveReplaceDataLine element (51260)
Added IntSavedQuery element to ShipmentCost element (51743)
Added TransactionCode element to ShipmentCost element (51743)
Added Location element to
Document element (51588)
Note that this element is supported on the outbound only
SalesLogix Ticket |
G-Log Issue |
Component |
Issue Summary and Resolution |
|
39064 |
User Preferences |
Users will be able to change user role and add new menus without getting duplicate key error. |
|
44495 |
Power Data |
The error while creating or editing a saved query in Power Data has been fixed. |
1-6010 |
45380 |
Infrastructure |
Internal |
|
45441 |
Algorithm |
Fixed a problem that was ignoring depot stops when figuring out the shipment start time from the stops. |
1-6043 |
45442 |
Customer Order |
All address lines for Source and Destination locations now appear. |
1-6433 |
45881 |
Rate Inquiry |
Issue 1: Accessorials will now be respected in Route&Rate RIQ. Issue 2: Labels for Discount, Stop Off charge, Circuity, and Other will now show up in Route&Rate RIQ |
1-6674 |
46364 |
Planning |
GC3 was not calculating accurate stop times on infeasible shipments. Changed GC3 to recalculate activity time even if the shipment is wait infeasible or late infeasible. |
1-7375 |
47661 |
Order Base |
Order Base special services will be correctly considered when multiple orders with mismatched special services are bulk planned together. |
1-7308 |
47765 |
Shipments |
In "Build Shipment Manually", if users choose to estimate service time, GC3 uses the time entered as "expected transit time" and then calls the drive routine. The old logic did not call drive routine, it just populated times manually, so the service time result from "Build Shipment Manually" can be different from "Build Shipment Direct" in the old logic. |
|
457992 |
Planning Order Actions |
If hazardous generic or hazmat item information is copied onto the order line, then the HAZARDOUS flag on the order line is now set to Yes. |
|
48268 |
Algorithm |
GC3 currently has the shipment cost ref table which allows users to link a shipment cost to one or more order lines. If a cost is linked to order 3, then order 3 is unassigned from the shipment, then shipment cost ref record is now correctly removed. |
1-8179 |
48278 |
Shipment Manager |
GC3 assumes the pickup/delivery dates are based on the time zone the source/destination is in and saves them in GMT. If a Plan From/To value is specified, the dates are for Plan From/To and the pickup/delivery dates need to be set properly to the time zone the Plan From/To is in. |
|
48384 |
Job Workspace |
Internal |
|
48692 |
Performance and Scalability |
Internal |
|
49022 |
Infrastructure |
Internal |
1-8559 |
49399 |
Events |
Lifetime event Tendered was used to stage ShipmentEvent. It is now changed back to TenderSent. |
1-8746 |
49543 |
Integration |
An ampersand (&) is now encoded as & when CSV is output as XML. |
1-8794 |
49583 |
User Preferences |
This problem would occur when there are more than 9 grid items and the user edited the first one. This has been fixed to search for a more definite string value. |
|
49744 |
Settlement Actions |
Added configurablity to the thresholds for the allocation rounding error adjustment routine. These were originally put in place to prevent infinite looping. |
|
49786 |
Rating |
Effective and expiration dates applied to rate records will now be considered when searching for a base rate. |
|
49807 |
Database |
Internal |
|
49831 |
Events |
The edit button has been added to quick events (power data) search results page and to the Quick Events View page. Also, clicking the Quick Event ID will open the edit screen instead of view screen. |
|
49866 |
Execution |
The action Modification Acknowledged did not process all selected orders. This action only processed one order release in the back-end, but allowed user to select multiple from the order release list. Changed the action to now allow a user to select multiple order releases. |
|
49869 |
Planning Order Actions |
When unassigning an order from a permanent shipment, try to unassign the order from the shipment rather than deleting everything except the 'shell' shipment. Modified GC3 so that the re-rating decision is only based on the Cost Fixed flag on the shipment, not on Servprovider Fixed flag. If rate engine does not return results and no orders on the shipment, then set shipment cost to 0. |
|
49871 |
NFRC Rules |
NFRC rule will correctly test the order release type criterion. |
|
49933 |
Rating Engine |
The array out of bound exception occurs when no flight instance was found in the air schedule search. A check was added so that this will not occur anymore. |
1-8970 |
49954 |
User Configuration |
Changed the element that thepPhone number field was referencing so instead of seeing the fax number, the user now sees the correct phone number. |
|
50041 |
Auto Assignment |
When editing an existing auto assign rule, if user changes the Pre Qual Criteria ID, the Pre Qual Criteria grid is deleted. |
|
50132 |
NFRC Rules |
When an NFRC rule asks for cost and one fails to be calculated, the Cost Infeasible flag should be applied |
|
50133 |
NFRC Rules |
It is no longer necessary to remove both sell and buy charges created by an NFRC rule get the rule to fire again. If a rule specifies both types of charges, and one charge exists, the rule will create the other charge. |
|
50164 |
Supply Chain Event Management |
Internal |
|
50176 |
NFRC Rules |
NFRC rule will no longer write a blank Service Provider ID into a newly created NFRC shipment. |
|
50246 |
Database |
Internal |
1-9155 |
50248 |
Infrastructure Business Logic |
When creating an invoice from a shipment - the following error occurred - No open range and default rule were found for Named Range. The GC3 server did not load business number generation related data correctly. This is now fixed. |
1-9229 |
50249 |
Labels/Internationalization |
Fixed a problem where users were unable to see events groups or event reason codes after loading and assigning the French language set to them via user preferences. |
|
50301 |
Integration |
User roles may now be uploaded via CSV. |
1-9159 |
50313 |
Web Tendering |
Code modified so that if GC3 cannot find Tender ID from ShipmentExecutionActionExecutor, use null. |
|
50421 |
Material Manager |
Changes to NMFC classes are now reflected immediately when building shipments. |
1-9229 |
50449 |
Labels/Internationalization |
Fixed a problem where users were unable to see events groups or event reason codes after loading and assigning the French language set to them via user preferences. |
|
50482 |
NFRC |
Fixed null pointer exception error that occurred when rating a NFRC shipment with no primary sell shipments on the job. |
|
50585 |
Infrastructure Business Logic |
Internal |
|
50613 |
Integration |
When uploading integration, the resulting screen now shows the ACK XML in one frame, and a link to the log/explanation in the other. |
|
50749 |
Planning Business Logic |
When the total cost of a set of orders going through a pool is more than the total cost of going direct, GC3 used to just send each order on direct shipment. Now those direct shipments are planned as multistop together. |
|
50819 |
Infrastructure Business Logic |
Internal |
|
50840 |
Collaboration |
Internal |
1-9414 |
50846 |
Screen Set |
In the Screen Set manager, the selection of a default operator (such as Same as instead of Begins With) can be made for fields like Shipment Reference Number and Source Location Name. |
1-9390 |
50883 |
Gatehouse |
When the shipment events were added through a Gatehouse screen, the REPORTING_GLUSER field in SS_STATUS_HISTORY table were not populated. But if the same event is added through the shipment events screen, the REPORTING_GLUSER field is populated with the correct user. Modified code to ensure that REPORTING_GLUSER field in SS_STATUS_HISTORY table gets set correctly. |
|
50889 |
Collaboration Business Logic |
The ORDER ON SHIPMENT - TENDER ACCEPTED event is now being raised. Added notify function TEMDER_ACCEPTED, and mapped it to ShipmentTenderAccepted order on shipment event. |
|
50923 |
Database |
Internal |
|
50943 |
Database |
The Vessel Code field on an invoice is now 101 characters. |
1-9557 |
50962 |
Planning Business Logic |
The Rating logic looks for the earliest possible start time of a shipment rather that the start time that is populated on the shipment, which is not accurate because sometimes a rate is not effective yet as the earliest possible start time. To address this issue, the logic was changed to look at the shipment start time. |
1-9443 |
50963 |
Collaboration |
The View Milestone page was not displaying the Timer Based Events properly. When a Milestone Monitor is assigned to a shipment which has timer based events. As long events did not occur the milestones will be displayed on View Milestone page. Once event occurs the Status History for Timer Based Events was not tracked. Issue resolved by correcting the Query which fetches Milestone history from Database. |
1-9523 |
50969 |
Planning Business Logic |
Change the Max Beans in Cache to 1000 for OrdrReleaseInvParty to match other OrderRelease beans. |
|
50980 |
Procurement Collaboration |
Internal |
1-9586 |
51048 |
Planning Business Logic |
Rate Inquiry did not re-calculate distance when a user preference is set to something other than miles. This is fixed. |
|
51052 |
Infrastructure |
On the new Rate Preference Manager page, when the user uses the l button on Lane ID, sorts the results twice and then makes a selection. The issue was that the selected record did not show on the new Rate Preference page. Now, the selection of Lane ID after multiple sorting on Lane ID Search page, does show the correct Lane ID on rate preference manager. |
|
51104 |
Integration |
Fixed the error that the transaction status is not being set to PROCESSEDD when CSVFileContent is successfully processed. |
1-9624 |
51119 |
Collaboration |
The discrepancy of event description in Public Tracking page vis-a-vis the event description on Buy Shipment event history has been fixed. The event description on public tracking now correctly points to 'status code description' instead of 'event group description' field (prior to the fix). |
|
51120 |
Execution |
Changed currency rounding during totalling to use standardized rounding instead of re-using the glog.business.shipment.costFractionalDigits property. |
|
51141 |
Execution |
The grid-flattened BOL Date field has been changed to have a date control. |
|
51145 |
Execution |
Allocation of a parent bill now sets the status of both the parent and child bills to ALLOCATED. |
|
51226 |
Procurement Collaboration |
Internal |
|
51230 |
Planning Business Logic |
Removed check for itinerary in merge shipments action. Instead, for each given shipment, GC3 finds the shipments that share SEquipments with the given shipments. It then combines all related shipments according to their relative position to the given shipments. |
|
51253 |
Execution |
Internal |
|
51259 |
Advanced Analytics |
Multiple aliases can be defined for carriers. However, when bringing carriers into the historical database, only one record per carrier can be created. The duplicate records were rejected. The code is fixed with logic to bring an alias name that is assigned to the alias qualifier of GLOG. Also, any records with shipment start time before 2000 were getting rejected. Time table is now filled from 1995 to 2008. |
|
51309 |
Execution |
Changed auto approval so that it will use the net amount due if Fixed Cost is checked instead of using line information. In this case, voucher lines are not created. |
|
51313 |
Execution |
Allocations will be ordered by order release or line ID, so the penny rounding will always be consistent between shipment allocation and voucher allocation. |
1-9769 |
51321 |
Advanced Analytics |
Tender Performance report is fixed. |
|
51324 |
Planning User Interface |
Fixed the following problems with saving contact information for locations:
|
|
51346 |
Collaboration |
Internal |
|
51348 |
Database |
Internal |
|
51354 |
Job |
When summing up allocations, GC3 now only uses allocation of type PLANNING and which are associated with orders on the current Job. |
|
51355 |
Execution |
The problem was when GC3 deleted a record from one of the child User Access tables (such as User Menu Access) it was not deleting the corresponding record from the User Access table if it was no longer used. This is now fixed. |
|
51364 |
Planning Business Logic |
For shipments that use an itinerary that does not require calculating contracted rate but does specify an estimated service time, GC3 will calculate the service time based on the estimated service time. (The old logic did not calculate service time at all if the itinerary does not require calculating contracted rate) |
|
51367 |
Planning Business Logic |
When a NFRC shipment has a fixed Rate Record assigned, you will be able to run the action Assign Rate to recalculate the cost of the shipment. |
|
51368 |
Freight Forwarder |
If a user clicks the Submit button multiple times on the Freight Forwarding page, a warning message is now shown on the screen and GC3 blocks the user from submitting the same page more than once. |
|
51369 |
Execution |
Bill/invoice creation previously always looked up the voyage and pulled in that information. This is changed so it now tries to get the information from the shipment (any data not available comes from the voyage). Also, the Voyage Number on the invoice is set with the Voyage XID and no longer the Voyage Name. |
|
51375 |
Execution |
Added status checks for Build from NVOCC and build Buy from Sell actions. |
|
51378 |
Automation Agents |
Agents will now complete even if when workflow_details log id is turned on and agent variables are used. |
|
51380 |
Integration |
Modified Integration Validation logic for the Shipment interface to verify existence of ShipUnit(s) that are being deleted. |
|
51402 |
Planning Business Logic |
Internal |
1-9846 |
51461 |
Planning Business Logic |
The Vessel ID is now copied to a Consol shipment on consol creation if it is of the Charter Voyage Stowage type. |
|
51500 |
Collaboration |
When a user logs in as a servicepProvider, after verifying the user's role, GC3 will give the user DBA privilege to query shipment events, and revoke it after the query returns. |
1-9869 |
51521 |
Execution |
Modified the Integration schema by adding the Billing element to the ChildPayments element. The ChildPayments element will optionally output either the Payment element, or the Billing element (which contains the Payment and Shipment information). The default output is the Payment element. To specify that the billing should be output, suppress the payment option labeled 'billing.ChildPaymentsPayment' in the outbound integration profile. |
|
51522 |
Integration |
Also added a new python script (DocumentHelper.py) which can be used to encode and decode a file into base64 format to be embedded into the DocContentBinary element within the Document XML Interface. There is also a command to extract all the DocumentContent from the Document XML and output into files. The script is available in the <gc3_install_dir>/utils/python directory. |
|
51523 |
Database |
Internal |
|
51541 |
Collaboration |
Made agent actions REPLAN and REPLAN LAST LEG available as pre-persistence actions. Some workflow agents have been using agent action PERSIST right before calling one of the actions listed above. If this is the case, the work-around in no longer recommended; the PERSIST action must be removed from the automation agents when this service release is applied. |
|
51591 |
Execution |
Internal |
|
51602 |
Collaboration |
On the Simple Tracker pager, the issue of Destination City showing the value of Origin City has been fixed. |
1-9892 |
51660 |
Planning Business Logic |
Order movements from same order release that are planned on different shipments should be unassigned separately. If one order movement is on a shipment that can not be deleted, the other order movement is on a shipment that is deletable, the second order movement should be unassigned. |
|
51663 |
Integration |
Fixed the unexpected child element error from the Release interface. |
|
51700 |
Infrastructure |
Added the property glog.login.suppressAccountPolicy to glog.base.properties. If this is true (which is the default), Account Policies on users are not paid attention to. |
1-9921 |
51701 |
Planning Business Logic |
When building a multistop shipment, when the direct distance from the first stop to the last stop is zero (that is the first and last stop are at the same location), GC3 now skips the out of route distance check. |
|
51724 |
Database |
Internal |
|
51745 |
Planning Business Logic |
Fixed a null pointer when consolidating shipment graphs. |
|
51783 |
Execution |
When order level information is specified on stop debriefs, it will be carried through to secondary charge shipments. |
|
51802 |
Database |
Internal |
|
51820 |
Collaboration |
Added ship_unit_line columns to file glog.compareengine.properties |
|
51841 |
Database |
Internal |
|
51847 |
Installation |
Internal |
|
51853 |
Commercial Invoice |
Default INCO term and Default Final INCO term are not working correctly on the Commercial Invoice Search page. The field labels were reversed. |
|
51863 |
Infrastructure |
This was an intermediate bug caused by the addition of Text triggers. |
|
51864 |
Execution |
Fixed an issue that could occur on some platforms (HP is one) where property overrides may not work. |
1-10080 |
51865 |
Execution |
Fixed ambiguous fields problem in CreateRechargeShipments. |
1-10054 |
51866 |
Infrastructure |
A previous bug (49975) broke the screen validation, but is now fixed. |
|
51872 |
Planning Business Logic |
Fixed a problem where a last stop with no times was nulling out the end time when changing a service provider on a shipment. |
|
51873 |
Execution |
Adjustments not reflecting in the total amount allocated. When allocation is run, there is an adjustment routine at the end that distributes or removes .01 in the currency of the allocation to account for round-off errors. For example, $100 divided evenly among 3 orders would allocate $33.33 to each order. Three orders with $33.33 allocated to each only totals $99.99. Since the allocated amount should total $100, the adjustment routine would end up adding .01 to one of the orders, so the allocated amounts would be ($33.34, $33.33, $33.33). This totals $100. A problem occurred, however. The adjustment routine only updated the allocation details but not the total amount allocated. In other words, even though the allocation details summed up correctly to $100, the total amount allocated remained at $99.99. This previously wasn't displayed on the screen, so it was never a problem. However, the shipment field, Total Trans Cost, displays the total allocated amount. So in the example above, it would display $99.99 in the shipment Total Trans Cost field, even though the allocation did indeed total $100. This became noticeable because the shipment Total Actual Cost showed the total amount $100, but the Total Trans Cost field, which is on the same screen, showed the allocated amount prior to adjustment, $99.99. This has been fixed so that the allocation total allocated amount in the database reflects the total allocated amount after adjustment not before, thereby allowing the shipment Total Trans Cost field to display the post-adjustment total allocated amount, and not the pre-adjustment total allocated amount. |
|
51883 |
Execution |
Job Primary Sell Shipment costs rate basis items are now working. |
|
51885 |
Execution |
When finding valid equipments using rates, GC3 now looks at the following 4 types of source and destinations combinations:
|
|
51886 |
Execution |
Updated the Shipping Agent Contact Manager label to Shipping Contact Agent Manager. |
|
51943 |
Infrastructure |
For the default stylesheet location used for branding to take effect, a user needed to be logged in. This should have not been the case. |
|
51982 |
Execution |
Internal |
|
51993 |
Execution |
Fixed a bug where allocation of a voucher for a consolidated invoice with only one child invoice would fail using the BY TOTAL allocation method. The BY TOTAL allocation method should never fail. |
|
52022 |
Execution |
Fixed the Null Pointer error that would occur on copy Freight Forwarding. |
|
52023 |
Infrastructure |
Fixed an XSL issue in Power Data view screen. |
|
52181 |
Database |
When running Compare Bulk plan process, a Bulk plan record is created, but the Log Process ID value is never filled in as it is when running a regular Bulk Plan. This makes it harder to find the correct log messages using the Log Viewer. |
|
52240 |
Collaboration Business Logic |
Open Tender (Broadcast, Spot Bid) were broken by Tender Contact Info. This is fixed to handle the special case of open tender where individual service provider's information on a shipment is replaced by a list of service provider's information. |
|
52326 |
Planning Business Logic |
Internal |
Issues with a description of Internal represent a technical correction that was not customer-reported but identified by internal development/quality assurance departments. In some cases, these issues resulted from system testing of new enhancements added in this service release. Contact Customer Support if you want the details on these issues.
SalesLogix Ticket |
G-Log Issue |
Component |
Issue Summary and Resolution |
|
49755 |
Consol |
The following enhancements were made to further extend the flight consols functionality:
|
|
49864 |
User Preferences |
Implemented the new user preference Change Stop Time Recalculate Default. The valid values should be Y or N. The default value for this user preference is Y. The default value for the Recalculate flag on the Shipment Manager action Change Stop Time is controlled by the value of this user preference. The flag defaults to checked if the user preference is Y and unchecked if the user preference is N. |
|
49924 |
Order Movement |
This enhancement allows you to manage Order Movement
Replace (OMR) data
through a user interface. A new Order Movement Replace Manager is now
available that allows you to find, view, edit, create new, and delete
existing Order Movement Replace records. You
can also manually process data. Another enhancement is to add status to
Order Movement Replace objects so that you can configure an automation
agent to process OMR at a later time. Currently, OMR data is processed
right after it is received through integration. |
|
50161 |
Gain Share |
This enhancement provides gain share functionality.
At a higher
level, gain share is a mechanism for third parties to increase customer
satisfaction by decreasing their customers’ overall costs. This
is accomplished by increasing savings in the third party freight spend
and in turn, passing a portion of that savings along to their customers.
As a primary
part of their core business, third party logistics providers generate
profits by selling logistics services to their customers and buying those
same services at a lower cost hence producing a profit margin; the ‘buy
low – sell high’ concept. Among
third parties, this is a common component in their contracts between themselves
and their customers. |
|
50241 |
ILT |
Denied party screening is now "transaction-based",
meaning a match of denied party to a location/contact and any subsequent
approval are in the context of a specific business object such as an order
release; current GC3 implementation have matches and their approvals applied
to a party, which can be shared by more than one business objects. GC3
also supports that location override information be used for screen instead
of the information in the GC3 contact; however this function is only
available to those business objects with location override; only order
release and shipment support location override. |
|
50533 |
Text Templates |
Enhancements to the current text template include:
|
|
50535 |
Document |
This enhancement includes the following features:
|
|
50536 |
Auto Assign Pay Terms |
Currently, the Apply Payment Terms shipment action allows
auto assigning payment terms to shipment costs. The
user chooses a “type,” either Customer or Master, which will run two separate
sets of rules to apply the payment method to each cost. This
enhancement expands this functionality so that payment terms may be set
on the shipment costs based on the individual rate costs within a rate
record. In
addition, the hard-coded rule logic was modified to allow for greater
flexibility. |
|
50537 |
Freight Forwarding |
This Freight Forwarding Additional Services Tab’s enhancement
gives the users five larger fields to contain the required information.
The following fields now allow at least 64 characters:
|
|
50538 |
Hazmat |
The following fields will be added to the Hazardous Material Manager:
The following field will be added to the Line Item of the Order Release and Freight Forwarding Managers:
Previously, when you clicked the Product Data Assignment button on the Ship Unit Line page, GC3 determines the corresponding Hazmat Item ID. From that it gets the Hazmat Generic ID and copies fields from the Hazmat Generic to the Line. GC3 now copies: ERG -> HAZ_ERG EMS -> HAZ_EMS ERG_AIR -> HAZ_ERG_AIR IS_NOS -> HAZ_ IS_NOS IS_MARINE_POLLUTANT -> HAZ_ IS_MARINE_POLLUTANT Since these fields now exist on both Hazmat and Hazmat Generic, the copy is done differently. For the checkboxes, if it is checked on either table then it is checked on the Line. For the Inhalation Hazard Zone field if only one of them is filled in, then that is copied to the Line. If both are filled in, then the Hazmat Item value is copied.
|
|
50539 |
Commercial Invoice |
The Commercial Invoice Creation Check enhancement will
prevent users from creating multiple Commercial Invoices for the same
Order Release Line. |
|
50540 |
Commercial Invoice |
The Commercial Invoice Read Only Fields enhancement
now allow changes on the Order Release and Order Release Line to be reflected
on the Commercial Invoice. An override-able field is provided so users
can change the value. |
|
50641 |
Transmission Purge |
A new and improved transmission purge has been added
to GC3. |
|
50922 |
Execution User Interface |
Added ability to send HTML instead of Plain text to
external systems. |
|
50965 |
International Rate Inquiry |
Implemented the following changes on the International Rate Inquiry page:
|
|
51109 |
Planning Parameter |
Added planning parameter BOOK ORDER USING EARLIEST CONSOL. Previously, the specific vessel chosen for a vessel
leg is the latest feasible vessel. Using
this new planning parameter, you can control this such that at certain
times if can be set to earliest. |
|
51116 |
Saved Query |
Loading of the saved queries on the Search pages are now cached to improve page reload performance. |
|
51225 |
Procurement Collaboration |
The following two new fields have been added to the View Lane Summary Action page:
Both these fields are Yes/No drop down fields. |
|
51242 |
Automation Agent |
The Copy Reference Number agent action is now available for Sell shipment. |
|
51260 |
Order Movements |
The following enhancements were made to the order movement business object:
|
|
51349 |
Automation Agents |
Added Move Order to Shipment as an Order agent action.
This prompts
for a shipment (typical case would be to use a variable) and a checkbox
for consolidate equipment. |
|
51330 |
Process Control |
Enhanced Process Control workflow to check whether a recurring process's user has been removed. If so, logs an exception and cancels the process. |
|
51343 |
Planning Parameter |
Added planning parameter SHIPMENT TOTAL PKG COUNT MULTIPLY
BY SU COUNT which by default is TRUE. When
set to FALSE,
the individual package counts will not be multiplied by the ship unit
count when summing the total package count for the shipment, rather it
will be a simple summation. |
|
51350 |
Rating |
The rate basis option SHIPMENT.ORALLOC_COSTS will only include allocated costs from order releases on the sell shipment being rated. |
|
51353 |
Event Reason |
Additional actions now support event reason functionality. |
|
51379 |
Procurement |
The following enhancements were made to the Procurement module: Sync Domain Data The Sync Domain Data screen will be modified to eliminate the need to repeatedly individually specify the Remote Host, Remote User, Remote Password, email address, and SMTP host. Instead, the system will provide a mechanism whereby this information can be specified once as domain specific glog properties. When the sync domain data screen is displayed the value in these fields will be automatically established via the domain specific glog properties. When the sync domain data screen is displayed, the field values will be initialized from the above properties. The user may then modify the values if desired. Display Shipments from Shipment Set Manager A new action was added to the Shipment Set manager to place the user directly into the shipment results page displaying the shipments in the given shipment set. Lane Summary Cell Detail A new Lane Summary Cell Detail page is provided to permit searching for a given lane summary by source location or destination location. Once a given Lane Summary Cell Detail record is found, you can ffollow a link to get directly into the Lane Summary. Lane Summary Starting Time Period Number A new column will be added to the lane summary table to indicate the first time period number to use when labeling the time periods in the lane summary. For example, if the first time period number is specified as 15, then the first time period will be 15, the second time period will be 16, and so on. Shipment Set and Lane Summary Count Fields A new field was added to the Shipment Set manager to indicate the number of shipments in the set. This will be 0 if the shipment set has not been built yet. A new field will be added to the Lane Summary to indicate the number of lanes in the lane summary. This will be 0 if the lane summary has not been built yet. Finding Projects by Location ID Use the new Lane Summary Cell Detail search page to find a given lane summary or summaries. Display Bid Rounds Action for a Project This new action was added to the Project user interface to display bid round finder results for all bid rounds in the given project. Shipment Copy You can use the P_Shipment search page to select the shipments to copy, then run a shipment copy action to make a copy of all selected shipments. You are prompted for a XID prefix used to construct a new XID for each shipment being copied. The user will also be prompted for an optional shipment set XID. When the Shipment Set XID is specified, after the system copies each shipment, the shipment is added to the indicated shipment set. Shipment Bulk Modifications You can use the Shipment search page to select the shipments subject to bulk modification. You are then able to bulk change the following fields to a constant value:
Recalc Distance & Cost You can use the Shipment search page to select the shipments subject to recalc distance & cost. For each selected p-shipment, the distance will be recalculated using a user specified rate offering. Null Out Lane You can use the Shipment search page to select the shipments subject to change and GC3 will then remove the lane on the selected p-shipments. You can then run the Fill Missing Lanes action to fill in the lanes according to the Geo-hierarchy Profile specified on a given Shipment Set. Remove from Shipment Set You can use the Shipment search page to select shipments subject to change. You are then prompted for a Shipment Set ID and GC3 removes all selected shipments from the given shipment set. Add to Shipment Set You can use the Shipment search page to select shipments subject to change. The user is then prompted for a Shipment Set ID and GC3 adds all selected shipments to the given shipment set. Delete Referenced Shipment The generic delete capability only permits the deletion of un-referenced shipments. This new action will support the deletion of referenced shipments. You can use Shipment search page, then use the delete referenced shipments action to delete the selected shipments. The selected shipment is removed, along with any data that references the given shipment (such as shipment set detail, lane summary detail, etc). |
|
51650 |
Workspace |
The text on the workspace buttons was not showing up correctly when using themes because entries were missing in the css files. I added these missing entries and now the button text should be correct. |
1-9937 |
51661 |
Automation Agent |
The Send Integration action is now available for the CLAIM object. |
|
51702 |
Planning |
This enhancement allows a user to see more routing options when running the order action‘Show Routing Options. Previously, the action only returned the least cost option for each selected itinerary. Now when the user clicks the Show Options button, the action returns the best shipping option for each selected itinerary. Then the user will be provided the ability to Refine Options for a selected itinerary. The action will then display all available shipping options for each leg of the selected itinerary. Each shipping option represents a potential shipment(s). Each shipping option will have its source location, destination location, service provider, total cost, transit time, preferred service provider indicator and allocation percentage displayed. Users will select a single shipping option for each leg. Once a user has selected a shipping option for each leg, they can then press the ‘Save’ button to perform feasibility checks on this combination of options. The user can then build the shipments using selected options. |
|
51743 |
Integration |
The following schema changes were made:
Logic is that when the TransactionCode = 'I' for insert and the ShipmentCostSeqno element is null or empty, then the sequence number is automatically generated. |
|
51744 |
Integration |
Established a property"glog.oaq.waitTime to control how long the Application server listener will wait for a message in the queue before exiting. The value for the property is an integer in seconds, or a predefined value of WAIT_FOREVER (wait indefinitely) or WAIT_NONE (do not wait). A value of 0 or WAIT_NONE appears to have an adverse impact on the CPU utilization for the database. We have set a default value of 120 seconds (2 minutes). The value can be changed in the Properties servlet, and the listener will be updated with the new value when either of the following occurs:
Also fixed the designation for the 'OracleAdvanceQueue' log id. The Id was previously mispelled such that nothing was appering the logs when the id was enabled. This should now be resolved. |
|
51760 |
Freight Forwarder |
Added order_release_remarks as a possible field for grid flattening on the manager layout screens. |
|
51763 |
Advanced Analytics |
For the Analysis Pathways reports, increase the number of rows that appear per page in the list. |
|
51764 |
Collaboration |
The following enhancements were made to the Appointment Manager: .
|
|
51769 |
Execution |
The following are Job-related enhancements:
|
|
51857 |
Infrastructure |
Added document distribution to the Document Type view and edit screens. |
|
51858 |
Infrastructure |
Added action Transmit Documents to support filtered reprinting. |
|
51859 |
Infrastructure |
Added Preview Document action to support previews from LOT documents. |
|
52261 |
Integration |
Added support of Inbound Consol XML. |
|
52270 |
Execution Business Logic |
Fixed a problem where the auto assign logic was erroring out when the rule used a single criterion made up of two parts, such as INCO Term and Term Location Text. Most criteria is only one part (Destination Location, Packaged Item, Payment Method, etc.) |
The next Service Release is scheduled for July 2005.
Contact G-Log Customer Support if you need assistance with this service release:
Email: |
support@glog.com |
Continental United States: |
+1.866.456.4423 |
International: |
+1.800.837.4717 |
Direct Dial: |
+1.610.491.3695 |
You should also have the following logs available before you call Customer Support:
dbpatch__<version>_<dbsid>_<date>.log (adds/updates data due to minor enhancements or fixes)
update_content.log (inserts/updates PUBLIC data included in the service release)