If I understand this, you are trying to create a new flow for the Setup Payroll Screen, so you can configure it to use the TreeNavigation7 harness?
Baed on the error you are reporting, you are attempting to create this new flow using the same name as the exisitng flow. Same-type record names must be unique.
You could delete the existing record, then create the new record using that name. Or, you could leave the existing record, and create a new record using a different name. If you choose this second option, remember to change the references so the new record is used.
As for now I am not trying to do anything, I just boot up the exercise VM, log in, open the "Payroll Setup" case type and click Save. I then get the error.
What I did just before was create a flow named "Setup Screen" (SetupScreen) which I don't think existed before. I then wasn't sure how to replace the existing step "Setup Payroll" (SetupPayroll) with it so I may have clicked here and there. If I simply remove the "Setup Payroll" step and try to save the case type I get the same error.
BTW, for me the fact that I can't open sth and save it without touching anything qualifies as a Pega bug and I would happily report it in a more appropriate place.
I am confident this is not a bug. The error you are getting is consistent with trying to create a record of the same name as one that already exists - and this is one "feature" of Pega that works solidly. There is always an indication of the offending record - maybe you could post a screen shot so I can help you identify what that record is?
Alternatively, you could simply close the Payroll Setup case type (clicking OK to dismiss the warning about any unsaved changes). This would allow you to start from a known good position.
I tried several times closing the case type (and even rebooting Pega). As I said I don't touch anything between opening the case type and trying to save it. So what you call a "known good position" is what gets me the error.
However by trying various things I got the error to disappear. Last thing I did was open the case type, rename step "Setup Payroll" to "Setup Screen", then do "Delete this step", then save. I'm not sure what good this did but...
But now I get a new error message when trying to add the "Setup Screen" step. The message contains more information than the first one but I don't understand what's wrong either. Can you help me?
A thought: in two previous exercises I imported the solution zip into Pega and then build upon it. I did it with little thinking about branches as I don't understand them well yet. Could this be the cause of the error?
I am getting the same error in my production environment, just opened the case from the desigenr studio and clicked on save without making any changs, and it says Rule Already Exists, i dont have any branches in my application. Is there any other solution for this?