toggle quoted messageShow quoted text
Sorry is there a picture of this process? Where is the timestamp stored? Is it on the database? Is there a method of exporting all the metadata to be stored in git without a view wrapped around it?
What happens on the import – if I have an lr there already – does it overlay that LR or does it just store it as a different timestamp? We need to process out how this will work both when we have the wb and when it is gone with the addition of code source lockdown management if there will be no user security.
If I remember correctly, if we wanted to change a view, we used to create a new env, import everything in the component, change the view, do testing but only migrate the vdp that had changed – then get rid of the environment.
We only migrated the one vdp so that we didn’t have to retest all the vdps. How would that work if we were trying to import the entire set of vdps. I would think they would eventually have different timestamps depending on when they were exported/migrated.
I think we need a working group on this.
When is a good time to have a meeting?
From: genevaers-discussion@... <genevaers-discussion@...> On Behalf Of Ian C
Sent: Sunday, February 21, 2021 8:18 PM
To: a orth <pwht@...>
Cc: speresie1@...; Ian C <ian@...>; genevaers-discussion@...
Subject: Re: [GeneraERS] Workbench
Just to clarify. Currently the workbench XML contains all of the components needed for a given view.
That is all the LRs, Lookup Paths etc.
You can also group many views into a workbench XML.
There is an concern regarding making sure we have consistent LRs etc.
The proposed method for doing this at the moment is the use of the CREATEDTIMESTAMP value.
When a set of WB XMLS are generated from the workbench (say for a set of views) they will all have the same timestamp.
To indicate that they are the compatible set. And when importing back into the workbench so they can be edited then the timestamps will be checked.
On Sat, Feb 20, 2021 at 1:58 AM a orth <pwht@...> wrote: