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

Deploying DCR and Image files associated with DCRs using OpenDeploy

Aditya218

Hi
I am uploading some image files in my DCR using a browse button in the DCR. I am deploying this DCR through a wokflow using OpenDeploy. Can anyone tell me if I can deploy the image files associated with the DCRs also at the same time while deploying the DCR through OD? If so, how could it be done?

Thanks

Find more posts tagged with

Comments

ISCBorisB

Hi
I am uploading some image files in my DCR using a browse button in the DCR. I am deploying this DCR through a wokflow using OpenDeploy. Can anyone tell me if I can deploy the image files associated with the DCRs also at the same time while deploying the DCR through OD? If so, how could it be done?

Thanks

You'd have to code for it, normally through Workflow Deployment Task. I have a similar case where an external Task
parses out attached DCRs and builds Assets List that is then used in the "File List" Deployment.

Alternatively you may simply make "Date/Time" Comparison Deploy from your Image Folders. I did not use this mechanism
because in my case images should go through formal approval before Deployment, etc...

Dhinesh

Thanks for the reply. I am using FileList deployment. In my case, the paths of the DCRs that is routed in the workflow and that need to be deployed is written in a filelist(not manual). Do you mean to say that the path of the image files that are uploaded in the DCR should also be written in the same filelist so that the files can be deployed along with the DCRs? If so, I have a concern here.

The path of the DCRs that need to be deployed is written automatically in the filelist because the DCR is routed in the workflow and its path can be fetched from the workflow's task itself. But how would that be possible in the case of an uploaded image? How would we be able to write the path of that image automatically into the filelist? Please correct me if I my analysis is incorrect here.

Thanks

Adam Stoller

Thanks for the reply. I am using FileList deployment. In my case, the paths of the DCRs that is routed in the workflow and that need to be deployed is written in a filelist(not manual). Do you mean to say that the path of the image files that are uploaded in the DCR should also be written in the same filelist so that the files can be deployed along with the DCRs? If so, I have a concern here.

The path of the DCRs that need to be deployed is written automatically in the filelist because the DCR is routed in the workflow and its path can be fetched from the workflow's task itself. But how would that be possible in the case of an uploaded image? How would we be able to write the path of that image automatically into the filelist? Please correct me if I my analysis is incorrect here.

Thanks

You parse the contents of the DCR for image references (preferably in their own dedicated field(s) and then you add those files either to the task (so that they go through the entire review process and then eventually get pulled into a deployment file list) or as part of the deployment script (to put them into the file list)

ISCBorisB

Thanks for the reply. I am using FileList deployment. In my case, the paths of the DCRs that is routed in the workflow and that need to be deployed is written in a filelist(not manual). Do you mean to say that the path of the image files that are uploaded in the DCR should also be written in the same filelist so that the files can be deployed along with the DCRs? If so, I have a concern here.

The path of the DCRs that need to be deployed is written automatically in the filelist because the DCR is routed in the workflow and its path can be fetched from the workflow's task itself. But how would that be possible in the case of an uploaded image? How would we be able to write the path of that image automatically into the filelist? Please correct me if I my analysis is incorrect here.

Thanks

I'm not sure I understand you questions. If you have some issues, could you be more specific?

You are correct, WF attached Files Path is relative to 'iw_workarea'. There is nothing you can do about that.
Filelist entries should specify File Path relative to the Deployment Definition source area. iw_workarea
and OD Source Area may be the same, may be totally different, OD source may reflect some approval *phase* location
(like "Latest Edition" of iw_workarea Branch), etc...

Both OD Source and the List population are under your control, it is your (the Developer) responsibility to set
them correctly whatever "correctly" means in your Business logic. Depending on what you need you may generate single
list or multiple lists, use any of them with different filters for different Deployment Legs and so on.

For example, in my case I generate a single List for the Workflow mix of JSPs and Binary Assets (Images, PDFs and the like)
and then use it in the single transactional Bracket with two fan-outs, one for the Application Servers Cluster (Filtering JSPs)
and another for the Web Servers Cluster (Filtering everything but JSPs)

Dhinesh

Thanks for your replies. I am confused about one thing here. When I parse my DCR xml, different tags are encountered which contain the path of the image that is uploaded. For example, one tag could be \templatedata\datatype\image\image1.jpg<\image1> and another tag could be \templatedata\datatype\image\image2.jpg<\image2>. How will the parser be able to recognize the tag which will contain these paths? Is there any option or any way where while saving the DCR, we can add a common attribute (say IsImage="true") to the tags which contain the path of the uploaded image in the DCR so that while parsing, this IsImage tag could be used as reference to get the image paths. How do i track the tags in the xml which have the uploaded image paths because all these tags will have different names?

Thanks

Adam Stoller

Thanks for your replies. I am confused about one thing here. When I parse my DCR xml, different tags are encountered which contain the path of the image that is uploaded. For example, one tag could be \templatedata\datatype\image\image1.jpg<\image1> and another tag could be \templatedata\datatype\image\image2.jpg<\image2>. How will the parser be able to recognize the tag which will contain these paths? Is there any option or any way where while saving the DCR, we can add a common attribute (say IsImage="true") to the tags which contain the path of the uploaded image in the DCR so that while parsing, this IsImage tag could be used as reference to get the image paths. How do i track the tags in the xml which have the uploaded image paths because all these tags will have different names?

Thanks

First, I'd consider it questionable to put images under the templatedata directory.
Second - you appear to be using an "xml" style DCT (good) which therefore gives you named elements - and your element names begin with the word "image" - so your parser should be able to recognize elements so-named and then extract their contents and then you have an area-relative path to the image which you can either attach to a task in a workflow or stuff directly into a filelist for deployment (assuming the root of your area is also the source area path for the deployment)
Third - when defining the DCT consider that if you have an image field appear within multiple different containers throughout - that they can all be named "image" - they don't have to be "image1", "image2", etc. - because their address or xpath will be unique:

So - I think you're on the right track, you just haven't followed it all the way through yet.