Santiago Aucejo

Hello Daniel, I can now confirm that the problem is definitely related to dependencies determined with a 2.7.x version after upgrading to 2.8.2. We have revisited the workaround 2 : "Update Dependencies" and found that while all still existing items are properly updated, other entries, e.g. dependencies related to already removed items haven´t been cleaned up properly, still linger in the dependencies table of the database and block the process for all other items, too. I can also confirm now an...

Hello Daniel, unfortunately there is not much you can do. The stacktrace you posted is sufficient as it points to the specific occurence of this error. The bug is already fixed for the next release 2.8.3 due end of Febuary. Please check the Jira Issue for updates in case we provide a patch for 2.8.2 before the release of 2.8.3. Currently i am checking if a patch release for this is possible as the occurence of this bug is hard to reproduce and does only occur in specific circumstances when some old...

Hello Daniel, thank you for the information. I have created a Jira Issue for this which you can track here: https://change.sos-berlin.com/browse/JOC-2161 With https://change.sos-berlin.com/browse/JOC-2136 we have optimized the proccesing of dependencies dramatically (performance and stability). Unfortunately, dependencies that have been determined before the change in 2.8.2 sometimes do not contain references which leads to the NPE you experienced. Workaround 1: As described also in the Jira Issue...

Hello Daniel, thank you for the information. I have created a Jira Issue for this which you can track here: https://change.sos-berlin.com/browse/JOC-2161 With https://change.sos-berlin.com/browse/JOC-2136 we have optimized the proccesing of dependencies dramatically (performance and stability). Unfortunately, dependencies that have been determined before the change in 2.8.2 sometimes do not contain references which leads to the NPE you experienced. Workaround 1: As described also in the Jira Issue...

Hello Daniel, thank you for the information. I have created a Jira Issue for this which you can track here: https://change.sos-berlin.com/browse/JOC-2161 With https://change.sos-berlin.com/browse/JOC-2136 we have optimized the proccesing of dependencies dramatically (performance and stability). Unfortunately, dependencies that have been determined before the change in 2.8.2 sometimes do not contain references which leads to the NPE you experienced. Workarounds (also in the Jira Issue): * Workaround...

Hello Daniel, thank you for your findings. I can reproduce the issue and have raised an issue in our issue management to be resolved with release 2.8.2. To track to progress you can find the issue here: https://change.sos-berlin.com/browse/JOC-2134 In the description of the issue i have posted a rather ugly workaround, but it should work at least. Thank you and Best Regards Santiago

Hello Daniel, if a workflow is not deployed, meaning the workflow is currently not deployed to any controller or deleted from any controller due to a "remove" or "revoke" operation, then it should not reappear when you "store everything" to the local Git repository. Best Regards Santiago

Hello Daniel, Please have a look at the docs at https://kb.sos-berlin.com/display/JS7/JS7+-+Git+Repository+Interface#JS7GitRepositoryInterface-GitOperations . if you want to delete objects from the local repository you should use the "Delete from Git Repository" operation instead of the "Store to Git Repository" operation you are using. When you use the "Store to Git Repository" operation in your case, the following will happen: items from that folder, that have been previously deployed to one or...