• State Verified Answer
  • Replies 12 replies
  • Answers 3 answers
  • Subscribers 25 subscribers
  • Views 4580 views
  • Users 0 members are here

Create Change Package option not available when there is a new not approved revision of a document

Kelly Wibbenmeyer

Bentley,

 

When I'm on an approved document that has a new not approved revision, why isn't there an option for "Create Change Package"?

I'm asking because I can create a CR and then go to the edit mode and add the approved revision and receive the log/implement/ignore screen.  I would assume that the same functionality would be available for the latest approved revision of the document when the user selects "Create Change Package" (if the option was available).  I can submit a ticket on this as well, but thought if anyone had any insight as to others having the same issue or same request- it would be helpful.

Thanks

Kelly

 

Parents
  • 0 Offline
    Hi Kelly,

    Has this issue been resolved? If so, could you please close the issue by selecting "This helped me" and "Verify Answer". If not, please let me know so I can follow up on this issue.

    Thanks

    Carma
  • 0 Offline in reply to Carma De Villiers
    No this has not been resolved. Please see my previous response.
  • 0 Offline in reply to Thomas Schoenbeck
    Hi Thomas,
    The Change Package will only work if all has been approved and under change control. If you require an enhancement, you need to add a ticket.
  • 0 Offline in reply to Carma De Villiers
    Carma,
    I understand what you are saying but I don't understand why it should function any differently when you're essentially doing the same task in a different way.

    Scenario 1: Find approved document with unapproved revision and create change package. Option for change package is not available due to new unapproved revision.

    Scenario 2: Create a new CR and then edit the CR and add the same approved document with unapproved revision. System allows us to add the document and implement even though the document still has a new unapproved revision.

    What we are saying is the functionality should be consistent regardless of which way you do it. If you can't create a change package for an approved document with an unapproved revision, why are you able to implement a change package for an approved document with an unapproved revision? It seems conflicting.
    Thanks,
    Tom
  • 0 Offline in reply to Thomas Schoenbeck
    Hi Tom,

    eB is a system based on Configuration Management and the Config has been built into the system with the config rules. I see what you are concerned about. I will speak to our Professional Services and get back to you regarding this.

    Regards
    Carma
  • 0 Offline in reply to Thomas Schoenbeck
    Hi Tom,

    I have received the following answers for Laurent:

    Scenario 1: Find approved document with unapproved revision and create change package. Option for change package is not available due to new unapproved revision:
    You should be able to raise a change on the latest / approved revision (it is still the released revision until the new revision is
    approved) but get a warning that there is a newer revision and the CR should be ‘carried-over’ to the new revision.

    Scenario 2: Create a new CR and then edit the CR and add the same approved document with unapproved revision. System allows us to add the document and implement even though the document still has a new unapproved revision:
    Same as above, however it is a carry over to the new revision because the user has already chosen what CR(s) to incorporate

    What we are saying is the functionality should be consistent regardless of which way you do it. If you can't create a change package for an approved document with an unapproved revision, why are you able to implement a change package for an approved document with an unapproved revision? It seems conflicting.
    I believe the principles should be the same if CP module is present or not – We may need to raise a bug report on this if it’s
    not behaving correctly.

    Please let me know if it is more clear. If required, please raise a bug report and add the bug number to this query.

    Regards
    Carma

    Answer Verified By: Carma De Villiers 

Reply
  • 0 Offline in reply to Thomas Schoenbeck
    Hi Tom,

    I have received the following answers for Laurent:

    Scenario 1: Find approved document with unapproved revision and create change package. Option for change package is not available due to new unapproved revision:
    You should be able to raise a change on the latest / approved revision (it is still the released revision until the new revision is
    approved) but get a warning that there is a newer revision and the CR should be ‘carried-over’ to the new revision.

    Scenario 2: Create a new CR and then edit the CR and add the same approved document with unapproved revision. System allows us to add the document and implement even though the document still has a new unapproved revision:
    Same as above, however it is a carry over to the new revision because the user has already chosen what CR(s) to incorporate

    What we are saying is the functionality should be consistent regardless of which way you do it. If you can't create a change package for an approved document with an unapproved revision, why are you able to implement a change package for an approved document with an unapproved revision? It seems conflicting.
    I believe the principles should be the same if CP module is present or not – We may need to raise a bug report on this if it’s
    not behaving correctly.

    Please let me know if it is more clear. If required, please raise a bug report and add the bug number to this query.

    Regards
    Carma

    Answer Verified By: Carma De Villiers 

Children
No Data
Communities
Support and Services
Training and Learning
Social Media