Combining DCR field value with SiteMap Node

Hi,

As per the scenario I am looking forward for an advice from our experts here on DevNet where my requirement is to combine a DCR field value with SiteMap node description tag. As there is a field called ""Summary" in DCR, and on the second hand while creating any node for the respective page, description tag in default.sitemap shall be updated with Summary field value based on DCR associated with a component on the specific page.

For Example: output page name is "ABC.page" that has a component having DCR path "ABC". So in this case I am looking for a mechanism where based on page name, it should look for DCR value and then this DCR shall be parsed and Summary field shall be fetched to update the description tag in default.sitemap file.

It would be great if anyone can provide me pointer for the above situation.

BTW, we are using TS7.2.1 with LS7.2.1.

Regards,
Ace

Find more posts tagged with

Comments

interDev

Hi,

As per the scenario I am looking forward for an advice from our experts here on DevNet where my requirement is to combine a DCR field value with SiteMap node description tag. As there is a field called ""Summary" in DCR, and on the second hand while creating any node for the respective page, description tag in default.sitemap shall be updated with Summary field value based on DCR associated with a component on the specific page.

For Example: output page name is "ABC.page" that has a component having DCR path "ABC". So in this case I am looking for a mechanism where based on page name, it should look for DCR value and then this DCR shall be parsed and Summary field shall be fetched to update the description tag in default.sitemap file.

It would be great if anyone can provide me pointer for the above situation.

BTW, we are using TS7.2.1 with LS7.2.1.

Regards,
Ace

In the workflow, look for page dependencies and find out the DCR name from there. Run an external task to parse and retrieve the field value based on the DCR name. Now in the same task or another task, you will have to open default.sitemap and add the pagename along with DCR field value which you just retrieved.

acezone

In the workflow, look for page dependencies and find out the DCR name from there. Run an external task to parse and retrieve the field value based on the DCR name. Now in the same task or another task, you will have to open default.sitemap and add the pagename along with DCR field value which you just retrieved.

Hi InterDev,

Thanks for the pointer. I do have a question on same line. As you mentioned

Now in the same task or another task, you will have to open default.sitemap and add the pagename along with DCR field value which you just retrieved.

But let say for an instance if the node for the created page is not available then even after opening the default.sitemap file workflow can not update the value for the Summary to the node as it is yet not created for the same page. So I think there should be some other way around to work on this piece of code / workflow.

Regards,
Ace

interDev

Hi InterDev,

Thanks for the pointer. I do have a question on same line. As you mentioned

But let say for an instance if the node for the created page is not available then even after opening the default.sitemap file workflow can not update the value for the Summary to the node as it is yet not created for the same page. So I think there should be some other way around to work on this piece of code / workflow.

Regards,
Ace

If somebody is updating the node manually what is point in sending out the summary field through automated process. Why the person adding the node, cannot add the summary?

If you add node and summary as part of the workflow, the whole process becomes seemless . One thing i am not sure and you will have to check is 'node ID'. How node is associated and generated. If the node ID is not an issue then you can use this solution.

acezone

If somebody is updating the node manually what is point in sending out the summary field through automated process. Why the person adding the node, cannot add the summary?

If you add node and summary as part of the workflow, the whole process becomes seemless . One thing i am not sure and you will have to check is 'node ID'. How node is associated and generated. If the node ID is not an issue then you can use this solution.

Inter_Dev,
Here we already have 240 DCRs in place and mapped to respective pages, and now we can not go back to client asking them to update node description for all 240 pages.

Well, I would like to understand the concept for the above quoted statement. It would be great if you may kindly share your views on the same.

Regards,
Ace

interDev

Inter_Dev,
Here we already have 240 DCRs in place and mapped to respective pages, and now we can not go back to client asking them to update node description for all 240 pages.

Well, I would like to understand the concept for the above quoted statement. It would be great if you may kindly share your views on the same.

Regards,
Ace

For these 240 pages, i assume that nodes are already present in sitemap file and you only have to add description. I

f that is the case, create an additional task in your workflow to parse DCR and sitemap file. Also get the .page file name (can easily get this information from attached file list). Read the description field from DCR and open the sitemap in edit mode through your parsing task . TRaverse the node names and compare them with page name, and add the corresponding description in the sitemap file.

acezone

For these 240 pages, i assume that nodes are already present in sitemap file and you only have to add description. I

f that is the case, create an additional task in your workflow to parse DCR and sitemap file. Also get the .page file name (can easily get this information from attached file list). Read the description field from DCR and open the sitemap in edit mode through your parsing task . TRaverse the node names and compare them with page name, and add the corresponding description in the sitemap file.

Inter_Dev,

Here we are dicussing about the existing page and node, but what if a new page is created and component with respective DCR is associated with page, but node has not been created. In that case I don't think DCR Summary field can then update the node description tag with values.

So ideally I want a process where node shall be created dynamically along with values from DCR shall then be updated accordingly.

Please let me know if this make sense.

Regards,
Ace

interDev

Inter_Dev,

Here we are dicussing about the existing page and node, but what if a new page is created and component with respective DCR is associated with page, but node has not been created. In that case I don't think DCR Summary field can then update the node description tag with values.

So ideally I want a process where node shall be created dynamically along with values from DCR shall then be updated accordingly.

Please let me know if this make sense.

Regards,
Ace

Check the comments i gave earlier.
"If you add node and summary as part of the workflow, the whole process becomes seemless . One thing i am not sure and you will have to check is 'node ID'. How node is associated and generated. If the node ID is not an issue then you can use this solution."

To explain little bit, Open the sitemap file in your workflow task and check if the node name exists in this file. If yes, add the summary value picked up from DCR. If no, add the node tag and corresponding summary field. One additional value which is assigned in sitemap file is 'node id' and i am not sure how exactly teamsite generates this value. Try giving some random unique number values to this field and see if that works fine. Otherwise check, if there is any Java class in LivesiteA API which can help you generate this ID.

HTH