PLC WF and Image deploy issue while using DCR

I have a very basic component , which gets the data from the DCR
DCR has two fields
- image
- link
I have followed the OOTB FormsPublisher Content.component to develop the component

Issue :-
The page on SP preview looks good , for images and links (internal .pages and external works )
but the OOTB PLC WF is not deploying the images to the LS Runtime Server , the images , which is called in the DCR.
I am getting the right path everything in the .pages . It is not showing the images in
the file associations at page level

Note:-
OOTB PLC attaches and deploy the DCR’s ,
OOTB PLC work flow deploy the images , if we call the images in the Datum

Am I missing any configuration or any steps

Thanks
Vin

Find more posts tagged with

Comments

Faizi

PLC workflow will not attach files browsed in DCR if the dependency metadata is not added with correct vpath of the attached files.

EA is TeamSite/LiveSite/DependentURI -- semi-colon delimited area-relative paths to files.

You can check this thread where vpatel mentioned solution in detail.
http://devnet.interwoven.com/forums_vb/showthread.php?t=30051&forumid=66&highlight=attach+dependency

I have a very basic component , which gets the data from the DCR
DCR has two fields
- image
- link
I have followed the OOTB FormsPublisher Content.component to develop the component

Issue :-
The page on SP preview looks good , for images and links (internal .pages and external works )
but the OOTB PLC WF is not deploying the images to the LS Runtime Server , the images , which is called in the DCR.
I am getting the right path everything in the .pages . It is not showing the images in
the file associations at page level

Note:-
OOTB PLC attaches and deploy the DCR’s ,
OOTB PLC work flow deploy the images , if we call the images in the Datum

Am I missing any configuration or any steps

Thanks
Vin

Adam Stoller

PLC workflow will not attach files browsed in DCR if the dependency metadata is not added with correct vpath of the attached files.

EA is TeamSite/LiveSite/DependentURI -- semi-colon delimited area-relative paths to files.

That's the "old" EA - used by 7.2.0 and below.
Since 7.2.1, that EA is no longer used and the dependencies are handled internally within the store / CSSDK. There's a utility (IWHOME/install/livesite/install_scripts/iw_migrate_dependencies.ipl) for migrating dependencies from older systems (that used the EA). I'm not sure if it can be used to seed, or fix, an existing newer system (7.2.1 or older) if the dependencies somehow got out of whack.

Rick Poulin

That's the "old" EA - used by 7.2.0 and below.

While that EA still works, setting it manually isn't really the cleanest way of solving your issue. You'd probably have to write an external task for this anyway, so you may as well write one that queries the association manager directly and attaches those files.

The reason the PLC isn't pulling them automatically is that it only looks for associations of type "Sitepub.Deployable", whereas DCRs create associations of type "image". Thus, all you need to do is write an additional task that picks out the DCRs attached to your task, resolve its dependencies of type "image", and attach those additional files to the task. Or, if you know your way around Spring+Java, you can create your own DependencyProcessor and add it to the "sourceSet" property of the "teamsite.DependencyService.DependencyProcessors" bean.

Not sure why it doesn't do this ootb, but meh.