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

Deleting HTML + DCR in TS6.5 CC Standard?

jwl

Hi there,
We have TS6.5 SP1 on Solaris 9. Our customers are using CC Standard.
Back in our (outgoing) TS5.5.2 WebDeskPro environment, our customers could delete an HTML file and its DCR by ticking its checkbox, then selecting File -> New Job, and selecting our DeleteContent workflow.
In CC Standard, users can't delete HTML+DCR (the "Delete" function only deletes the HTML file). They also can't seem to invoke our DeleteContent workflow on a particular file.
Would be interested in seeing how others achieve HTML+DCR deletion in TS6.5 CC Std?
Thanks,
John

Find more posts tagged with

Comments

gzevin

In reply to:

They also can't seem to invoke our DeleteContent workflow on a particular file.

do you know why? have you configured it correctly?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jwl

Hi,
Let me clarify myself. I can't see how users in CC Std can invoke our DeleteContent workflow on a particular file, as they were able to in TS5.5.2 WebDeskPro. Hope that's clearer...
Thanks,
John

gzevin

can't they submit a file in CC STD?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jwl

Yes they can, but if the file is unmodified, the Submit function is greyed out. I don't want them to have to first modify a file before being able to Submit it to the DeleteContent workflow.

gzevin

Ah, Ok. got it.

what can I say. Ask Interwoven why in their design they made such a flop. does not make sense to me. And it does not make sense to me either the fact that there is no Delete HTML+DCR out of the box.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Migrateduser

yes GZevin, you are absolute right. sometime the IW functionality seems like a flop show Smiley Happy

.

~Rishi Gupta
Worksite MP 4.1 SP1 with HFB4 @ Linux

Adam Stoller

As I recall - one of the problems with CCStd in this aspect is the inability to actually 'select' a file.
The only work-around I can think of at the moment would be to add a custom menu item that provided the ability to select a file, and then, if it's a generated file have it find the DCR as well (unless your workflow already takes care of this) - and then use iwwft_compile.ipl to launch your DeleteContent workflow.

Alternatively, if they have the ability to delete a file and then want to invoke the job - again using a custom menu item - have it provide a list of the currently deleted files from which to select and then invoke the workflow (or, depending on what the workflow actually does, code all the logic directly into the custom menu item)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

gzevin

so.. what you are talking about are the vital enhancements/FRs for TS.

I repeat - is that only a few of us, consultants are so concerned? I agree, since 6.X, TS is a better product, at least visually, but probably because I use CC PRO mostly.

But when I start dealing with CC STD, I almost cry. so many flops/holes/etc.. and yet no signs of the product management addressing those issues. Many authors/editors do like CC STD and do not want to use CC PRO. But they have to because of many vital features being unavailable in CC STD. I am not talking about 'professional' features, but rather some very basic ones, like one that we are discussing

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jwl

Now I'm worried. All our customers are being trained in CC STD, which is the interface targeted at them. If their DCRs aren't deleted, their templatedata/ directory will become unsynchronised and unmanageable. I've confirmed that in CC PRO I can tick a file, then execute Action -> New Job -> DeleteContent (workflow), which works. I might end up having to train our users to enter CC PRO just for deletions? But that would mean they need to enter the "Workflow" tab to send off the Job.... which would be very confusing for them. "Surely" other companies out there are using CC STD - how are they solving this?
Thanks,
John

Adam Stoller

But that would mean they need to enter the "Workflow" tab to send off the Job

Huh? Do you mean to transition tasks? You already indicated knowing that you could do Action -> New Job from the navigation tab.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jwl

Uh yes, that's what I meant. Thanks.

gzevin

In reply to:

I might end up having to train our users to enter CC PRO just for deletions?

This is what IWOV says - for some 'admin' tasks one has to use CC PRO. Which is, as far as I am concerned, too bad. But this is not all. One cannot delete folders in CC STD.. for some reason.

if you start training your users in CC PRO, they might as well use it for any other purposes as well....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jwl

How about this? I can explain to users the problem with the Delete function, and in turn ask them to adopt the following procedure:
1. If FileActions->Submit is greyed out then:
___a. File Actions -> Tag
___b. Modify one of the metatags (doesn't matter what they do, since this file will be deleted)
___c. Click Next
___d. Click Cancel at the screen where they're asked to Submit.
___e. The file is now marked as Edited
2. Select FileActions -> Submit
3. Select DeleteContent workflow.
At least users don't have to flip over to CC PRO. Lesser of two evils?
Regards,
John

gzevin

yep, will work. an ugly workaround, though.

let IWOV product managers see this and think about introducting new fewtures into CC STD as soon as they can.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

manishfulambarka

Hi All
I have given the permission " 770" to a particular folder in Teamsite workarea. When the user who don't have the read,write, execute permission, still he is able to delete that folder. Why is it so. Is it a functionality or bug.

Thanks
Manish

gzevin

we'll have to see more information to see why this is happening. Usually it's better done right on site

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jwl

A cleaner workaround. Educate users to use Tag instead of Delete
1. File Actions -> Tag
2. Click Next at the metadata capture screen - no need to modify content
3. Click Next to Submit
4. Select DeleteContent workflow
5. continue as usual
Regards,
John

gzevin

You found a back door Smiley Happy

well done. Cleaner, I agree. But still.. out of whack with what you want to do.... Smiley Happy

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

jwl

Possibly even cleaner.... use the Assign Task feature instead of Tag.... at least I can tell the users that they're Assigning a file to the DeleteContent "task", rather than tagging it for deletion....