Approval Workflow 7.2.1

[JohanArvidsson]

Hi!

I recently had a customer who wanted to migrate from 7.1.1 -> 7.2.1. After this migration, in a testt environment, we noticed that some bugs started to appear in the Approval workflows.

I reinstalled my own environment with 7.2.1 to have a fresh install to see if this was a general bug with 7.2.1 or if it was only in their environment and I got the same result. I patched the environment to 7.2.1 P01 and still had the same issues.

The bug seems to appear when I modify the name on a button transition(the workflow).

After the name is modified the button name in the approval form is in all uppercase and the option to partial reject disappear.

The standard supplied workflows works as expected but as soon as you modify the name on a transition the bug appears.

I have tried using the standard CR approval template and tried using the Role Owners Approval workflow.

I haven't touched the approval forms I only modified the name in the button transition.

Approval using the Standard role owner approval workflow:

Approval using the Modified role owner approval workflow (appended an a the end of each name):

Sometimes, on the modified workflow, partial rejected is apparent(modifyPic_1) but after I click on rejected(modifyPic_2) and then back again to accept(modifyPic_1) the partial rejected option has disappeared.

(modifyPic_1)

(modifyPic_2)

(modifyPic_3)

I'm wondering if anyone has experienced the same or could try this case to see if this is an general problem? (Mostafa Helmy‌ (?), Ian Staines‌ (?))

(The data used in this example is just test data and fictional data)

//Johan

[MHelmy · Accepted solution]

So to summarize, the Approved transition has the checkbox to allow partial rejection enabled.

When you change the approved transition name, sometimes the partial rejection buttons disappear from the beginning and sometimes it disappears if you select the Rejected option then back to the Approved option.

If that is the case and you can reproduce it, I would recommend raising a case with RSA Support to investigate this.

[JohanArvidsson]

Yes that is correct! The name of the transition will also be uppercase by default after a name change!

Yes I will raise a support case!

Just wanted to check if anyone else had the same problem and if so is the case then update the broad majority of users that this case might exists before they consider an upgrade.

[JohanArvidsson]

I have raised a support case.

I will leave this question open for now to see if more people experience the same issue and then mark your answer as correct later.

[IanStaines]

You might try deleting the problem node and transitions, saving the workflow, then opening up the workflow and creating the nodes again from scratch.

There can sometimes be data migration issues with workflows created on an older version that causes the resulting workflow nodes to be in an indeterminate state.  

If you try and reproduce the issue, try on a new workflow to confirm this is a defect and not a migration issue. 

[JohanArvidsson]

Hi Ian!

Yes I have tried deleting the problem node and the recreate it with a fresh new, that have worked sometimes before with other problems so was one of my first actions, but resulted in the same issue.

As my environment is a fresh install I doubt this is a migration issues (hence why I reinstalled my own environment to see if this was a migration issue or not).

The tests above is done with newly created workflows in a new fresh environment so I think I can rule it out that it would be a migration issue but thanks for the suggestion!

[IanStaines]

I see you opened case 01698290 for this issue.  I will monitor it for a solution.