Autor
|
Thema: Secured By flag in the Project Manager window (2199 mal gelesen)
|
marco esposito Mitglied
Beiträge: 9 Registriert: 20.09.2005
|
erstellt am: 14. Nov. 2005 18:53 <-- editieren / zitieren --> Unities abgeben:
Excuse me for using english, but I speak a really poor german; I'd like to know how is possible to set the flag in the "Secured By" field as default, in the Project Manager window: in this way the users don't forget to secure their documents when they save them in Smarteam . Thanks in advance, best regards M. Esposto Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP |
KangarooJack Mitglied
Beiträge: 31 Registriert: 08.04.2005
|
erstellt am: 15. Nov. 2005 07:48 <-- editieren / zitieren --> Unities abgeben: Nur für marco esposito
|
marco esposito Mitglied
Beiträge: 9 Registriert: 20.09.2005
|
erstellt am: 22. Nov. 2005 01:03 <-- editieren / zitieren --> Unities abgeben:
Thanks for the script. It's working but I have found another problem: when I use joe I can add a Catia Part in the correct project and the script is working well "securing" the CatPart to the project. But if I use a user having a role "Designer" in the project (Project Role) I'm unable to add the CatPart : I receive a message about a unauthorized operation for the Document-Project link; but the Designer role has that correct kind of permission (given by User Maintenance). Why I'm receiving that message? More, in the script, is used the SmBehavior.ChackAuthorization = False setting, so I think the operation would have to perform even if the user has no authorization on the class. What's happening ? If I add the user to the Engineering group then I can add the Catpart to the project. Any hints about this problem?Thanks in advance, best regards, Marco Esposto Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP |
cwillmann Moderator PLM-Berater
Beiträge: 1487 Registriert: 17.03.2001 Job: die 'big three' in CAD & PDM - aber nicht (mehr) täglich!
|
erstellt am: 22. Nov. 2005 09:18 <-- editieren / zitieren --> Unities abgeben: Nur für marco esposito
Hello, what about your "project-based authorization"? You need to configure the project behaviour: "Restricted" -> Add the roles / users who should have access to the project and the secured documents inside. Did you read chapter 9 of the "SMARTEAM Editor Administrator Guide" - a pdf you can find on the ST Documentation CD or inside ST Support Website. Inside this chapter you should find very usefull informations for the different cases of project authorization.
------------------ Grüße,Christian Willmann --- Inoffizielle Pro/E-Hilfeseite http://PROE.CAD.de --- DENC AG http://www.denc.de Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP |
marco esposito Mitglied
Beiträge: 9 Registriert: 20.09.2005
|
erstellt am: 23. Nov. 2005 08:09 <-- editieren / zitieren --> Unities abgeben:
Thanks, but from documentation I understand that the Ristrected project is a further option, that I don't need: I need that people generally could see (only view) all documents (and this is possible by global groups or global roles) and team designers could work in their project (so the need of roles in the context of project); with the ristrected project instead the general people could not see all the projects. But there is the problem described in my previous note.... Any hints ? Bye, Marco Esposto Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP |
marco esposito Mitglied
Beiträge: 9 Registriert: 20.09.2005
|
erstellt am: 30. Nov. 2005 00:00 <-- editieren / zitieren --> Unities abgeben:
I solved the problem using scripts: instead of giving global "low" authorizations (view only, print) by global roles to all users, I solved giving global "high" authorizations (lifecycle operations) by global roles to all users , adding to them also specific roles to specific projects and filtering then with the scripts their access to these specific projects ; I added this script as Before script to all the lifecycle operations, the Update and Delete operations and for the Add operation I inserted the code in the SetDesc script. I attach here the code to insert in the SetDesc to filter the Add operation to the users not having the correct specific roles for the project. Bye, Marco Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP |
cwillmann Moderator PLM-Berater
Beiträge: 1487 Registriert: 17.03.2001 Job: die 'big three' in CAD & PDM - aber nicht (mehr) täglich!
|
erstellt am: 17. Feb. 2006 08:42 <-- editieren / zitieren --> Unities abgeben: Nur für marco esposito
Morning, I think I have a similar problem as Marco described above in combination with the "Design Copy" script. The "secure associate" option for the project is activated ("yellow key") for all documents. When I try to make a DesignCopy in the Role "Designer", the operation fails with an error message like "unauthorized operation for the ADD operation". If I only use the "normal" project association (only the chain-button), everything´s working fine with the Design Copy as a "Designer". But as an administrator I can copy "as I like", means independently of the Secure-Option! Perhaps it´s a problem with my authorizations, but I counldn´t find a suitable option for this. Do anyone have experiences with "SecuredBy" and DesignCopy? Thanks! ------------------ Grüße, Christian Willmann --- Eine Antwort auf diesen Beitrag verfassen (mit Zitat/Zitat des Beitrags) IP |