Skip to main content
12-Amethyst
January 15, 2025
Question

dita keyscope workaround? Alternative?

  • January 15, 2025
  • 1 reply
  • 673 views

Hi All,

I am working on creating templates for the company.

 

Basically, at some point, I would need to aggregate the documents from other teams into a super document.

Map product 3

 - key def (company name)

 - map reference - product 1

  -- key: product_name = product1

  -- text for product 1, " This is product 1 "

 - map reference - product 2

  -- key: product_name = product2

  -- text for product 2 " this is product 2 "

 

output desired

blah blah blah "product 3"

 - this is product 1

 - this is product 2

 

not desired output

blah blah blah "product 3"

 - this is product 3

 - this is product 3

 

I think I might be explaining it poorly, but I'm not too familiar with this. Does arbortext do something like this already?

 

But when it comes to aggregating several of these smaller documents together each using "product_name" but with different products, does it take ...? I have read oasis documentation on keyscope, but as far as I can tell, that's not supported in arbortex (https://www.ptc.com/en/support/article/CS322076)

 

What is the work around/behavior in this case. I can't wrap my head around the current arbortext documentation and cant find examples/videos online regarding this.

1 reply

15-Moonstone
January 16, 2025

Good Morning,

If you are wanting to utilise the use of key scope using the keyscope attribute, this is not currently supported by Arbortext Editor.

Should you wish this to be considered for future implementation please raise it as a Product Idea:
How to submit a product idea for an enhancement request of a PTC product
https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS67713

I hope this is of help 

Best wishes

Alexia