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; } } }

How to find associated html from the dcr

tirrudev

Hi

My requirement is to push the dcr and the html file that the dcr generated to the staging area.

If the user selects the generated html file and start and a workflow.I can find the associated dcr by using iwextattr of TeamSite/Templating/PrimaryDCR.

But if the user selects the dcr and not the generated html.How can i get the generated html?associated with DCR.

Thanks in Advance

Find more posts tagged with

Comments

vpatel

I haven't dealt w this in a while but if there is an EA on the DCR itself you could use that. If not, then you could set a custom EA on your DCR at generate time and use that?

jagadesh

Hi

My requirement is to push the dcr and the html file that the dcr generated to the staging area.

If the user selects the generated html file and start and a workflow.I can find the associated dcr by using iwextattr of TeamSite/Templating/PrimaryDCR.

But if the user selects the dcr and not the generated html.How can i get the generated html?associated with DCR.

Thanks in Advance

We have faced this scenario in my past, where we have done setting attribute in dcr for the generated html.

TrialReport_dummydata_modified.rptdesign

nipper

If you have not planned on it, this is difficult.

Setting an EA is a common way, also is not allowing the user to name DCR and output files. If your workflow generates the page, it can figure out what the name *should* be.

If you inherited a system without the EAs set, start writing a script to traverse the folders, find a file, see if it was generated and then set the EA on the DCR that generated said file.

tirrudev

Hi,

Thanks for the quick reponses..

The scenario is:

If the user clicks Finish Button The html is generated at the backend and deployed to LSCS Environment and from there portal would pick up..

As of now I am done doing the above step..as sson as the user clicks finish a workflow starts and a html is generated and deployed to test environment.
tHIS REQUIRES NO APPROVAL STEPS.
But it requires approval before deploying to stage and production.So planning to design another second workflow for deploying to stage and production..

So,Now if the user selects the DCR how can i associate the html for the seond workflow..

Thanks in Advance

nipper

that is what you are paid to figure out. This is an architecture issue that someone really should have thought about before building it.

Maybe you can do something funky with setting an EA in the TPL or in the workflow. In the second workflow you need a step to read the EA and attach the appropriate files.

This is a very convoluted process you have.

tirrudev

Thankyou very much Nipper...

This has not been build yet..This was the idea and trying to implement because we are still in POC..

1.In the first case as soon as the user clicks Finish..The html is automatically generated with the name of the dcr..

2.So,Instaed of setting any extended attributes..If the user selects the dcr and start and a second workflow..

.The first task I can write CGI Task or External Task and as the attched file dcr path would be say:templatedata/page/artticle/data/nameofdcr so I can take the nameof the dcr and append .html and check if the html file exists or if it does not giving the user a message "File does not exist" or not generated".

This was my idea..Please let me know if this a feasible approach...

Thanks in Advance

nipper

it sounds like a reasonable approach, but a user should never have to generate the output file, it should always be done for them in workflow regardless.

Adam Stoller

My preferred approach is to ensure that the generated output file's name and location can be derived directly from the name and location of the DCR itself - that way you can go in either direction when trying to attach the associated file to the workflow.

E.g.: