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 Releases 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.
Note: If you are using location capacity functionality, there may be an issue with this functionality on the Linux platform. If you experience a problem using Linux, you can do the following. You should only do this if you are running Linux and encounter a problem.
Edit the following file on your GC3 application server(s)
<gc3_install_dir>/weblogic/config/gc3domain/weblogic.conf
After the line:
wrapper.java.additional.19=-Djava.security.policy=%WL_HOME%/server/lib/weblogic.policy
You then need to restart GC3 for the change to take effect.
There are no database changes for this service release.
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:
There are no integration changes for this service release.
G-Log Issue |
Support Ticket |
Issue Summary |
Issue Resolution |
55880.5.0 |
|
Improve "invitation" email to carrier for Procurement |
Bugs #53837.5.0 and #55880.5.0 were both checked in
together since they were similar. Here is what was changed: |
56150.5.0 |
16148580.6 |
In the Job Details only remarks with a remark level of 1 should be displayed |
Job Details now only show the level 1 remarks. |
56153.5.0 |
16148530.6 |
When using User Preference of freight forwarding UI Type = SHIP_UNIT in combination with manager layouts for freight forwarding - Line Item Tab is displayed and License and Import/Export fields disappear |
Fixed the screen set to show the license and import/export fields. In custom screens there is no way to hide tabs like in XSL. However, the user can hide the line item tab themselves when creating their manager layout. |
57365.5.0 |
|
Smart Links icon intermittently does not display on Financial Overview screen |
The HTML cell width has been increased to handle this. The icons should always display now. |
57583.5.0 |
16150600.6 |
Unable to Change Com Method for Master B/L Notify type on a Shipping Agent Contact |
SHIPPING_AGENT_CONTACT_QUERY.XML was wrong. Fixed. |
57619.5.0 |
16149532.6 |
On the Tender Notification Screen the List of Contacts is showing more contacts then what is tied to the Service Provider ID. |
This is a designed behavior. |
57648.5.0 |
16150808.6 |
Release Schedule Instance action is not updating the stop distances for static trip |
Added logic to calculate stop distances after schedule instance is successfully rated. |
57661.5.0 |
16150882.6 |
Actual stop times not being set for events of static trips |
The problem is that the logic that sets the shipment
stop actual times was throwing an exception when trying to re-drive this
shipment. As the shipment is based on a static-trip ground schedule, we
should not re-drive it. The fix has been made to prevent a re-drive of
this kind of shipment when setting the actual times. |
57666.5.0 |
|
ADMIN GUIDE needs to be updated. |
Updated the GC3 Administration Guide so that it does not reference the audit trail. |
57715.5.0 |
16151018.6 |
Exchange Rate GID defined on Rate Offering accessorials is not used. DEFAULT/PUBLIC is. |
To fix this we added a new User Preference called "Display Rates/Accessorials as Entered". If the user sets this to "Yes" then the Rate Record and Accessorial Cost pages will show their currencies the way they were entered (and as they are in the database) instead of how they are set in user preferences. The default for this preference is "No" so existing users will not see a difference. |
57766.5.0 |
16151204.6 |
Notify Contact with a Contact Group is not finding the associated contacts |
This was an issue with the business map. |
57776.5.0 |
16151210.6 |
Clicking Check Global Classification UI button on the Order Ship Unit Line throws an error. |
Check Global Classification button now works. |
57779.5.0 |
16151240.6 |
NFRCs (non-freight related charges) are being created in the domain you are logged into and not the domain of job using the automatically apply NFRC action. |
NFRCs created by a successful NFRC Rule will be created in the same domain as the job, NOT in the domain running the 'Automatically apply NFRC Rules' action. |
57831.5.0 |
16151372.6 |
Assign rate for NFRC shipment fails from Job Details |
Fixed "No rate defined" message when running Assign Rate against an NFRC. |
57837.5.0 |
|
Need Port of Loading and Port of Discharge on the International Rate Inquiry Screen. |
Added the ability to specify the Port of Load and/or Port of Discharge on the International Rate Inquiry screen. |
57867.5.0 |
|
NullPointer and ClassNotFound exception when auto assigning based on OrderLineDestRegion |
Fixed the issue where NullPointer and ClassNotFound exceptions occurred when auto assign rule assigned something to order release lines and used the Dest Region criteria. |
57887.5.0 |
16151430.6 |
Remarks do not display on Order Information screen under Online Booking+Tendering |
1. Corrected the xpath of remarks of order release,
order base, shipment, |
57888.5.0 |
16151414.6 |
When 4 orders booked on the same shipment are replanned at the same time (via OMD agent), one of the orders will fail to replan even though it is feasible. |
This change allows a user to wait for the completion of all backend processes when submitting UI changes made to multiple business objects. In addition, the backend processes are executed in a single thread. For example, if there is an ORMD agent listening for order release changes events from UI and a user submits changes to 2 releases in a single edit session. The agent run triggered by changes to the second order release does not begin until the agent run for the first release is complete. In addition, the user will not see the result page until the two agent runs are complete. This enhancement is applicable only to the OMD UI feature in which changes to order bases or order releases are handled by an OMD agent. The following property must be added to turn off the enhancement. glog.agent.action.publishWait.doNotInterrupt.<OMD agent action class name>=USER |
57925.5.0 |
|
Postal Code validation does not factor in the State. |
State is now be factored into postal code validation. |
57934.5.0 |
|
Build multi-stop shipment didn't fail even though it fails location capacity constrain. |
The weight on the shipment stop at the point of location capacity check for multistop was not being set properly and causing the optimizer to think that it is feasible. After correction, it now fails to build a multistop shipment when the total weight exceeds capacity. Also, as expected, it builds successfully when the weight on the orders is reduced such that total weight is less than location max capacity. |
57937.5.0 |
|
NullPointerException Caused by Unknown Lanes |
It will now throw an exception that says "Some of the lanes attached to the bids are not there in the lane summary" instead of a null pointer error. |
57941.5.0 |
16151454.6 |
Agent actions triggered off of Move To Consol Shipment for temporary OM fail |
We will raise a new event at the end of MOVE TO CONSOL SHIPMENT action. This event will be raised on the parent ORDER_MOVEMENT if the action is performed on the temporary order movement. If the action is performed on a permanent order movement, then this event will be raised on this OM. The users can then write an agent that will listen to this event and set appropriate reference numbers and statuses. |
57953.5.0 |
16151524.6 |
Getting an error when trying to delete a lane summary stat |
Can now delete a Lane Summary Stat record. |
57999.5.0 |
|
Planning logic fails to adjust start time in some cases that built exceed location capacity max. |
This problem only occurs on the Linux platform. If encountered,the stack size should be changed to 256k. See the service release installation instructions above. |
58018.5.0 |
16151522.6 |
Bid Round actions are not being activated from Bid Round View Page |
Can now run actions from the Bid Round View screen. |
58032.5.0 |
16151840.6 |
Ship Unit Line Net Weight does not get reflected on the Ship Unit Net weight even when CALC SHIP UNIT FROM SHIP UNIT LINES is switched on |
Ship Unit Line Weight is now correctly reflected on the Order Release Ship Unit Line. |
58038.5.0 |
16151854.6 |
Saved queries using 'Before' are not working correctly |
Fixed the 'Before' operator for date controls when used in saved queries. This fix will only work for saved queries created after the patch has been applied. Old saved queries using the 'Before' operator will need to be recreated. |
58040.5.0 |
16151876.6 |
RemoveChildInvoiceFromConsolidatedInvoice needs the fix to allow many to be selected at one time |
Fixed the actions: Remove Child Invoice From Consolidated Invoice, Remove Child Bill from Consolidated Bill, Add Child Invoice to Consolidated Invoice, Add Child Bill to Consolidated Bill, to allow many to be selected at a time. |
58041.5.0 |
16151858.6 |
Voyage GID should not be validated from Conditional Tender UI screen |
In conditional booking code, add logic to skip GID validation if the GID is not Foreign Keyed to other table. |
58111.5.0 |
|
Add Order Movement status to define if Plot has been processed or not. |
Status OMR_PROCESS is added to OrderMovement. |
58122.5.0 |
16151948.6 |
Gc3App.ear File Needs to be updated to a bean count of 400 |
Increase the Max Beans in Cache to 400 for the Beans: |
58125.5.0 |
16151980.6 |
Editing global classification undoes changes to ship unit line. |
The edit buttons were using the wrong button tag. They were not calling the document update servlet. The manager template layout has been modified to save prior changes on the detail pages from the line item and ship unit tabs. |
58130.5.0 |
16151934.6 |
javax.servlet.ServletException when deleting global classification line on the ship unit line user interface. |
Updated the web XML template for the global classification delete servlet to redirect to the correct servlet. |
58171.5.0 |
|
Logistics guide does not check the compatibility flag on the service provider profile on the order template. |
Fixed the issue where the logic to build the Logistics Guide was not accounting for the compatible flag on the service provider profile for single leg itineraries. This caused the results for single leg moves to always include a service provider from the profile regardless of the compatible flag. |
58173.5.0 |
16152048.6 |
International Trade Logistics bean counts need to be set to 500 |
The following bean cache count has been set from 1000
to 500. |
58206.5.0 |
16151768.6 |
GC3 does not recognize Australia/Victoria as a valid time zone |
Added new timezone Australia/Victoria into GC3. |
58221.5.0 |
|
Appserver would freeze producing the following in the nohup.outExecuteThread: '36' for queue: 'default'" prio=5 id=0x1900 pid=9234 active, daemon at java/util/HashMap.put(Optimized Method)@0x227da779 |
Add synchronization in security realm to make it thread safe. |
58277.5.0 |
16152002.6 |
Generic Remote exception error when trying to release an order from the user interface. |
The interface should no longer access the database directly for these actions. They should now use a session bean. |
58312.5.0 |
|
Additional Order Base OMD Agent Action Required |
In glog.base.properties, need to set the following to
make the agent work as needed for this bug: |
58352.5.0 |
|
Multi-domain data synchronization doesn't work |
Previously, it was not possible to synchronize multiple domains in a single operation. With the change you can specify a % in domain name on sync domain data screen. This way you can synchronize a parent domain along with all child domains. |
58354.5.0 |
16151244.6 |
Tender notifications are using default contacts and not specified shipper contact |
Modified planning code to use shipment domain to search tender contact base on contact_corporation record. |
58391.5.0 |
|
Got an array index out of bound when build shipment manual. |
This bug is a result of the 'capacity sharing shipment stops' being not populated on TShipmentStop in some actions like 'build shipment - manual' and bulk plan with 'calculateWaitTimeUsingLCinBP' true creating an empty 'tShipmentStops' that is passed into LocationCapacityOptimizer. Fixed that and it works fine now. |
58403.5.0 |
|
Order Base Release Instructions If Condition |
An agent action called "IF RELEASE INSTRUCTION CHANGE ONLY" is created for data query type ORDER BASE. The action can only be used in conjunction with agent event "ORDER BASE - MODIFIED". It will return true if the data changes triggering event "ORDER BASE - MODIFIED" are from ob_release_instruction and ob_su_release_instruction. |
58423.5.0 |
16152392.6 |
Custom FFORD screen - Involved Party Location giving XID error. |
Selecting an Involved Party Location where the Location ID exists in multiple domains now works correctly. |
58576.5.0 |
16152558.6 |
Itinerary cannot be used to build a feasible shipment |
We show message "Itinerary cannot be used to build a feasible shipment." for each itinerary that has no shipment built Unfortunately, when determining whether an itinerary has shipment built or not, we specified wrong XML path. As a result, none of these itineraries was determined to have shipment built, and on the screen, the same valid itineraries were listed as "Itinerary cannot be used to build a feasible shipment." again. Changed to fix the XML path. |
58619.5.0 |
|
Transorder Delete fails if the related order releases have Order Movements but are not on shipments |
ObProcessor::unassignOrderReleases checks if there are order_movements related to the order base. If yes, those order releases will be unassigned. |
58660.5.0 |
16152622.6 |
BN_SEQUENCE for OB_SHIP_UNIT_XID is not resetting properly. |
Fixed the error when using business number generator for ob_ship_unit |
58818.5.0 |
|
Unable to create consol from Voyage Schedule |
Modified NotifyContact to allow null shipment domain call from planning code. |
There are no enhancements for this service release.
glogserver.jar
glog\gc3webapp\WEB-INF\web.xml
glog\config\maps\ui\*
glog\oracle\insert_security_roles.sql
weblogic\config\gc3domain\applications\GC3App.ear
apache\htdocs\html\help\webhelp\en\*
apache\htdocs\js\roe\OrderEdit.js
apache\htdocs\xsl\accessorialcost\AccessorialCostBase.xsl
apache\htdocs\xsl\accessorialcost\AccessorialCostUnitBreaks.xsl
apache\htdocs\xsl\accessorialcost\AccessorialCostViewBase.xsl
apache\htdocs\xsl\carrier\ViewCommMethods.xsl
apache\htdocs\xsl\comm\Fields.xsl
apache\htdocs\xsl\comm\Remarks.xsl
apache\htdocs\xsl\comm\Style.xsl
apache\htdocs\xsl\comm\uom.xsl
apache\htdocs\xsl\contact\CommonContact.xsl
apache\htdocs\xsl\contact\ViewCommonContact.xsl
apache\htdocs\xsl\job\JobFinancial.xsl
apache\htdocs\xsl\rate\RateGeoAttributes.xsl
apache\htdocs\xsl\rate\RateGeoCostBase.xsl
apache\htdocs\xsl\rate\RateGeoCostBase2.xsl
apache\htdocs\xsl\rate\RateGeoCostUnitBreaks.xsl
apache\htdocs\xsl\rate\RateGeoMisc.xsl
apache\htdocs\xsl\rate\RateGeoStops.xsl
apache\htdocs\xsl\rate\ShowUnitBreaks.xsl
apache\htdocs\xsl\rate\ShowWeightBreaks.xsl
apache\htdocs\xsl\rate\view_RateGeoAttributes.xsl
apache\htdocs\xsl\rate\view_RateGeoCostBase.xsl
apache\htdocs\xsl\rate\view_RateGeoMisc.xsl
apache\htdocs\xsl\rate\view_RateGeoStops.xsl
apache\htdocs\xsl\rateroute\RouteAndRates.xsl
apache\htdocs\xsl\rateroute\input.xsl
apache\htdocs\xsl\rateroute\result.xsl
apache\htdocs\xsl\roe\OrderEdit.xsl
apache\htdocs\xsl\tenderresp\ExecTendConditionalBooking.xsl
apache\htdocs\xsl\tenderresp\ExecTendMain.xsl
apache\htdocs\xsl\tenderresp\ExecTendMore.xsl
apache\htdocs\xsl\tenderresp\ExecTendOrders.xsl
apache\htdocs\xsl\uic\GetItineraryOptions.xsl
glog\config\glog.base.properties
glog\config\glog.recalc.properties
glog\glog_resources\glog.ejb-metadata.properties
glog\oracle\script8\content_glogowner\ACTION.csv
glog\oracle\script8\content_glogowner\AGENT_ACTION.csv
glog\oracle\script8\content_glogowner\AGENT_EVENT.csv
glog\oracle\script8\content_glogowner\APP_ACTION.csv
glog\oracle\script8\content_glogowner\APP_ACTION_RESP_PARTY_P.csv
glog\oracle\script8\content_glogowner\NOTIFY_SUBJECT.csv
glog\oracle\script8\content_glogowner\NOTIFY_SUBJECT_STYLESHEET.csv
glog\oracle\script8\content_glogowner\PREFERENCE.csv
glog\oracle\script8\content_glogowner\PREFERENCE_VALUE.csv
glog\oracle\script8\content_glogowner\STATUS_FUNCTOR.csv
glog\oracle\script8\content_glogowner\STATUS_TYPE.csv
glog\oracle\script8\content_glogowner\STATUS_VALUE.csv
glog\oracle\script8\content_glogowner\TIME_ZONE.csv
glog\oracle\script8\content_glogowner\TIME_ZONE_LOCALE.csv
glog\oracle\script8\content_glogowner\TRANSLATION.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_NOT_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_D_en.csv
glog\oracle\script8\content_glogowner\TRANSLATION_NOT.csv
glog\oracle\script8\content_glogowner\V50BP_ACTION.csv
glog\oracle\script8\content_glogowner\V50BP_AGENT_EVENT.csv
glog\oracle\script8\content_glogowner\V50BP_APP_ACTION.csv
glog\oracle\script8\content_glogowner\V50BP_APP_ACTION_RESP_PARTY_P.csv
glog\oracle\script8\content_glogowner\V50BP_DEPENDENCY_SERVICE.csv
glog\oracle\script8\content_glogowner\V50BP_NOTIFY_SUBJECT.csv
glog\oracle\script8\content_glogowner\V50BP_NOTIFY_SUBJECT_STYLESHEET.csv
glog\oracle\script8\content_glogowner\V50BP_PREFERENCE.csv
glog\oracle\script8\content_glogowner\V50BP_PREFERENCE_VALUE.csv
glog\oracle\script8\content_glogowner\V50BP_STATUS_FUNCTOR.csv
glog\oracle\script8\content_glogowner\V50BP_STATUS_TYPE.csv
glog\oracle\script8\content_glogowner\V50BP_STATUS_VALUE.csv
glog\oracle\script8\content_glogowner\V50BP_TIME_ZONE.csv
glog\oracle\script8\content_glogowner\V50BP_TIME_ZONE_LOCALE.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_NOT_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_D_en.csv
glog\oracle\script8\content_glogowner\V50BP_TRANSLATION_NOT.csv
glog\oracle\script8\content_glogowner\V50BP_csvdiff_tables.txt
glog\oracle\script8\content_glogowner\V50BP_insert_glogowner_data.txt
glog\oracle\script8\content_glogowner\V50BP_update_glogowner_data.txt
glog\oracle\script8\content_glogowner\xml\agent_action\if_release_instruction_change_only.txt
glog\oracle\script8\content_glogowner\xml\manager_layout\freight_forwarding.xml
glog\oracle\script8\content_glogowner\xml\user_menu_layout\adminmenu.xml
glog\oracle\script8\content_glogowner\xml\user_menu_layout\dbaadmin.xml
glog\oracle\script8\content_glogowner\xml\user_menu_layout\defaultmenu.xml
glog\oracle\script8\content_procure\xml\user_menu_layout\procadmindefault.xml
glog\oracle\script8\content_procure\xml\user_menu_layout\servprovadmin.xml
glog\oracle\script8\content_procure\xml\user_menu_layout\servprovmenu.xml
glog\oracle\script8\pkg\domainman.pkb
glog\server\eventreason\StageEventReasonData.omit
The next Service Release is scheduled for April 2006.
Contact G-Log Technical 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)