The History tab of the Change object will store a “Redline line item”  in the Action column for each redline change.  The history tab will also show you the User, Affected Item, what was changed, etc.

The biggest limitation that I have found (which isn’t mentioned in the limitations from the manual)  is that Page 2 user defined flex fields cannot be used as “read through’ fields on other object tables (BOM, Affected Items, etc.) 
I find the read-through capability to be very useful so I try to avoid using the user defined flex fields whenever possible.  
You are correct about the axml mapping, but this is relatively painless to sort out using the Class Configuration reports.  

You are most likely getting this error due to your Java Security settings in the Java Control Panel
I would recommend adding your Agile URLs to the Exception Site List and/or lowering your security level to medium (if applicable).
Start > Configure Java > Security Tab > Edit Site List > “Add”
“http://agile933.*********.com”
“http://agile933.*********.com/Agile/PLMServlet”

The short answer is that you cannot modify a 100% complete project.

The exception/workaround is through adding a new activity or gate to the project, which requires setting the “Enable Addition of Activities and Gates to Completed Activites” SmartRule to Allow.
Note – this will change the completed project status to “Not Started” which may be undesirable.

It looks like your “DuplicateRefDes” SmartRule is set to ‘Warning’ (which is OOB default) .  This means that if duplicate reference designators are used – you will always get this Change Status Error (even if they are only warnings) window pop-up when attempting to change status.  

As you can see in your attachment – the ‘Continue’ button is not grayed-out which mean that you can choose to manually ignore the warnings and continue to change the status.  If you don’t ever want to see these warnings – and are okay with duplicate reference designators being used – you will need to change the SmartRule property to “Allow”. 
(Java Client -> Admin -> System Settings -> SmartRules -> DuplicateRefDes).

Arif –
35 to 40 seconds sounds about right for the first time the Gantt chart is accessed, but subsequent attempts should be faster as the application is saved in the Java Cache.  
I would suggest checking your Java settings to see if the Gantt application is being cached or if there are any setting/storage issues preventing this.

Java Control Panel -> General Tab -> Temporary Internet Files -> View (look for Gantt application)

Sorry about that – hopefully this bug has been fixed and will post my full answer.
The short answer is that you cannot set limits to as to who has access to the searches in the OOB Global Search folder.  As Patrick pointed out – you can put restrictions on the search results using appropriate Discovery privileges, but you can’t limit the Global Searches themselves.

My  thought as a potential work-around was to try and create a second Global-ish search folder to house any Saved Searches that you wouldn’t want suppliers to see.
I have found that additional values can be added to the system “Searches List” and those new values can then be assigned to a User’s ‘Searches’ property.  This, unfortunately doesn’t seem to have any impact, as of yet, in making any new search folders available.  It is possible that something may also need to be added on the server level as well in order for this to work, or perhaps it is a design flaw and these edits shouldn’t actually be allowed.  I haven’t had time to take it to that level yet, but probably will at some point to satisfy my own curiosity.

In the meantime – I would suggest renaming any sensitive global searches and/or using the Discovery privilege to limit the objects returned for Supplier accounts.

Adriex –
This is an interesting question, and I can definately think of some reasons that you may not even want suppliers to see the names of some Global searches. 
After doing some digging – I have found that you can make additions to the “Sear

Unfortunately, No.  The fields on the workflow tab are not available to be displayed in the output of a search.

You also need to be set as the routing manager (Change Analyst, Component Engineer, etc) on the change object. 
Another thing to note is that if you are on any version prior to 9.3.2  this notification is not sent to the routing manager if the workfl