Mobile Layout

This page is accessed via Configuration and Administration > User Configuration > Mobile Layout.

A mobile layout contains the default look and feel of the Oracle Transportation Mobile Web Application. By copying and editing a mobile layout, you can change the number of boxes shown, the color and label of the boxes, the saved query used to fill the boxes, etc. Use the Copy Mobile Layout action to duplicate the public or other custom mobile layout. The mobile layout is configured using JSON and REST API integration. See the REST API for Business Object Resources Guide for instructions on how to make API calls. See Mobile Metadata Expression Syntax for details on how to structure the JSON.

If you are creating a mobile interface that your driver will use to make his deliveries, copy and then modify the copy of DEFAULT_MOBILE_LAYOUT.
If you are creating a mobile interface that a carrier or service provider will use to accept bids, copy and then modify the copy of SERVPROV_MOBILE_LAYOUT.

Creating a Mobile Layout

Note: While you can create a new mobile layout by clicking New, it is recommended that you select a sample mobile layout and click Copy Mobile Layout. If you are creating a mobile interface that your driver will use to make his deliveries, copy and then modify the copy of DEFAULT. If you are creating a mobile interface that a service provider will use to accept bids, copy and then modify the copy of SERVPROV.

Enter a Mobile Layout ID.
Enter a Name to describe the layout.
Select a Domain Name.
Edit the JSON text area to customize how your browser-based mobile app will appear.
Click Finished.

After creating a mobile layout, select it in your user preferences in order to use it.

Configuring JSON

Each section of the JSON configures how the browser-based mobile app will appear. See Mobile Metadata Expression Syntax for details on how to structure the JSON.

Many of the following structures are shared between the DEFAULT mobile layout and the SERVPROV mobile layout. Items that are only in the SERVPROV mobile layout appear in a separate section later in this topic.

DEFAULT_MOBILE_LAYOUT

The DEFAULT layout is designed for a driver user.

General

These settings control what is displayed when you tap the User button in the upper-right, next to the Home button.

showNickname: Set to true to display the user's nickname.
showUserID: Set to true to display the user's ID.
showUserRole: Set to true to display the user's role.
showMobileLayoutID: Set to true to display the Mobile Layout ID under the user information menu. Default: true.
idleTimeout: Allow you to configure the idle timeout so that a mobile user signs out when they are idle for the indicated number of minutes. The maximum allowed value is 480. Default is 0.
expandShipment: Controls the child elements you want to show as expanded, by default. For example, to expand Shipment Remarks, Shipment Stop Reference Numbers, and Shipment Stop Remarks you would add:

"expandShipment": "remarks,stops.refnums,stops.remarks",
You can then decide which of those values you would like to see in the mobile web application. For example, to show the Shipment Remark value for Qualifier "AIRLINE" you would add this:

"shipmentInfo": [
{
"name": "Shipment Airline",
"value": "remarks/items[remarkQualGid eq 'AIRLINE']/remarkText"
}
]
NFRStopEventsOptional: Set this to true to make Arrived/Departed Events optional for NFR (Non Freight Related) stops for drivers.
showNFRStops: Set to false to to hide Non Freight Related (NFR) stops on the driver flow on the Shipment List page.
multipleActiveShipments: When set to true, drivers have the ability to start multiple shipments. When the "Active Shipments" box on Dashboard is selected it will show a list of active shipments. The default is false, meaning drivers will only see one active shipment. Note that if there are shipments that begin from different start location from the current shipment's ending location, review the NFR stops in subsequent shipment. For example, if the shipments are processed out of order, the NFR stop for the earlier shipment may not be relevant.
verificationOptions: Controls the labels on the buttons for verifying actions in the app. The default is "Ok-Cancel" and you can also set this to "Yes-No".
shipmentIdOption: If you want to show a shipment value other than the shipment ID, you can choose to display any field on a shipment instead, such as the shipmentName. This is configurable much like PrimaryHeader. The default is "shipmentXid".

landingPage

You can customize the landing page of your mobile app by changing API connection points, saved queries, titles, and button/label colors.

For example:

{
"boxId": 1,
"endPoint": "/logisticsRestApi/resources/v2/custom-actions/savedQueries/shipmentNoSSUs",
"savedQueryGid": "DRIVERS CURRENT SHIPMENT",
"title": "Active Shipment",
"backgroundColor": "green",
"fontColor": "white",
"boxType": "activeShipment",
"shipmentsType": "activeShipment"
}

and

{
"boxId": 2,
"endPoint": "/logisticsRestApi/resources/v2/custom-actions/savedQueries/shipmentNoSSUs",
"savedQueryGid": "DRIVERS CONFIRMED SHIPMENTS",
"title": "Confirmed Shipments",
"backgroundColor": "orange",
"fontColor": "black",
"boxType": "shipmentsCount",
"shipmentsType": "confirmed",
"shipmentListTabId": "confirmed",
"shipmentListTabName": "Confirmed"
}

dynamicBoxes
- boxId: The unique whole number of the box you are customizing on the landing page. The UI displays the buttons based on the order they are in the JSON file, not the numbers in the boxId.
  
  Note: If you are using a custom mobile layout and change the glog.fusion.cil.config.defaultShape.v2.shipments property from "shipmentNoSSUs" to "shipments" then you need to change all the endPoints for your boxeIds from using "shipments" to using "shipmentNoSSUs" in that custom mobile layout.
- endPoint: The API endpoint you are referencing.
- savedQueryGid: The saved query that controls what information is being returned through the API call. You can use your own saved query here.
- parameterValues: Used with the DRIVERS COMPLETED SHIPMENTS and SERVPROVS COMPLETED SHIPMENTS savedQueryGids to control the number of shipments which appear in the Completed box. By default, only shipments which have been Completed in the last 7 days will be returned.
- title: The title of the box.
- backgroundColor: The background color of the box. You can use common HTML names of colors or HEX color codes.
- fontColor: The font color. You can use common HTML names of colors or HEX color codes.
- boxType: It is not recommended that you change this setting. boxtype and shipmentsType must match and correspond with a valid saved query. You must have one box defined as the activeShipment in order to access other features, such as the addEvent. The possible values are activeShipment and shipmentsCount.
- shipmentsType: For a boxType of shipmentsCounts, it can be "all," "confirmed," "assigned," or any unique label. When defining this value, shipmentsType and shipmentListTabId must be the same unique value. For boxType of activeShipment this must also be "activeShipment."
- shipmentListTabId: Used when the shipmentsType is "shipmentsCounts."
- shipmentListTabName: Used when the shipmentsType is "shipmentsCounts." This is the tab name displayed in the mobile application.
- hideOnDashboard: When set to true, the corresponding box will not be shown on the dashboard.
- refreshOnHome: When set to true, the corresponding box will refresh every time you tap the Home button. If it is false, the box will only be refreshed when you tap the Refresh button or when the screen loads when you sign in.
- savedQueryResultCount: Defines how many saved query results are displayed. Setting to too high a value will slow down the system. Valid values are 1 to 100. Defaults to 25.
- allowMore: The savedQueryResultCount sets how many query results are displayed. If you set allowMore to true, then you get an option to load more query results than were originally returned. When you select that option, the next set of results are returned. The additional amount returned is determined by the savedQueryResultCount value. Default: false.
- shipmentListOverride: Controls how you override shipment fields that are shown in a box. Any changes made to an overridden shipmentList take precedence over edits in a standard shipmentList. See the overrideSections for details.
- shipmentDetailsOverride: Controls how you override shipment fields that are shown in a box. Any changes made to an overridden shipmentDetails take precedence over edits in a standard shipmentDetails. See the overrideSections for details.
- shipmentList
  - confirmAll: This only applies if the shipmentsType is "assigned." If set to true, a Select All checkbox and a Confirm Selected button are shown. Default: false.
    
    Note: This element only applies to DEFAULT/Drivers and is not used by SERVPROV.
  - defaultSortCriteria: Changes the default option for each shipment type. Valid default values that can be assigned for different shipments are:
    - All Shipments: startDate, endDate, shipmentXid.
    - Accepted: startDate, endDate, shipmentXid, tenderDate.
    - Active: startDate, endDate, shipmentXid.
    - Assigned: startDate, endDate, shipmentXid.
    - Completed: startDate, endDate, shipmentXid.
    - Confirmed: startDate, endDate, shipmentXid.
    - Open Spot and Broadcast: startDate, endDate, shipmentXid, tenderDate, timeoutDate.
    - Submitted Spot and Broadcast: startDate, endDate, shipmentXid, bidAwarded.
    - Tendered: startDate, endDate, shipmentXid, tenderDate, timeoutDate.

shipmentList and shipmentDetails

For Shipment List and Shipment Details, the default value for primaryHeader is primaryHeader: "firstEquipmentGroupGid".

Alternatively, you can use this to get a reference number value for the BM qualifier in the metadata:

primaryHeader: "refnums/items[shipmentRefnumQualGid eq 'BM']/shipmentRefnumValue"

primaryHeader: "attribute8"

New fields can only be added on shipmentDetails on header and footer sections. For example, for Shipment List:

"shipmentList": {
"primaryHeader": "refnums/items[shipmentRefnumQualGid eq 'BM']/shipmentRefnumValue",
"secondaryHeader": "attribute8",
"sourceLocation": [
"locationName",
"city",
"provinceCode"
],
"destLocation": [
"locationName",
"city",
"provinceCode"
]
},

E.g for Shipment Details

"shipmentDetails": {
"primaryHeader": "firstEquipmentGroupGid",
"secondaryHeader": "",
"dataFieldHeader": [
{
"name": "Loaded Distance",
"value": "loadedDistance"
},
{
"name": "Load Config Engine Type",
"value": "loadConfigEngineTypeGid"
},
{
"name": "Shipment RefNum",
"value": "refnums/items[shipmentRefnumQualGid eq 'BM']/shipmentRefnumValue"
}
],
"footerLabel": "Shipment Totals",
"dataFieldFooter": [
{
"name": "Total Gross Weight",
"value": "totalWeight"
},
{
"name": "Total Gross Volume",
"value": "totalVolume"
},
{
"name": "Total Ship Unit Count",
"value": "totalShipUnitCount"
}
]

For details on how the API integration works with shipmentList and shipmentDetails, see these areas of the API guide:

Location > Get a Location
Shipments > Get a Shipment
Shipments > Stops > Get a Stop
Shipments > Stops > Details > Get a Detail

Shipment List and Details use the following parameters:

showTotalGrossWeight: Set to true to show shipment total gross weight in the shipment information. Default: true.
showTotalGrossVolume: Set to true to show shipment total gross volume in the shipment information. Default: true.
showTotalShipUnitCount: Set to true to show shipment total ship unit count in the shipment information. Default: true.
showContactDetails: Set to true to show shipment contact details in the shipment information. Default: true.
involvedPartyQualifier: If "showContactDetails" is set true, then the contact information will be pulled from this qualifier. Default: LOGISTICS. Valid value: An involved party qualifier GID.
sShipUnitRefnumQualGid: If the shipment ship unit reference number qualifier GID is given here, the same reference number text will be displayed in the shipment information. Valid value: shipment ship unit reference number qualifier GID.
showShipmentRefnums: If set to true, then shipment reference numbers are displayed in the mobile web application.
expandAccordion: Set to true if you want the shipment reference numbers to be shown in an expanding text area.
expand[Specific]Accordion: Set to true to provide ability to expand or collapse corresponding areas.
- expandDataFieldFooterAccordion
- expandContactDetailsAccordion
- expandEventsAccordion
- expandDocumentsAccordion
- expandStopDetailsAccordion
- expandOrderReleasesAccordion
defaultMapZoomLevel: Controls the default zoom level of the map. If you set the value above 100, the app uses 100. If the value is set below 0, the app uses 12. The default is 12. Setting above 17 has no noticeable effect.
showStopDocuments: Set to true to show all documents (images and PDFs) available on the shipment stop.
expandStopDocumentsAccordion: Set to true if you want the stop documents to be shown in an expanding text area.
shipmentInfo: Lets you add a line with more info about the shipment using a "name": "Shipment Attribute 12", "value": "attribute12" format. For example:
"shipmentInfo": [
{
"name": "Shipment Total Gross Weight",
"value": "totalWeight | uomTwoDecimalFormatter"
},
{
"name": "Shipment Total Gross Volume",
"value": "totalVolume | uomTwoDecimalFormatter"
},
{
"name": "Shipment Total Ship Unit Count",
"value": "totalShipUnitCount"
},

{
"name": "Shipment Refnum",
"value": " refnums/items[shipmentRefnumQualGid eq 'GLOG']/shipmentRefnumValue"
}
]

orderReleases

showOrderReleases: Set to true to display order releases.
orderReleasesLabel: Sets the text that is displayed for the section when viewing order releases.
expand: Defines which of the objects can be expanded so you can show data from child records. Applies to refnums, remarks,and involvedParties.
popupEnabled: Set to true to show shipment reference numbers in a popup.

The "expand" parameter is not related to the accordion expand options used elsewhere. It defines which of the objects can be expanded in the REST API so you can show data from child records.

The following example is for the refnum option.

{
"name": "Vessel",
"value": "refnums/items[orderReleaseRefnumQualGid eq 'VESSEL NAME']/orderReleaseRefnumValue"

}

addEvent

You can customize the Add Event functionality of your mobile app by limiting location access, photo access, and signature access.

For example:

"addEvent": {
"allowCurrentLocation": true,
"photos": true,
"signature": true
"allowImageCompression": false,
}

allowCurrentLocation: Set to true to let the app insert the users' current location. If it is true, the option of "CURRENT LOCATION" appears in the application when selecting locations. If set to false, the user will not be able to enter a shipment event with "current location", and can only enter events with shipment stops as location.
Default: true.
photos: Allows the users to attach photos. If set to false, you will not be able to upload photos or documents with shipment events.
Default: true.
signature: Allows the users to attach a signature. If set to false, you will not be able to upload a signature along with the shipment event. Default: true.
allowImageCompression: If set to true, the system will compress image as per the image minimum size defined. Default: false.
minimumImageSizeForCompression: This will only come in play if "allowImageCompression" is set to true. The system will compress images more than the minimum size to within the value. Value is always defined in MB. Valid value: a number. Default: 1.
captureReceivedQuantity: This section records received values for a shipment ship unit, including the weight received or volume received. It contains the following parameters:
- enableBarCodeScanner: Enable this to activate the barcode scanner. Default: false. If enabled, you can configure what to capture by the scan:
  
  "captureReceivedQuantity" : {
  "enableBarCodeScanner": false,
  "captureReceivedQuantityEnabled": true,
  "captureReceivedShipUnit": true, (ship unit)
  "captureReceivedWeight": true, (weight)
  "captureReceivedVolume": true, (volume)
  "sShipUnitRefnumQualGid": "" (set to GUEST.MYQUAL_GID to display a reference number instead of the shipment ship unit ID.)
  - captureReceivedQuantityEnabled: This allows the user to capture a shipment received quantity along with the shipment event. If set to false, the user will not be able to capture the received quantity. Default: true.
  - captureReceivedShipUnit: This allows the user to capture a received ship unit count under the received quantity. If set to false, the user will not be able to capture the received ship unit count. Default: true.
  - captureReceivedWeight: This allows the user to capture the received weight under the received quantity. If set to false, the user will not be able to capture the received weight. Default: true.
- captureReceivedVolume: This allows the user to capture the received volume under the received quantity. If set to false, the user will not be able to capture the received volume. Default: true.
- captureReceivedRemark: Allows you to show/hide the Remark field when entering received quantities. Default: true.
- sShipUnitRefnumQualGid: This will replace the sShipUnitGID to show on the Add Event screen. It will help you provide a number/ID other than the sShipUnitGID which can be helpful for a user to identify the ship unit ID.
- mandatoryCaptureReceivedQuantity: Use this to make the Received Ship Unit Count required based on Stop Type and Quick Code. For example, if you want to specify the fields are always required on Pickup Stops, you would use:
  
  "mandatoryCaptureReceivedQuantity": {
  "stopType": [
  {
  "type": "P",
  "required": true
  }
  
  },
  
  For example, if you want to specify the fields are required on Delivery Stops only for Quick Codes ARRIVED_AT_STOP and DEPARTED_FROM_STOP, you would use:
  
  "mandatoryCaptureReceivedQuantity": {
  "stopType": [
  {
  "type": "D",
  "requiredForEvents": ["ARRIVED_AT_STOP","DEPARTED_FROM_STOP"]
  }
  
  },
remarks
- captureRemarks: This allows the user to capture remarks along with shipment events. Default: true.
- remarkQualifierGid: If "captureRemarks" is set to true, the remark qualifier GID can be changed from default to any other value. Valid value: remark qualifier GID. Default: MOBILE and a FieldType of Text. You can also define a label, a field type (Text, Number, or fixedList), and indicate if this is required or not. For example:
  
  "remarks" : {
  "captureRemarks": true,
  "remarkQualifierGid": [
  {
  "remarkQualifierGid": "MOBILE",
  "label": "Mobile",
  "requiredForEvents": ["ARRIVED_AT_STOP","DEPARTED_FROM_STOP"]
  },
  {
  "remarkQualifierGid": "REM",
  "label": "Rem",
  "required": true,
  "fieldType": "Number"
  },
  {
  "remarkQualifierGid": "AIRLINE",
  "label": "Airline",
  "fieldType": "fixedList",
  "options": [
  {"label": "", "value": ""},
  {"label": "American", "value": "AMERICAN"},
  {"label": "Southwest", "value": "SOUTHWEST"},
  {"label": "Spirit", "value": "SPIRIT"}
  ]
  }
  ]
  }
expandRemarkAccordion: Set to true to provide ability to expand or collapse corresponding areas.
expandShipUnitAccordion: Set to true to provide ability to expand or collapse corresponding areas.
exceptionEvent: The Add Exception Event button on Mobile Event screen is configurable and by default is not displayed. You can configure the label, location, and event details (quick code) for the Add Exception Event button. An event detail or quick code is mandatory in order to show this button.
- exceptionEventLocation: Can be current, first or last. The default is current.
restrictEventDateChange: You can restrict the ability to enter event dates based on the mobile date and time. "restrictEventDateChange" can have values of false, true, or "future". If it is false, there will be no restriction on entering an event date. If it is true, you cannot change the date and time from what is displayed. If it is "future", you cannot change the date and time to any future date and time, but can change to past date and time. Default: false.
shipUnitAutofill: Set to true to auto-fill the ship unit received quantity from the planned quantity when you open the ship unit received quantity page. The default is false.
defaultArrivedQuickCode: Allows you to change the default quick codes. The default is "ARRIVED_AT_STOP". If this is incorrectly defined, the Shipment Details page may not display the Arrived/Departed buttons.
defaultDepartedQuickCode: Allows you to change the default quick codes. The default is "DEPARTED_FROM_STOP". If this is incorrectly defined, the Shipment Details page may not display the Arrived/Departed buttons.

dockScheduling

Allows both drivers and carriers to see, add, modify, and delete appointments.

enableAppointments: Shows/hides the Appointments icon on the Details page. This icon will appear for all boxes, not just the Dock Appointments box. Default: false.
showAppointmentFields: Shows/hides the Appointment Pickup and Delivery fields on the Details page. Default: false.
locationResourceTypeGid: Allows you to select which resource type to show when querying appointments. These are set on the Resource tab of the Location manager. Default: "DOCK DOOR".

branding

You can brand your mobile app by adding a custom logo, URL, and title.

logoImage: A path to a custom logo. The recommended image dimensions are: width: 137px, height: 18px. Images of other sizes will be resized to those dimensions.
logoUrl: The URL that opens when you tap on the logo.
title: The title that appears next to the logo.

For example:

"branding": {
"logoImage": "/images/icons/system/lengthwise_top.gif",
"logoUrl": "https://www.google.com",
"title": "Your Title"
}

externalUrls

If you want a user to access websites outside of Oracle Transportation Management, you can define external URLs. When you set these up and a user taps on the link, the URL will open in a new tab in the mobile browser. There are no default external URLs defined.

"externalUrls" : [ ]

For example:

"externalUrls" : [
{
"name": "Google",

"url": "https://www.google.com"
},

]

quickcodes

You can configure XID, GID, or the Description in the Quick Code droplists.

showGids: If you set "showGids" to true, GIDs will be shown in the droplist.
showDescriptionIfExists: If "showDescriptionIfExists" is true, a description will be shown in the list.

For example:

"quickCodes": {
"showDescriptionIfExists": false,
"showGids": false

}

overrideSections

You can override the shipmentList and shipmentDetails sections for certain boxes by duplicating those sections in the overrideSections element. For example, you may want to override your default shipment details to show location details only in active and tender shipments and also hide those details on spot bid open and accepted shipments. To use this feature, two elements can be added to any boxes: shipmentListOverride and shipmentDetailsOverride.

For example, here is how to override shipmentList and shipmentDetails sections of the "Open Stop and Broadcast Bids" box.

Copy the shipmentList section in the JSON.
Within the JSON, find the "overrideSections": {} and paste the entire shipmentList within the brackets of that section.
Rename the shipmentList to match the one defined in the example below, e.g. "MyShipmentList". The same can be done for the shipmentDetails section.
Edit the shipmentList in the overrideSections to change what is displayed, such as by hiding details you do not want to display on spot bids.

For example, this box has been configured to use the shipmentListOverride and shipmentDetailsOverride. The new shipmentList and shipmentDetails are named "MyShipmentList" and "MyDetailsList." Further down in the JSON, the overrideSections contains the MyShipmentList referenced in the box definition.

{
"boxId": 6,
"endPoint": "/logisticsRestApi/resources/v2/custom-actions/savedQueries/shipmentNoSSUs",
"savedQueryGid": "SERVPROVS OPENSPOTBID SHIPMENTS",
"title": "Open Spot and Broadcast Bids",
"backgroundColor": "brown",
"fontColor": "white",
"boxType": "shipmentsCount",
"shipmentsType": "openSpotBidServProv",
"shipmentListTabId": "openSpotBidServProv",
"shipmentListTabName": "Open Bids",
"hideOnDashboard": false,
"refreshOnHome": false,
"savedQueryResultCount": 25,
"shipmentListOverride": "MyShipmentList",
"shipmentDetailsOverride": "MyDetailsList"

}

...

"overrideSections": {

"MyShipmentList": [custom changes ]...

SERPROV_MOBILE_LAYOUT

This type of layout is used by a carrier user.

The following elements appear only in the SERVPROV mobile layout.

endPoint: The API endpoint you are referencing.
Note: Anyone that is using a custom SERVPROV Mobile Layout will need to update their SERVPROVS OPENSPOTBID SHIPMENTS and SERVPROVS SUBMITTEDSPOTBID from "endPoint": "/logisticsRestApi/resources/v2/custom-actions/savedQueries/shipmentNoSSUs" to "endPoint": "/logisticsRestApi/mgmt/mobile/runSpotBidSavedQuery".
flowType: Indicates how the layout is used, such as by a driver or service provider. If undefined, the layout is used for the driver. Set it to "servprov" to make the layout be for a service provider. Default (in SERVPROV): servprov.
showCost: If set to true, a carrier can see shipment costs in the OTM Mobile Web Application. Default: false.
shipmentList
- showServiceProvider: If set to false, the carrier ID would not be shown in shipment information. Default: true.
- acceptAll: This only applies if the shipmentsType is "tendered." If set to true, a "Select All" checkbox and an "Accept Selected" button are shown. Default: false.
shipmentDetails
- spotBidRemarks: You can set this to add/view remarks when bidding on a spot tender.
  - showRemarks: Set to true to see the remarks.
  - captureRemark: Set to true to enable editing of the remark.
  - remarkRequired: Set to true to make the Remark field required.
  - remarkQualifierGid: Sets the default remark qualifier for the mobile app. Default: MOBILE.
  - expandRemarkAccordion: Set to true to expand the remarks accordion. When the Remarks accordion is expanded a list of remark qualifiers for the added remarks will be shown.
shipmentUpdateDetails
- refnumQualifierGid: Sets the default reference number qualifier for the mobile app. Default: MOBILE.
invoiceList: Shows invoice information. To enable this, set the hideOnDashboard to "false" for the invoices dynamic box.
invoiceDetails: Shows the details of the invoice.
- accessorialCodeGids: If you want to have accessorial codes populate into the field, define them here. For example:
  "accessorialCodeGids" : [ "MOBILE.0011", "MOBILE.0012", "MOBILE.0013", "MOBILE.0014" ]
- allowImageCompression: If set to true, the system will compress image as per the image minimum size defined. Default: false.
- minimumImageSizeForCompression: This will only come in play if "allowImageCompression" is set to true. The system will compress images more than the minimum size to within the value. Value is always defined in MB. Valid value: a number. Default: 1.

offline

This offline functionality is only used by service providers. Drivers do not need this functionality as they are allowed to submit offline events. Offline functionality has been extended to the following service provider actions:

Start on Accepted Shipments.
Accept and Decline on Tendered Shipments.
Decline on Open Bids.

Offline functionality is configurable, and you have to set the parameter "true" in order to allow carriers to respond to tender while offline. They default to false.

For example:

"offline": {
"startShipment" : false,
"acceptTender": false,
"declineTender" : false,
"declineBidTender": false
}

Mobile Layout

Creating a Mobile Layout

Configuring JSON

DEFAULT_MOBILE_LAYOUT

General

landingPage

shipmentList and shipmentDetails

orderReleases

addEvent

dockScheduling

branding

externalUrls

quickcodes

overrideSections

SERPROV_MOBILE_LAYOUT

offline

Related Topics