Having not used this particular version of Gentran, I'm not certain that this 
will work, but if you can export the map to a file that can be re-imported 
later, you could use my favorite VCS: FreeVCS (http://www.freevcs.de/).  You 
can comment your changes as well as restore older versions and store your 
documentation there as well.
   
   
  Harold DeWayne

----- Original Message ----- 
From: [EMAIL PROTECTED] 
Date: Friday, February 9, 2007 9:21 am 
Subject: [EDI-L] Change Request documentation/control for Gentran NT 
To: [email protected] 

> Hello group, 
> 
> I am trying to get a handle on tracking production change 
> requests. Our 
> company has a one person EDI department, I am sure many others out 
> there 
> can relate. Being a one person shop, I have had the liberty of 
> changing 
> things any way I want and tracking (or not tracking) the changes 
> any way I 
> want. We were a privately held company up until February 1st and 
> as such, 
> no audits were required. Now that we are public, I am expecting 
> that we 
> will have an audit and my current way of tracking will never fly. 
> We have 
> Gentran on an NT server. We do not have a test system. For 10 
> years now, 
> we haven't had too many problems with "production control", but, I 
> would 
> like to organize this a little more and document changes within 
> some type 
> of structure. Gentran on the NT server does not enforce any 
> production 
> change control or version control. You have to create your own. 
> My goals 
> are to create a change request system for documentation purposes 
> and to 
> find a way to limit the risk of production maps and other scripts 
> from 
> being overwritten by development efforts. I am splitting my 
> personality 
> and pretending that I now have a multi-person EDI support team. 
> One 
> person is the Manager and the other person is the developer. My 
> other 
> reason for doing this is in the hope that I may actually get 
> another 
> person to back up the EDI efforts, and need to have procedures in 
> place 
> for that person to follow. 
> 
> The first thing I want to tackle is Map control. One thing I have 
> done 
> over the years is to put a version number in my map name. When I 
> do 
> update a map, I rename it to a higher version. I have my Maps 
> directory 
> subdivided into four categories, Dev, Prior Versions, Production, 
> and 
> Test. I am thinking that I could put a "read-only" protection on 
> the 
> Production folder and "read-only" on the TransObj for all users 
> other than 
> my server main, overall user. Then, the only way you could move a 
> map 
> into the Production folder or register it in production would be 
> if you 
> have access and can sign on to the server. Would that work? 
> Each 
> developer will have their own TEST trading partner. Any testing 
> is to be 
> done only with this partner. They would change the Map Summary 
> Description to be Test_whatever for the TEST tp to find it when it 
> is 
> compiled and registered, and so the real trading partner doesn't 
> find it. 
> Developers, when finished testing, would put their map in the Test 
> folder 
> and submit a request to the manager to do a quality check and 
> place the 
> map into production. Developers would keep their development 
> version on 
> the server as opposed to the client in order for the whole EDI 
> team to be 
> able to see which maps are being worked on. Can't see this if the 
> maps 
> are on the client. 
> 
> Ok, all that being said, any one out there already do this? Do 
> you have 
> some suggestions for me? 
> 
> Any feedback would be greatly appreciated, thanks, 
> Cindy 
> 
> [Non-text portions of this message have been removed] 
> 
> 

 
---------------------------------
Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get 
things done faster.

[Non-text portions of this message have been removed]



...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

Reply via email to