Approve content workflow failure

Please contact support. If it occurs in an unmodified standard workflow you need them to fix that for you. I don't suppose that you managed to create a cycle in the group structure as the error message suggests.

Thank you for your answer. Yes it is a standard workflow. Could you please explain what does cycle mean in this context?

Hello Raynard,

"running Group.Path(1038)" looks like it evaluates the DB root group name with localeId 1038 = Hungarian. Is it maintained?

The message "Invalid group structure (cycle)" might be misleading.

Regards, Martin

Script Help: <yourserver>/abs/help/en/script/ba/index.htm#report_OBJECTS_Group_path.htm

Hi Martin! 

Thank you for your answer. If I understand the question correctly then yes the database is maintained in Hungarian.

Could you please elaborate how could this cause the problem?

Thanks again and best regards, Raynard

Hello Raynard,

I was just wondering about the localeId because it is rare. If the approval requester started the workflow in a UI language not maintained in the content, the model comparison report could get into trouble resolving the model path.

re: Invalid group structure (cycle)

We had this error message in Aris 10 SR7 when generating governance workflows and versioning but it was fixed in 10 SR8 (cf. Release Notes Pivotal no. 5356658) and the real reason was a corrupted cloud search index. A cycle in the group structure never existed.

So it depends on your Aris release if this can give you a clue. Better to follow M. Zschuckelt's advice.

Regards, Martin

Hello Martin!

Thanks again for your answer. We are using 10 SR3 so I suppose it is possible that the cause of the problem is what you mentioned. Is there way that I can make sure that this is the root cause?

And I am not exactly sure what does "cycle in the group structure mean". Could you please explain it to me?

Best regard,

Raynard

Hello Raynard,

essentially this would mean a severe database inconsistency whereby a group would be contained in itself. The comments above make perfectly sense. You would need a patch to the script that is causing this issue.

The API used by the script is not safe, because it relies on the group names being maintained in the current language (Hungarian). Very likely you maintain your content only in English or some other language and your user chose Hungarian for the user interface. Since SR3 is already quite old, the following could happen now:

- there is a patch for SR3 that was built in the past, that solves this problem. Software AG support may supply you with it.

- there is no patch for your release, then you should upgrade to a current release like SR16c or SR15b. SR3 had its end of maintenance last year.