Skip to main content
B
BrianToussaint19-Tanzanite
19-Tanzanite
March 3, 2020
Question

New CN to CR Closure Flow 11.2

  • March 3, 2020
  • 5 replies
  • 2887 views

Since I didn't go to 11.1, I cannot say for sure, but I'm thinking this is new to 11.2.  There is a massive change to the way that a Change Requests (CR) get closed when a Change Notice (CN) closes that it references.  For the old code no longer a closes CRs when a CN finalizes.  So far I have found that the code in the Synch Robot has changed quite a bit.  Also there is a new variable in the CR workflow called handlesClosure.  It isn't used in the code.  Does anyone know what all was added to the OOTB CR workflow and or CN workflow that I need to add to my custom CR and CN workflow?  I do have a call open, but haven't heard from anyone in 4 days.

5 replies

J
JeffZemsky17-Peridot
17-Peridot
March 3, 2020

@BrianToussaint  - did you convert your Changes to the new Flexible Change Association or have you been on it since 11?  This change came in 11.0 with the new Change Associations.

 

There is a section in Help that covers this

 

Change Workflow Closure

B
BrianToussaint19-TanzaniteAuthor
19-Tanzanite
March 3, 2020

@JeffZemsky - I do not remember changing anything when I went from 10.2 to 11.0 a few years ago.  It seems that all the 11.0 items that are associated are fine, but all the 11.0 to 11.2 or within 11.2 are what is messed up.  So I think that I didn't change to the new way.  So I'm thinking I should follow those instructions in my test environment and see if that fixes it.  Is there anything other than that or the page it links to that I need to do?

J
JeffZemsky17-Peridot
17-Peridot
March 3, 2020

@BrianToussaint  I forget the 11.0 default off the top of my head, but the 11.1 and onward default is to use the Flexible mode.  It sounds like you did not make the transition to Flexible mode. (And you should make this transition - we have not hard enforced it yet, but are looking at making the 12.0.x the last release one can be using the Legacy links.

Terms & ConditionsAccessibility statement