Skip to main content
J
jhall21-Visitor
1-Visitor
January 25, 2016
Question

User permissions question in 10.2

  • January 25, 2016
  • 3 replies
  • 3379 views

Hello,

My company is working out a new installation of Windchill 10.2  We use Creo 2.0 along with it.

We need our Users to be able to Reset Teams on our In Work WTParts, but not be able to Set State on those same, In Work parts.  Our admin is telling us that the software won't permit Eng Users to Reset Teams, unless they can ALSO Set States on those WTParts. 

Is there a way around this dilemma?   Having the Admins Reset Teams is frustrating and slows the designers down, since they have to wait on them.

3 replies

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
January 25, 2016

Not sure about Reset Team but suspect one has to be Admin or Manager of the context.  It's possible that there would be an ACL to the Team object, but don't recall seeing.

Set State is enabled by either:

A) Administrator or Manager of the context (regardless of the lifecycle)

B) Set State transition in the lifecycle from the current state + Set State permission at the current state.

    J
    jhall21-VisitorAuthor
    1-Visitor
    January 26, 2016

    Thanks Mike,

    Do you think an ACL could be written to give certain users the ability to reset teams, but not Set State, or perhaps other Admin permissions?

    James

    N
    Nitin1-Visitor
    1-Visitor
    January 26, 2016

    In my opinion, you should address this with a specific set of users added to a new role created for this purpose.

    Allowing designers to change teams as and when required can be dangerous at times particularly if you have to set limited access to certain data in contexts.

    Also you might want to revisit your business process to understand if there can be other business solutions to the scenario you might be trying to address.

    On a side note - Windchill workflows can be helpful here, since they can track your process and also provide ways to reset teams on fly.

      J
      jhall21-VisitorAuthor
      1-Visitor
      January 26, 2016

      Nitin

      That special role sounds interesting.  Could you describe what that might look like to me?  Thank you!

      K
      kpritchard1-Visitor
      1-Visitor
      January 26, 2016

      James,

      Modify Team is a separate permission from Set State and can be set for Object Type by Role and State in the Policy Administration Utility, and should allow the specified User Role to add and remove members.  Reset Team would be a re-imaging and may not be what you're after.  I would recommend testing in a non-production environment to be confirm desired behavior.

        E
        ehuffman-33-Newcomer
        3-Newcomer
        April 12, 2016

        James,

        I assume you have different teams because the parts are being processed through a workflow?  If so, you can reset your teams programmatically using standard APIs.  Which team to use would have to be based on a determined logic.  You can also configure use unique roles and only have one team.  This would allow you to reset the target role of a task based on the requirement, using the  specific role required.  For example, Q1, Q2 and Q3 are unique Quality roles and Q is the target.  Mapping either Q1, Q2 or Q3 members to Q can be done based on any configured logic (i.e. Soft Type Attribute or any combination of such).


        You can allow any Assigned Task to be a task allowing the mapping of principals to a role.  I believe the Change Request and Promotion Request both provide an example.

        I know there has been other comments regarding your question.  The truth is, WC is versatile, configurable and even customizable.  There is always a way.  Mine may not even answer your question.

        To your original question:

        wt.team.TeamHelper.service.reteam (wt.team.TeamManaged object, wt.team.TeamTemplateReference teamTemplateRef)


        This is basically the API that will reset your team.  You just have to fill in the gaps.

        Terms & ConditionsCookie settingsAccessibility statement