|
Assuming:
Two weeks ago the devs sent QC a build. In the interim the devs have been
making data changes for the next release. The QC department now comes back
and requires 100's of data rows be changed in their build.
Question:
Do the devs hand key all the changes into the QC data and then repeat the
process in the dev data (somehow manually checking for conflicts)?
-----Original Message-----
From: David Gibbs [mailto:david@xxxxxxxxxxxx]
Sent: Friday, March 03, 2017 11:17 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Percolating QC changes
On 3/3/2017 11:10 AM, Justin Taylor wrote:
To clarify, by "table data" I mean PF's containing static data. A
typical QC report could necessitate 100's of DB row changes.
I've you're asking about how an ALM system would deploy static data ...
Implementer has a special object code called PFDTA that can do that.
I suspect that other ALM systems have a similar mechanism.
david
(who works for PTC, on Implementer, in addition to running midrange.com)
--
David Gibbs
midrange.com
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding a metric century (100 km / 65 miles) in the American Diabetes
Association's Tour de Cure to raise money for diabetes research, education,
advocacy, and awareness. You can make a tax deductible donation to my ride
by visiting http://lsteml.diabetessucks.net. My goal is $6000 but any
amount is appreciated.
See where I get my donations from ... visit http://lsteml.diabetessucks.
net/map for an interactive map (it's a geeky thing).
I may have diabetes, but diabetes doesn't have me!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.