Skip to main content
J
jwagh18-Opal
18-Opal
November 10, 2015
Question

New to 10.2: Promotion Request rights worse than previous versions?!!

  • November 10, 2015
  • 7 replies
  • 2824 views

According to my research and the below SPRs, it appears that the rights for users to promote files are worse than previous versions of Windchill. Has anyone seen this? PTC does not want to fix it in 10.2.

  1. Users can promote checked out objects
  2. Promotion Requests with checked out objects will hand in the OPEN state and not change to UNDER REVIEW
  3. Objects UNDER REVIEW can be checked out

SPRs:

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS158224&source=Case%20Viewer

https://support.ptc.com/appserver/cs/view/spr.jsp?n=2892612&source=Case%20Viewer

7 replies

M
MikeLockwood22-Sapphire I
22-Sapphire I
November 10, 2015

There is simple code on two conditionals in the two OTB Promotion Workflow templates (same for many releases) that confirms that a Promote LC transition exists, etc.  Seems that additional simple code could be added to confirm that all objects are not checked out.  If someone does a stellar job of creating this code and provides it to PTC they will add. 🙂 //// Permissions for checking out objects on a Promotion Request and have used the LOCK transition to go to UNDER REVIEW are a different matter.  If a system is properly configured, users will not have MODIFY permission at the UNDER REVIEW state.

    C
    ChrisPLM12-Amethyst
    12-Amethyst
    November 12, 2015

    Agreed with you Mike.  While I was reading, I thought  Checking Out ability for UNDER REVIEW is just an authorisation matter.

    D
    ddemay1-Visitor
    1-Visitor
    November 11, 2015

    As Mike pointed out, code, and also configuration of lifecycle.  I'll also add, promotion requests are heading the ways of dust in the wind.  Change notices with their recent functionality improvements are the future.  Personally, I like promotion requests, because it to me is not indicating a change, but a bump in the status, creating extra ECR's or ECN's are a killer waste of time and sap performance if too many exist concurrently.

    S
    STEVEG21-Topaz I
    21-Topaz I
    November 11, 2015

    I agree David.  We also still use promo req occasionally even though we have change management.

    M
    MikeLockwood22-Sapphire I
    22-Sapphire I
    November 11, 2015

    Promotion serves the purpose very nicely for certain cases to simply change state.  It has the same collection functionality as change and allows for all needed workflow variations.  But - Promotion Requests cannot be edited and do not allow attachment files. For this reason, we are forced to change objects a few places.  We'd be happy to use just Change Notice + Change Task with Change Request, but one cannot create a CN/CT without selecting the Assignee / Reviewer roles and this greatly confuses every new user.  They also don't "get" the concept of implementation plan.  Their goal is to request a change - which is clear on a Change Request. We'd be very happy if Promotion Requests allowed for Editing and Attachments.

    Terms & ConditionsAccessibility statement