nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

item as a subelement of ruleset

shahzamaj

TS6.7.2 SP2, win server 2003
-----------------------------------

1) I have manual of TS6.7.0. According to this manual, Item element and container element can be subelement of root-container element and not ruleset element.

I have a DCT in which item is placed as a sub element of ruleset. And this DCT is working fine. So in TS6.7.2, is Item allowed as subelement of ruleset ?

2) This gets me to other question, about path in FormAPI.
[html]
|

|[/html]
[html]
|

<script>1</script>

<script>2</script>

<script>3</script>

<script>4</script>

|[/html]
If I want to access Item it1 in first case , then I can use
IWItem.getItem("/rt/ct1/it1").
If I want to access Item it1 in second case, can I use IWItem.getItem("/it1")
without any mention of root-container ?

Secondly, does it matter where you place script tag in DCT or does have to be at the ruleset level only as I have put one in second case as <script>4</script>?
If I put script tag at different level, does it affect x-path ? I have provided <script>2</script> container ct2 level , <script>3</script> container ct1. level and <script>4</script> at root-container level. Does it mean that if I am accessing Item it3 in script at ct2 level, then x-path will be IWItem.getItem("/ct2/ct3/it3")
if I am accessing Item it3 in script at ct1 level, then x-path will be IWItem.getItem("/ct1/ct2/ct3/it3")
and if I am accessing Item it3 in script at root-container level, then x-path will be IWItem.getItem("/rt/ct2/ct3/it3")

OR no matter what, wherever I put script in the DCT, x-path for accessing any Item will always be from root level (from the item or container placed next to ruleset )

Thanks

Find more posts tagged with

Comments

Adam Stoller

The first example is that of an "xml" style DCT.
The second example is that of an "iwov" style DCT.
The each utilize different DTD's - as such, the xpath structure is different for each.

shahzamaj

1) How could you find out, whether its "XML" or "IWOV" DCT without looking at the first two lines of the DCT ?

2) I believe, DTDs given in manual are for IWOV type DCT. Are the DTDs provided for XML type DCT at any place ?

3) Can you please answer to my questions for both types ? I guess I am getting issues because of the type of DCT being created.

4) Will DTD be different for "content-type" DCT ? Where can I find DTD for this type ?

Thanks

Adam Stoller

1) How could you find out, whether its "XML" or "IWOV" DCT without looking at the first two lines of the DCT ?

I stand corrected, the second code example posted is completely erroneous as it has an open ruleset element but no open root-container element, even though it has a close root-container element - so the second example is garbage.
However, based on your description of having a DCT without such an root-container element - that's part of the difference between the two DTDs for the two DCT-types. There are other differences too though.

2) I believe, DTDs given in manual are for IWOV type DCT. Are the DTDs provided for XML type DCT at any place ?

I don't know which manual you are looking at. Since at least 6.7.1 the FormsPublisher Developer's Guide has included documentation on datacapture6.0.dtd which is what is used for "xml" style DCTs. Personally though, I prefer to look in IWHOME/local/config/ and read the DTDs directly.

3) Can you please answer to my questions for both types ? I guess I am getting issues because of the type of DCT being created.

Based on the garbage code supposing to have a root-container element - then the answer is no - you want IWItem.getItem("/rt/it1"). If you switched to an "iwov" style DCT (not recommended) - then it would be IWItem.getItem("/it1").

4) Will DTD be different for "content-type" DCT ? Where can I find DTD for this type ?

Already answered above

shahzamaj

1) I am sorry for the second code. Its not real code, I produced it to present my questions and I missed an opening root-container in the second code.

Still a question, if I want to access an element of it3 in DCT, I can use IWItem.getItem("/rt/ct1/ct2/ct3/it3");
where it3 is the name attribute of this Item. So even there is a duplicate name for an item, thats not a problem as long as xpath is different

For iwov type I can use IWItem.getItem("/it3");
where it3 is the pathid attribute of an Item.So in this case every pathid has to be unique in a DCT, irrespective of what container they are located in.
Will that be ok, if I access item in iwov style DCT using xpath ?

2) Can I keep two containers on the same row ?

Thanks

Adam Stoller

1) I am sorry for the second code. Its not real code, I produced it to present my questions and I missed an opening root-container in the second code.

Garbage-in, Garbage-out

Still a question, if I want to access an element of it3 in DCT, I can use IWItem.getItem("/rt/ct1/ct2/ct3/it3");
where it3 is the name attribute of this Item. So even there is a duplicate name for an item, thats not a problem as long as xpath is different

You need to learn how to express your questions more clearly.
You are asking if you have an item named "it1" that appears within both "ct1" and "ct2" - is there a problem? And the answer, as you have already determined is "no" - because the xpath to the item is distinct:

You're talking about display here - the answer is "no" - containers do not provide a rowcontinue attribute, and thus cannot appear within the same row.I strongly suggest you spend a bit more time reading the manuals, the examples that come with TeamSite / FormsPublisher, and/or talk to your managers about arranging for you to get some actual training.

shahzamaj

Originally Posted by shahzamaj
Still a question, if I want to access an element of it3 in DCT, I can use IWItem.getItem("/rt/ct1/ct2/ct3/it3");
where it3 is the name attribute of this Item. So even there is a duplicate name for an item, thats not a problem as long as xpath is different

You need to learn how to express your questions more clearly.
You are asking if you have an item named "it1" that appears within both "ct1" and "ct2" - is there a problem? And the answer, as you have already determined is "no" - because the xpath to the item is distinct:
•/rt/ct1/it1
•/rt/ct2/it1
Quote:
Originally Posted by shahzamaj
For iwov type I can use IWItem.getItem("/it3");
where it3 is the pathid attribute of an Item.So in this case every pathid has to be unique in a DCT, irrespective of what container they are located in.
Will that be ok, if I access item in iwov style DCT using xpath ?

No - Using the same example as just above - the difference is that there is no root-container, beyond that there is still no issue:
•/ct1/it1
•/ct2/it1

So, I dont have to use root-container in case of an IWOV type DCT. Is this choice or mandatory ?
By this statement I mean, I dont have to include root-container at all in DCT developmet of IWOV type ? If I still use root-container for DCT, is it valid or its an error ?
If I use root-container in IWOV type DCT, and I need to use path to the item in script, do I need to include root-container in the path or is it optional , eventhough root-container is present in DCT ?

Adam Stoller

So, I dont have to use root-container in case of an IWOV type DCT. Is this choice or mandatory ?
By this statement I mean, I dont have to include root-container at all in DCT developmet of IWOV type ? If I still use root-container for DCT, is it valid or its an error ?
If I use root-container in IWOV type DCT, and I need to use path to the item in script, do I need to include root-container in the path or is it optional , eventhough root-container is present in DCT ?

Learn how to read DTDs - "iwov" DCTs use datacapture5.0.dtd, "xml" DCTs use datacapture6.0.dtd - if you cannot figure it out the answer to your question that way, you should probably find a different line of work.