[anoopkrishna]

A very simple question actually, I am trying to modify the Web Tender Stylesheet under the Servprov domain. The client wants this particular stylesheet to be customized to their business. The customization is simple but since these are core OTM files (tenderresp/ExecTendMain.xsl, tenderresp/ExecTendMore.xsl and a few more under tenderresp folder), it will be re-written if any patch is updated to this folder.

So, is there a way, I can keep it away from any patch updates and still use it to show the Web Tender in Servprov domain ? I was hoping there is something similar like using "Stylesheet Profile" option in OTM to customize Email Notification Tender stylesheet.

Has anyone done this before ? Any inputs will be appreciated.
Thank You

[bfolan]

We are trying to do something similiar if I understand you correct. Basically when a carrier logs into OTM they are able to see a results screen with different/more columns. For example, search all loads which are currently tendered (Spot, Broadcast, Regular tenders) in a user friendly format which includes the source city, source state, destination city, destination state, and start date. Were you able to come to a conclusion and/or solution on this issue? I have tried to test using different screensets and results format. As soon as a result column is chosen such as destination city is listed zero results are returned but if I just list the shipment id it lists the appropriate number. Any help if anyone was able to modify the results screen which carriers are able to view shipment data.

[Stefano]

Hi
there is a way to create a USER REPOSITORY for CUSTOMIZED stylesheet, OTM when find this user properties setted up check before in this path later on in standard location.
This prevent also problem during patch update or similar, but in this case is better however after pacth re-check your custom screen.
Check on OTM Help ON LINE item "Stylesheet Location" in User Preferences topic

regards

[Clay Combs]

anoopkrishna, I agree with Stefano. This is one of the basic uses for User Preferences.

Create a custom directory within the xsl directory on the Web server. Make sure to follow a parallel subdirectory structure to that within xsl. For example, if you want to customize tenderresp/ExecTendMain.xsl, simply create xsl/CUSTOM/tenderresp/ExecTendMain.xsl, where ExecTendMain.xsl is your custom stylesheet (but named the same as the original--this is the basis of the override functionality).

Create a User Preference and add a Stylesheet Location value that specifies where your custom stylesheets are--in this case, CUSTOM.

Apply the User Preference to all users in SERVPROV. At this point, whenever a user in SERVPROV accesses the screen in question, the system will substitute your custom stylesheets for the defaults. all users in that domain should see the custom screen. Since the stylesheets reside in a custom directory, they should not be overwritten by patches.

Sorry for the late post--just joined the FAQ today. Feel free to contact me directly for clarifications.

HTH,
cfc

[Clay Combs]

As to bfolan's followup question, I'm curious as to whether you're asking about screen sets for Tender Response? I'm on a project now in which we would like to modify the PUBLIC screen set for Online Booking/ Tendering, but to the best of my ability I can find no reference to it anywhere in any screen set in any domain.

As far as I can tell, then, the search/results pages for Online Booking/Tendering, which would normally be controlled by screen sets, are actually *completely beyond customization*. In several years of working on similar customizations for screens, I've never come across any other object that is so completely out of reach. Perhaps ironically, the screens themselves (controlled from the stylesheets in the tenderresp directory, as mentioned in anoopkrishna's original post) are totally customizable.

BTW, for my related project, we are pushing Accept/Decline functionality through an entirely different (though still SHIPMENT-based) screen set called SHIPMENT_VISIBILITY. This bypasses the TenderRespServlet, but should suffice for this implementation. By using the alternate screen set, we can customize not only the screens (in XSL), but also the search/results pages (with a screen set).

[bfolan]

Clay,
Great info. I will let you know if I am able to get this working.