Diff Users editing diff parts of record

I have a datacapture.cfg file that I need to allow multi users to edit at different times and different parts. I can't seem to get cred user to work. I got cred role to work but I don't under stand how they are not going to over write the other users who will be editing other parts of same .cfg and generating.

Find more posts tagged with

Comments

gzevin

DCT mechanism will handle this, don't worry Smiley Happy

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

LucretiaHolcomb

OK...but when they generate to the same url wont that overwrite?

Could I send you my datacapture.cfg and templating.cfg to make sure I am doing this correctly. I have 9 unique users editing different parts. I got the cred user working. However, when they create a new record...it show all the other fields with this verbage <no data entered>. But that unique user can enter their info.

gzevin

have you tried all 9 users and then inspected the contents of that DCR?

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

LucretiaHolcomb

No. Just individual users. Each user will be making mods at different times.

gzevin

This is exactly what I meant. After all 9 users made their changes at different times - what can you see?

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

bturns

What are you're requirements for the templates? How many documents (URLs) do you want to generate from a dcr. If you are generating one html page for each dcr then the URL will be overwritten each time. However, it will be overwritten with all the data contained in your DCR. You won't have a problem generating to the same URL as long as your .tpl is configured correctly.

LucretiaHolcomb

I logged in as each two of the different users. Did updates and generated (the file name is the same 'name.htm') and the htm file only shows the last users changes and blanks on everyone elses.

This has been so complicated and I am novice. I know there must be a simple solution.

LucretiaHolcomb

I am attaching a file

LucretiaHolcomb

last one

bturns

Will you send the DCR also.

LucretiaHolcomb

Yes...you are my angel!!!

I added the .txt extention so that it would attach.

LucretiaHolcomb

I want to only generate one .htm page. But multi users will be generating it at different times having access to different parts.

We had an IW consultant come in and each one told us different stuff, but they could never get it working before they left.

LucretiaHolcomb

Does it make sense what we need? I really appreciate all the help I can get on this. Thanks

Adam Stoller

Are these different users editing the DCR in the same workarea or different workareas?
If the same workarea - what you described sounds like it should work correctly.
If different workareas - you need to make sure that the DCR is updated (GetLatest / iwupdate) in each workarea before editing and submitted to STAGING after editing.

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

LucretiaHolcomb

It is different users editing the same dcr in the same workarea. But how do they each generate without creating blanks where the others are to do their updates.

Adam Stoller

The way it *should* work (as far as I know) is this:

userA creates DCR-1 and fills in fields F1, F2, and F7, saves DCR-1 and generates a page with information from F1, F2, and F7 included.

userB edits DCR-1 and fills in fields F3 and F4, saves DCR-1 and generates a page with informatikon from F1, F2, F3, F4, and F7 included.

userC edits DCR-1 and fills in fields F5 and F6, saves DCR-1 and generates a page with information from F1 through F7 included.

Any time a user edits an existing DCR - pre-exist field data should be preserved and allowed fields should be editable.

Any time a user generates a page from the DCR - all existing field data (whether entered by that user or not) should be accessible for using in the generated page.

The restrictions on access to the field should apply ONLY to filling in the form - NOT to accessing the data within the PT for generating the page.

Are you saying that you've got a verifiable example where this does NOT work like that?

If so - I suggest you contact Interwoven Support and work with them to resolve this - although it would seem unlikely, it's possible you uncovered a bug that somehow has slipped past everyone else (I'm not sure how frequently the allowed tags are actually used)

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

JonathonG

I think I know what the issue is. Try adding a readonly element to each of your item definitions, after the user-restricted one. For example, your first item reads:


<item name='pictureOne'>
    <label>Select the picture for the first group of community events:</label>
    <description>This image will show to the left of the text.  It should descibe 
    the community event</description>
    <browser initial-dir='/PowerWeb/images/' ceiling-dir='/PowerWeb/images/'> 
        <allowed><cred user ="iw\pdierkin"/></allowed>
    </browser> 
</item>

You should change it to:


<item name='pictureOne'>
    <label>Select the picture for the first group of community events:</label>
    <description>This image will show to the left of the text.  It should descibe 
    the community event</description>
    <browser initial-dir='/PowerWeb/images/' ceiling-dir='/PowerWeb/images/'> 
        <allowed><cred user ="iw\pdierkin"/></allowed>
    </browser>
<readonly/>
</item>

This tells the datacapture engine to make this item a readonly item if the user is any other than pdierkin. With the way you currently have it, the item will actually disappear from the datacapture specification for other users. Thus, the data that was stored by pdierkin has no place to live on the form and when it is saved, no data is saved for the item.

Hope this helps,

Jonathon
Independent Interwoven Contractor