WTDocumentDependencyLink and WTDocumentUsageLink are used to build document structure, but the LoadFromFile and Import/Export utilities do not support them.
Thank you for publishing your idea. We need more information as specified in the form you saw in the submission process. (Questions below). The more details and context you give to build a better case, the better.
I invite you to check out this topic where 2 PTC executives explain product managers' approach to customer ideas and input for product roadmaps.
Please let us know within the next two weeks.
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
2. What product & version are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
4. What is the use case for your organization?
5. What business value would your suggestion represent for your organization?
I understand supplying the data requested if I was opening a support case with ptc, but the reason I am posting here is that ptc directed me to do so. My understanding of the purpose of this site is to post ideas that we think ptc should consider, so detailing my environment/industry/organization/stakeholders/product version/use case/business value seems like overkill. I will keep it simple here. If that means my postings get canned after two weeks (I assume that was the purpose of the warning), so be it.
The problem is that WTDocument structures are not supported by the utilities. My idea is that they should support them.
@temmett-bec I'm going to disagree. Yes, we collect product ideas from customers on the Community. Since the beginning of December 2021, we have started to apply higher standards of information gathering for product ideas. They may resemble what a support case requires. When product managers consider what items to add to the roadmap, they consider a wide array of information beyond the precise problem to solve. We are essentially asking customers to make the best case possible for their idea. I acknowledge your reluctance to provide more substantive information, but my request for information and timeline still stands.
Actually the method exists.
params> parent, child
<!ELEMENT WTDocumentDependencyLink (dtd?, ObjectID, (describedBy, describes), linkDescription*)>
<!ELEMENT WTDocumentUsageLink (dtd?, ObjectID, (usedBy, uses), structOrder)>
you just need to build correct xml input.
OOTB Convert function with csvmapfile do not contains WTDocumentDependencyLink but the WTDocumentDependencyLink is there.
hope this can help.
While it may be possible to create the WTDocumentDependencyLink, it will only be created for the latest revision of each document. Other supported loaders do not suffer this limitation. It is also unsupported in the Import/Export utility.
We are archiving your idea in the absence of further information from you. You still have the option to post a new idea with all the details required.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.