Make the "Go To Latest" text stand out

[GaryWalling]

If you are reviewing out of date data, the Windchill object details page shows the text 'Go To Latest". Please make the "Go To Latest" text stand out more - perhaps make the text/cell red and blink.

The bottom line - make it more obvious to the user that they are looking at old data.

[MikeLockwood]

Completely agree - make it red and 64 font!

[gmehta]

YES make it RED and highlight it....

[RivanHassanali]

Absolutely, it is a fundamental need for users to immediately be aware that they may be looking at wrong data.

It is not good enough to have this tucked up in the corner of the screen in peripheral vision.

We customised the page, to move the "Go to Latest" link to be after the part name & version. It helps alot, though we have to always re-apply the change with patches / updates.

(We haven't yet made it flashing or highligted text, though (no joke) that was in my request internally).

Pic after our customisation:

[gmehta]

How did you customize it, was it just a change in the JSP?

Did you get the change info from PTC. If its not confidential can you share the details?

I wish if we could make it just a larger font (20?  or so) and red in colour

thanks

[RivanHassanali]

Here is the info from my dev team:

Find the following files: main.js , windchill-all.js , windchill-all-debug.js

1. Open main.js

2. Perform a text find "gotolatest"

3. You will notice there is a sequence of 'if' statements that basically put together the headeritems. It begins with the gotolatest, followed by Actions menu, followed by icons, followed by lifecycle state.

4. Simply comment out the existing 'gotolatest' block and copy-paste it a little further down in the sequence.

(repeat for the other files)

That's it. The headeritems will be built in the new sequence. I dont think you have control over the font appearance at this stage, but at least you can move it around to a location you prefer.

As always, take care to do backups and testing... and this change will be lost anytime you apply a patch. You will need to re-edit as needed.

[ShirishMorkhade]

The easiest way to control this is via the CSS stylesheet. In "<WT_HOME>/codebase/netmarkets/css/windchill-base.css" you can add an entry similar to the following:

.infoPage .goToLatest a{

    margin-right: 6px;

    margin-top: 1px;

    color: red;

    font-size: 16px;

    font-variant: small-caps;

    font-weight: bold;

    text-decoration: blink;

}

Of course the CSS properties and values you choose can be different. The blinking text is probably a bit overboard. I google for blinking text CSS properties and found it might have been deprecated, but not sure.

[gmehta]

A+ works great.

I guess for it to work I had to add the "a" on the first line. OOTB does not have the "a"

Very simple yet functional solution. No method server restart etc is needed.

***Backup your windchill-base.css file before making changes.

[LawrenceS]

I think nothing short of a hand coming out of the screen and smacking the user would be satisfactory...although I am not sure what this code would look like.

That being said, the next best thing would probably look something like the larger red text as Shirishkumar shows in the above screenshot.  Very nice.

[ShirishMorkhade]

Please disregard my previous comment to this blog. It is recommended not to modify windchill-base.css directly. Instead you can follow below modified instructions:

1. Create your own css file: I have created mycustomcss.css in “<WT_HOME>/codebase/netmarkets/css” directory with the following content:

.infoPage .goToLatest a{

margin-right: 6px;

margin-top: 1px;

color: red;

font-size: 16px;

font-variant: small-caps;

font-weight: bold;

text-decoration: blink;

}

2. Register this custom css: Add this custom css scripts to all the pages. To do this by modify netmarkets.presentation.cssFiles property in site.xconf to have the necessary css files included.

<Property name="netmarkets.presentation.cssFiles"

overridable="true"

targetFile="codebase/presentation.properties"

value="netmarkets/css/mycustomcss.css"/>

• Make sure path specified is relative to codebase
• Use forward slashes for the path separators
• You can include multiple css files as a comma or semicolon separated list in the value.
• Note that order is important, and that the files will be loaded after the Windchill style sheets so they will properly override the default styles.

3. Propagate changes: Propagate above changes using below command:

          “xconfmanager –p”

4. Execute below command to combine all css files.

          “ant -f bin\jsfrag_combine.xml”

Note- Please refer Windchill Help Centre for details about Adding Custom CSS Files

5. Stop Windchill Method Server

6. Clear Tomcat and Info*Engine cache

7. Restart Windchill Method Server

         

Please check video: http://youtu.be/cWOLqtpPOdU

[thauglie]

‌this is a key compliance need for Boston Scientific.   We are providing a list of key Ned's to PTC and this is one of them.   It seems universally needed and could be simple. 

[MikeLockwood]

The referenced CS on this has all the needed info.  It's correct and relatively complete - and repeated above in various ways.  I found the CS hard to use though, and re-documented all steps in a simple 2 page document w/screen captures. Happy to provide to anyone.

[aacciano]

Hi Mike,

can you please share it?

Thanks!!!

[MikeLockwood]

https://community.ptc.com/t5/Windchill/Go-To-Latest-make-more-visible/td-p/450834

I've got dozens and dozens of these little documents - have to find some way to make a few $ from them at some point but happy to share.

Hard in general to use the info as provided by PTC it seems (or maybe I'm just not good at reading what they provide).

[MikeLockwood]

very nice - great idea

[MatthewKnight]

I'd like to see it managed by a couple of different preferences so that we could pick from a predefined set of possibilities - or maybe even set custom CSS as a preference value.  All that said, Shirishkumar's post from Sep 16, 2014 1:37 PM looks like the right idea to me.

[JeffZemsky]

There is a project underway for 11.0 M010 to address this - screenshot previews to come.

[SteveShaw]

This has been addressed as of 11.0 M010.

[hvaradharajan-2]

Hi,

Nice to have this feature in OOTB..

We are moving to WC 11, and it shall be M010.

Is this already available in the Release that came recently on June 24th?

Is it pure OOTB or any preference /Property?

Thanks

Hari

[JeffZemsky]

M010 is the June release and yes the behavior is OOTB.