Re: Percolating QC changes -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Percolating QC changes
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 3 Mar 2017 11:17:08 -0600
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Percolating QC changes , Justin Taylor

This mailing list archive is Copyright 1997-2024 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.