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

Form (DCT) permissions in Standard View

SueHernandez

Summary: My user can't see any forms in Standard view.

I have migrated a system from 6.0.1 to 6.7.1. We have some Data Capture Template forms that can be accessed via File --> New Form Entry in the professional view.

When I first upgraded, even though I could enter a new form in the prof view, I didn't see the form in the "New Forms" section (bottom right) in the Standard view. I had myself added to the right Active Directory group, and now I see it just fine.

We opened up the testing to users. My user, who is in this same active directory group, sees no forms at all in the "New Forms" area. I believe everything is the right permissions - but I'm a master and he's not. I imported this user from the old system using iwusermigrate.

Does anyone have any tips where else I need to check permissions? What exactly controls what forms you are able to see in Standard view?

Thanks in advance

Sue H

Find more posts tagged with

Comments

moonkhanna

6.7.1 has branch level security roles. Navigate to the branch and view its properties. What role do you see the user in? Is the group, you are pointing to is added as author\ editor\ admin\ master on the branch, then check the filesystem permissions for the workarea you are referring to. What do you see there? Paste the portion of your templating.cfg which configures this DCT.

SueHernandez

6.7.1 has branch level security roles. Navigate to the branch and view its properties. What role do you see the user in? Is the group, you are pointing to is added as author\ editor\ admin\ master on the branch, then check the filesystem permissions for the workarea you are referring to. What do you see there? Paste the portion of your templating.cfg which configures this DCT.

Thank you for your reply. OK it turns out that using iwaccessmigrate.exe did not work. It added 85 groups, but then when you go to the branch and view the properties, as you suggest, you see "<no group> - Author". I.e. it assigned several "groups" to roles in each branch, but it somehow lost the association with the actual group, so nothing actually got assigned.

I put in a support ticket for that (iwaccessmigrate) but anyway this forces me to look at / clean up our Active Directory group permissions anyway. It turns out that our A/D groups for each branch were all assigned the "Reviewer" role which means members in this group can't do anything, by default.

So I'm going through by hand now and cleaning up the permissions.

Thanks for pointing me in the right direction.

Sue