Issue in Set Associations for Content Deployment Workflow

Hello,
I have 2 tpls for one template lets say a parent and a child tpl.The parent internally gives a call to the child tpl and the child tpl creates .json files at a different location which later gets referred during the page generation.

I want to attach this .json file in during the SetAssociations automatically when I attach the generated xml DCR.My SetAssociations functions using CSSDK and fetched the child/parent associations perfectly.

I added extended Attributes for the .json file using the TeamSite/Templating/DCR/Type and am hoping to have this .json attach automatically since it would be the child association for the SetAssociation task.But this does not seem to work in my case.Anything that I am missing out here?

Thanks.

Find more posts tagged with

Comments

Adam Stoller

I'm not sure about the answer, but thee are some questions regarding context that might make it easier for someone to assist you.

The more detail you supply, the better chance you have of getting a solution.

SonaliKulkarni

TeamSite 7.3.1.
Logic to create JSON is inside the tpl hence .json would be created on page Generation.Nothing to do with the workflow.

THis is a non PLC workflow.Its a Content deployment workflow.

XML DCR shows the related files except for the .json file on clicking Actions->Find Associated files.

.json files no associations on the same on clicking Actions->Find Associated files.

Other output files show the required associations properly on Actions->Find Associated files and get associated during the workflow.

•If you do the generation of the JSON file outside the context of the workflow and then select the DCR for a PLC or PLC-derivative workflow - does the JSON file get attached?
- No..It does not get attached anyway as an association.It would get attached if tried to attach individually which is not something as per my requirement.

•Is the primary issue that you want the JSON file to be generated and attached within the context of the PLC or PLC-derivitave workflow?
-Issue is .json gets created during the page generation but does not get attached during SetAssociations in the workflow which is something I want to achieve.Other dependencies get attached during this task.Only issue is with .json.I tried to assign extended attributes to this .json file as TeamSite/Templating/DCR/Type property but is in vain.Still it does not get attached.

Thanks.

Adam Stoller

You said:

I want to attach this .json file in during the SetAssociations automatically when I attach the generated xml DCR.My SetAssociations functions using CSSDK and fetched the child/parent associations perfectly.

I don't have a copy of the javadocs for 7.3.1 - but looking in the 7.2.1 version at the CSAssociatiable interface, it looks like you need to do a createParentAssociation() from the JSON file to the DCR or a createChildAssociation() from the DCR to the JSON file - which, since it requires CSSDK / Java - means you'd have to call out to a Java program from your TPL to do this and the Java program would have to create a valid CSClient object to make that association.

Is this what you've been doing?

If the JSON file's name and path are programmatically determinable from the DCR's name and path - you could handle this in a workflow through a URL External) Task. That way you'd already have the CSClient object. You could traverse through the list of files associated with the job, if any are DCRs (of the correct type) you could check to see if a JSON file exists with the same base name and relative path information, and if so:

That's about all I can think of at this time, hopefully it will help get you to where you want to be.

SonaliKulkarni

Hello,
Thanks a lot for your update.I think its a good workaround for this issue.
Will surely try working on this.

But still my query is shouldn't setting extended attributes work directly after the TeamSite/Templating/PrimaryDCR and TeamSite/Templating/DCR/Type is set.I was kind of hoping to follow this easy approach so as to avoid the modification of all tpls that too with incorporation of complexity for CSSDK.
Is there anything else that I can do on the EAs so as to have this work.

I was wondering what makes the output file give this error on edit
unable_to_parse_dcr after I set any extended attribute for this.
And having sorted this out would my setassociations work directly for the output files.Its basically considering my .json as a DCR file and then is finding the issue to parse it.

Your response on this is much appreciated.

Thanks.