Follow us on Facebook Follow us on Twitter Get the latest job postings quicker!
Follow us on Facebook and Twitter!
Sponsors

Like this Page? Share it!
HomeHomeManhattan Assoc...Manhattan Assoc...GeneralGeneralTracking / Documentation of ConfigurationTracking / Documentation of Configuration
Previous
 
Next
New Post
3/22/2017 12:20 AM
 

Hi,

I need to create documentation for configuration in order to track any configuration change made. We need to documented also last configuration in document.

Please advice how to documented the configuration and how to record every configuration change effectively ?

 

Thank you for any feedback

Zul

 

 
New Post
4/27/2017 9:02 AM
 

We used to do that here, but it became far too onerous to keep all the documentation up to date. Now, we only really document large config changes. We make note of things like:

  • Functional area of the change (i.e. does it relate to receiving, picking, putaway, etc).
  • Who requested the change?
  • Who approved the change?
  • What's the purpose of the change? I.e. what problem did we have that the change solves?
  • Screenshots of any relevant UI screens or database snapshots from before and after the change.
  • Any "weird" things about the change, which may relate to bugs in the system or things that are very specific to our own configuration. E.g. we bastardize the system a lot to get it to do things that it wasn't necessarily designed to do out-of-the-box, so if we've re-purposed a particular database field or something, we'd make note of that.

Depending on the scope of the change, we may also document what changes occurred within the database, i.e. "if we make this small change in this UI screen, what database tables get touched?"

 

 
New Post
4/28/2017 1:07 AM
 

Thank you John... yes

 
Previous
 
Next
HomeHomeManhattan Assoc...Manhattan Assoc...GeneralGeneralTracking / Documentation of ConfigurationTracking / Documentation of Configuration


Copyright 2010-2011 by WMS Support Forum   |  Privacy Statement  |  Terms Of Use