nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DCRs : should it be submitted to Staging

System

What are the advantages/ disadvantages of submitting DCRs to Staging?
One advantage could be versioning, but if my HTML is getting versioned what do I need the DCR versioning for?
How do I get rid of DCRs associated with deleted HTMLs?
How to take care of expiring/retiring DCRs from the system?

TIA

Find more posts tagged with

Comments

abhishek_gupta

Don't feel there are any added advantages in submitting DCR's to the staging area.
How do I get rid of DCRs associated with deleted HTMLs?
You can write a custom menu "Delete html file". In that perhaps you can in an ipl file write code to read the DCR name (from the extended attributes) and then delete the file.

How to take care of expiring/retiring DCRs from the system?
Build a custom code in the same way..

Adam Stoller

The DCRs are the *source* for the generated files (in some environments, they are source directly for the application server and no generated files exist) - so not versioning the DCRs is "wrong" - it's like working in a software development company and only versioning the binaries produced from thousands of different source files, without versioning the actual source files themselves.

To remove DCRs and generated files associated with one another when either is deleted - you need to develop custom code. At my customer's site we have the PTs for generating the files add EAs to the DCRs so that from a single DCR we can find all of its generated pages; and each generated page already has an EA that refers back to the DCR. Therefore when either part is the subject of a deletion, we can track back to the DCR, and then forward to all of the generated files, delete all of them, and deploy the deletions.

The biggest headache in all of this is the overhead of calling iwextattr.

Expiring/retiring DCRs is essentially a variant of the deletion semantics above - you would need to have some code traverse through the DCRs to find out if they have reached their expiration date and then fan out to all their generated files ...

Of course, you can get far more detailed and fancy with regard to expiration - including sending out advance notification when any given DCR is within a week of becoming expired, and so on.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com