Showing results for 
Search instead for 
Do you mean 

Sage SalesLogix Update Requests (formally known as Hot Fix requests) - Guest Blog by Matthew Walters

by Employee on ‎06-11-2012 12:00 PM - last edited on ‎06-13-2012 09:25 AM by Administrator Administrator

Updates and Hot Fixes are something that support commonly gets questions on and I will attempt here to provide some facts and also lay out the life of an Update (Hot Fix) request through Sage’s different teams.

 

Updates are released to address high severity/priority defects in between larger Service Pack releases.  You’ll notice that the term Update (7.5.4) has replaced the term Hot Fix (7.5.3).  Any update that is web specific will be referred to in the format of: Web Update XX.  When preparing to apply a Web Update, make sure to read the prerequisites section in the applying guide as most require that all previous Web Updates be applied.  For example, if you need a fix that is included in Web Update 03, you’ll need

Web Updates 01 and 02 applied prior. 

 

Updates that are not specific to WEB are referred to as Updates or LAN Updates. These Updates include files for the programs that are installed for SalesLogix for example the SalesLogix client, server, speedsearch, administrator, and architect.  Since LAN Updates often include fixes to core server components such as the SalesLogix OLE DB Provider, it is important to frequently review these as they become available even if your CRM implementation is 100% Web. All implementations, including Web only, make use of the SalesLogix LAN Server components.  For the most part Updates are stand alone and can be applied independently from each other.  There exceptions, which are noted in the applying guide that accompanies the update.  For example, 7.5.4 Update 08 states in the prerequisites that Update 05 is required.  The following is a step by step breakdown of the Update request process and the various steps it takes…

 

  1. Customer/Business partner reports an issue to Support and it is confirmed as a defect
  2. Customer/Business partner provides impact statement that details how the defect is affecting their system and business
  3. Update request is created by Analyst and approved by Manager
  4. Update is sent to Research and Development (R&D) to review
  5. R&D  approves or rejects Update request
  6. (Update - approved) Development team will scope the issue
  7. Dev works on a fix for the issue
  8. Dev sends the fix to QA for assurance testing
  9. If rejected by QA it’s sent back to Development for further research
  10. Validation of Update is sent to the customer
  11. Customer Validates Update
  12. If customer rejects the Update it will go back to QA
  13. Final build is created and posted online

Register Read Guidelines Request Partner or Employee Access

What's New in 8.1

Labels