Command iw.group.edit not found in command descriptors

Hi,

TS732 @ win2k8.

When I have selected the 'CC Std' gui (or 'Teamsite' as it is dubbed in this version) and use one of the 'command url's' like /iw-cc/edit I get the error:

[PHP]Command iw.group.edit not found in the command descriptors.[/PHP]

Is this a bug?
Has this functionality been obsoleted in this version?

BTW: if I switch back to 'CC Pro' the very same url command works fine!

Find more posts tagged with

Comments

Rick Poulin

When I have selected the 'CC Std' gui (or 'Teamsite' as it is dubbed in this version) and use one of the 'command url's' like /iw-cc/edit I get the error:

Careful.. CCStd is not the same as TeamSiteUI. It's its replacement, but ccstd (the old one) is still kicking around.

I don't know if that qualifies as a bug or not. I haven't come across a note saying the URLCommands have explicitly been deprecated, but they're curiously missing from the 7.3.2 UI Customization Guide. It would be useful to have clarification from HP via a support ticket.

RonaldV

It would be useful to have clarification from HP via a support ticket.

Meaning being on the phone with somebody who hardly speaks english, asks me all kind of irrelevant questions and does not understand why anybody would ever want to use these command urls?

Migrateduser

Meaning being on the phone with somebody who hardly speaks english, asks me all kind of irrelevant questions and does not understand why anybody would ever want to use these command urls?

In other words....yes that's exactly what he meant.

Adam Stoller

Meaning being on the phone with somebody who hardly speaks english, asks me all kind of irrelevant questions and does not understand why anybody would ever want to use these command urls?

Alternatively - meaning someone well versed in explaining what they are trying to do, how they are trying to do it, and what is (or is not) happening, composes a clear and concise description of the preceding by opening a support case online. You can often bypass most of the problems with phone support that way (at least in my experience - you still run into it sometimes, but far less frequently)

iHub 16 REST Data Source.png

RonaldV

Ghoti,

I think that is because the support guys know you are the master of devnet and they better be nice to you. It never happens to me.

Adam Stoller

Ghoti,

I think that is because the support guys know you are the master of devnet and they better be nice to you. It never happens to me.

As time goes on, fewer and fewer of the Support folks who know/knew me are still there - but I suppose it does help that some of them do know who I am. However, I still find it much better to file cases online where I have control of explaining the situation than calling and letting the information get poorly filtered into a description of the issue written by them...

Migrateduser

To be fair, there are some support engineers who are top notch. All of them are in the US. I have found that the lower tier of support tends to be offshore. If I get offshored with a support case, I immediately call to have the case transferred to someone in the US. It's just a waste of my time to deal with someone who's best response to any situation is to "have a live meeting", which seems to be the common reaction when they don't have the first clue what I'm talking about.

RonaldV

Hi,

iwov-support has confirmed that this is a bug but are, so far, not inclined to fix it. This I think is very weird as I am sure this effects many more clients then just us.

Rick Poulin

iwov-support has confirmed that this is a bug but are, so far, not inclined to fix it. This I think is very weird as I am sure this effects many more clients then just us.

There was another thread where support basically admitted that the new TeamSite UI isn't ready for production use, so.. not sure what to make of that.

There's also been an annoying workflow bug that's been around for ever, which they've declined to fix and has no 'good' workaround. It's been encountered by at least half a dozen clients that I know of, so sometimes I wonder how "facebook and twitter integration" takes precedence over "fixing the workflow engine"...

/just sayin.. it's frustrating.