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; } } }

How to set Dependent URI in TS 7.2

Ankmit

Hi All,

As per Interwoven,
"DependentURI" are no longer used in TS 7.2. The Teamsite associations feature achieves similar functionality as dependent URI.

We found that when we migrating pages from TS 6.7.2 SP1 to TS 7.2,the extended attribute is not set.

Will you guys please put some light on this

Thanks in Advance

Find more posts tagged with

Comments

vpatel

When you migrate from pre-7.2 release to 7.2+, there is a migration script that you have to run. Refer to the release notes/install guide for more info on this script. This will figure out all of the dependencies and set them for you once. After that, going forward the system will keep track of dependencies for you automatically.

Net-net: with 7.2+, the "DependencyURI" EA is no longer used. System has a very robust capability built into it to handle very advanced functions than just a single EA :-)! These dependencies could be accessed (i.e. retrieved or set) via CSSDK API.

HTH!

Adam Stoller

When you migrate from pre-7.2 release to 7.2+, there is a migration script that you have to run. ...

How about when you migrate from 7.2 to 7.2.1? Is this migration automatic as part of the upgrade (assuming an upgrade installation, not a fresh server installation)?

Net-net: with 7.2+, the "DependencyURI" EA is no longer used. System has a very robust capability built into it to handle very advanced functions than just a single EA :-)! These dependencies could be accessed (i.e. retrieved or set) via CSSDK API.

Hmm - I know that some of the customizations at my current customer's site use that EA as part of their own process for finding and deploying "related assets" (they use SP but not LS) - you're saying that this EA is no longer being created / updated as of 7.2.1? I didn't see any mention of this in the 7.2.1 release notes or SP documentation - is it documented anywhere else?
Is there a CLT or something that one now uses for accessing the list of dependentURI's? (assuming it's documented - just provide a CLT name and/or manual name - I'll look from there)

vpatel

How about when you migrate from 7.2 to 7.2.1? Is this migration automatic as part of the upgrade (assuming an upgrade installation, not a fresh server installation)?

If your content/sites were created in 7.2 then going to 7.2.1 should not require any migration scripts. However if your sites/content were created using any version pre-7.2 then you have run this script manually after the installation is complete. It is documented in the install guide for 7.2 -- look at *Migration of Legacy Content for Dependency* section. Actual script name is *iw_migrate_dependencies.ipl*.

Hmm - I know that some of the customizations at my current customer's site use that EA as part of their own process for finding and deploying "related assets" (they use SP but not LS) - you're saying that this EA is no longer being created / updated as of 7.2.1? I didn't see any mention of this in the 7.2.1 release notes or SP documentation - is it documented anywhere else?
Is there a CLT or something that one now uses for accessing the list of dependentURI's? (assuming it's documented - just provide a CLT name and/or manual name - I'll look from there)

With 7.2+ this EA is no longer set. DependentURIs can be get/set via CSSDK API -- CSFile.getRelatedAssets(). Also the PLC WF has been updated to NOT use the EA and instead use this API. I do not believe there is a CLT for this.

I would also encourage to read the "Notes" section of release notes around Globalization. It has some really important information such as if you create a file through iw-mount / Y: (windows file explorer -- any non-TS UI / API) then dependencies are not set automatically, etc.

HTH!

Adam Stoller

Thanks for the info - I've passed it along to my customer. They are in the midst of getting all their servers set for 7.2.0 (DEV and QA done, PROD in progress) and were about to do the 7.2.1 upgrade now as well (one cut-over instead of cut-over and upgrade) ... but this information makes it highly unlikely that they'll be able to do the 7.2.1 part any time soon (and extremely valuable to know about this kind of thing to prevent them from doing so and having a bunch of things break!)

Wouldn't it be nice if such non-backwards-compatible changes were clearly identified within the release notes ....

vpatel

This shouldn't be a deal breaker, right? Why go to 7.2 and not to 7.2.1? You can still go from pre-7.2 version to 7.2.1 and run the same migration script.

If you are going from 6.x or 7.1 version to 7.2.1, that script should still work.

Adam Stoller

This shouldn't be a deal breaker, right? Why go to 7.2 and not to 7.2.1? You can still go from pre-7.2 version to 7.2.1 and run the same migration script.

If you are going from 6.x or 7.1 version to 7.2.1, that script should still work.

(Ankmit - sorry for taking over the thread)

If I understand the purpose of the migration script - it migrates the EAs into the new dependency management system - not the other way around.
So if there is a bunch of customization code that uses the EAs, it all needs to be changed before 7.2.1 could be "fully" released in their environment. While that's normally what DEV is for, the current situation here is not as clean as it should be, so the 7.2.0 => 7.2.1 upgrade will have to wait a while (here).

Frederik

I don't know about this EA (never used it), but I think there's a misunderstanding here.

... you're saying that this EA (edit: DependentURI) is no longer being created / updated as of 7.2.1?

Ghoti, I think he's saying that this EA is no longer used as of 7.2.0

> vpatel: With 7.2+ this EA is no longer set.
> Ankmit: As per Interwoven, "DependentURI" are no longer used in TS 7.2.

With that in mind, it would be strange for your customer to happily go to 7.2.0 but not to 7.2.1

Adam Stoller

I don't know about this EA (never used it), but I think there's a misunderstanding here.

Ghoti, I think he's saying that this EA is no longer used as of 7.2.0

> vpatel: With 7.2+ this EA is no longer set.
> Ankmit: As per Interwoven, "DependentURI" are no longer used in TS 7.2.

With that in mind, it would be strange for your customer to happily go to 7.2.0 but not to 7.2.1

Well, either they did something about it that nobody's told me about - or the EA is still there and being set in 7.2.0.

It might be a question of interpretation: Does "7.2+" mean (inclusive) "7.2.0 and anything newer" or (exclusive) "anything newer than 7.2.0"?

Not to cast doubt on Viral's information - but if there are folks using SP on 7.2.0 and 7.2.1 - it would be nice to know if they are still seeing this EA set on their system when they use DCR-based components....

vpatel

Well, either they did something about it that nobody's told me about - or the EA is still there and being set in 7.2.0.

It might be a question of interpretation: Does "7.2+" mean (inclusive) "7.2.0 and anything newer" or (exclusive) "anything newer than 7.2.0"?

Not to cast doubt on Viral's information - but if there are folks using SP on 7.2.0 and 7.2.1 - it would be nice to know if they are still seeing this EA set on their system when they use DCR-based components....

In 7.2+ (inclusive of 7.2) relevant EA is no longer set for newly created content - if you just carry over a Content Store with content created in previous version than you'll probably see it. However, PLC WF is no longer using that EA -- instead it is using the API that I posted earlier.

HTH!

Adam Stoller

In 7.2+ (inclusive of 7.2) relevant EA is no longer set for newly created content - if you just carry over a Content Store with content created in previous version than you'll probably see it. However, PLC WF is no longer using that EA -- instead it is using the API that I posted earlier.

HTH!

Yeah - I figured this out earlier today - apparently the SP files I had been using for doing my testing of their customizations were, in fact, part of a 6.7.2 backing store migration - which is why I still saw the EA there.

So according to the javadocs - CSFile's getRelatedAssets() [actually part of the CSAssociatable interface] takes the following parameters

{parentAssociationsConstraint, localeRenditionsConstraint}); CSTraverse traverse = new CSTraverse(tConstraint);

vpatel

Basically query parameter defines what type of information you want to retrieve:



   /***** If you look at the CSQuery class, at minimum it takes 3 parameters:
    Number 1: selector -- which attributes should be fetched for the related assets.
   ******/
   CSSelectorAttribute attr1 = new CSSelectorAttribute("vpath", null, null, -1);
   CSSelectorAttribute attr2 = new CSSelectorAttribute("name", null, null, -1);
   CSSelectorAttribute[] attrs = { attr1, attr2 };
   CSSelector selector = new CSSelector(attrs);

   /***** 
    Number 2: constraint -- filtering as in which type of related assets should be retrieved.
    This example looks for *.jpg in the file name -- basically any .jpg image.
   ******/
   CSMatchesConstraint fileNameContraint = new CSMatchesConstraint("name", "*.jpg", CSAttributeCase.DEFAULT);

   /***** 
    Number 3: orderby -- self-explanatory.  It is optional so we'll just ignore it for now.
   ******/

   CSQuery query = new CSQuery(selector, fileNameContraint, null);
   CSQueryResult res = yourFile.getRelatedAssets(query.toString(), 0, -1, true, true);

HTH!

Adam Stoller

First - a correction:

So according to the javadocs - CSFile's getRelatedAssets() [...] takes the following parameters
* queryId - Id of the query previously executed
* offset - offset in resultset at which to begin iteration
* maxElements - maximum number of files that the iterator should return. If -1, the iterator will not limit the number of files returned.

I got confused when apparently the first link for getRelatedAssets in the CSFile javadoc takes you to the second definition - and I only scrolled down from there instead of looking up to find the other getRelatedAssets() definition.

Basically query parameter defines what type of information you want to retrieve:
...
HTH!

It does help - though I'm still working through it right now...

I can't quite get the query to work [yet] - I'm trying to create a "non-constraint" - so I tried modifying your suggested code so it comes out as:[html]

vpath
name

name
*
default

[/html]But that seems to be considered as having a syntax error.

So I'm back to having "fun" with Java development in TeamSite:

I'll post back if/when I have something that works - or if I'm ready to start beating my head against a wall... whichever comes first ;-)

vpatel

make_toolkit / build.bat is recompiling/refreshing various web-apps (i.e. iw-cc and / or iw-preview) depending on what type of changes you are making. If it is updating iw-cc, then your session would be lost :-)!

Adam Stoller

make_toolkit / build.bat is recompiling/refreshing various web-apps (i.e. iw-cc and / or iw-preview) depending on what type of changes you are making. If it is updating iw-cc, then your session would be lost :-)!

Hmm - I didn't verify, maybe when I change log4j.xml it loses the authentication -- but I don't think I changed it all the times I lost it - and the only other file I've been editing has been the same one java source file -- so I'm still not sure about this (from a consistency stand-point) - and still not thrilled at the disruptions I'm causing my colleagues (or rather, they're not thrilled with me:-).

I've finally got a query that compiles (doesn't throw a run-time exception) - but I'm still not getting any results. The query comes out as:[html]

vpath
name

name.*default

[/html]but I don't seem to be getting any results (if I select the file in the GUI and use Actions > Find Related Files I get back around a dozen files listed).

Do you see anything [logically] wrong with this code snippet:

...
CSQuery query = new CSQuery(selector, constraint, null);
for (CSSimpleFile sfile : sflist) {
    logger.debug("A");
    try {
        CSQueryResult qres = sfile.getRelatedAssets(query.toString(), 0, -1, true, true);
        CSIterator results = qres.getResultsIterator();
       if (results != null) {
           logger.debug("B");
           while (results.hasNext()) {
               logger.debug("RESULTS: " + results.next().toString());
               CSSimpleFile file = (CSSimpleFile) results.next();
               outList.add(file); //arraylist of CSSimpleFiles
            }
        }
        else { logger.debug("No Reults Found"); }
    } catch (CSException e) {
        logger.error("Query Failed: " + e.getMessage() +
                     "\nFile: " + sfile.getName() +
                     "\nQuery: ===\n" + query.toString() + "\n===");
    }
    logger.debug("C");
}
logger.debug("D");

Because right now, I'm seeing the alerts for "A", "B", "C", and "D" - but not any of the other ones - which means (if I understand this correctly) that I have a non-null-but-empty CSIterator named "results". It's a slight improvement over getting a "No results found" and/or "Query Failed" message due to a syntax error in the query - but not by much...

Adam Stoller

I believe I may have found a solution going a slightly different route.
First - for those, like me, who dislike having to constantly bounce the GUI services on a shared development resource, I put together a combination of a bunch of other threads along with my own conclusions on getting a remote CLT-is CSSDK program to work in this thread.

Secondly - to get the dependencies I ended up doing the following:

...
For (CSSimpleFile sfile : sflist) {
    CSAssociation[] dependencies;
    try {
        dependencies = sfile.getParentAssociations(null);
        for (CSAssociation assoc : dependencies) {
            System.out.println("=> " + assoc.getSecondary().getUAI());
        }
    } catch (CSException e) {
        e.printStackTrace(); return;
    }
    ...
}
...

I still need to modify the above code to use the information in

dependencies

and/or

assoc

(rather than just print it to STDOUT) - but this appears to give me the same list of files as the OOTB menu item - and it's a **** of a lot more than I was getting from that query.

I'm still a bit curious whether that query should have worked and if so, what was wrong with it - but as I now have something to produces results, I'm willing to move forward.

Ankmit

Hi All,

We have raised the ticket with IW and found the reply that DependentURI is no longer available in TS 7.2+

@ghoti: We are not using LS, we are still using DCR based components.We have migrated Content from 6.7.2 SP1 to TS 7.1 then TS 7.1 to TS 7.2+.
DependentURI was there in migrated contents but not in newly created pages in TS 7.2+.

@vpatel: Thanks for your explanantion.We have script to set EA manually but in TS 7.2+ it was not effective I suppose.Let me look into that too

I hope I have answered your question

Ankmit

Hi ghoti,

Let me try to implement your code in our environment and come up with the results.

Thanks for all your effort.

cmscooler

Did anybody get CSAssociatable.getRelatedAssets() to return any results? Like Adam described, I eventually managed to get the head spinning banging my head.

datacube_problem.jpg

new_report_01.rptdesign