Frank Bergmann

Hi Antanas, I understand you just did a "vanilla installation" following the instructions and then you tried to manually install the intranet-reporting-indicators on top of that, is that correct? It seems that the data-model already included the data from this package, even though it is not "installed" ("installing" is just one entry in the database, the main part is loading the related tables and meta data). And because the entries for the indicators already exist, the DB reject duplicate new indicators...

Hi Antanas, Delete all ~projop/log/error.log*, do a "killall -9 nsd" and check the error.log for "Error:" or "Warning:". Please post the result! :-) V5.1 V5.2 is just packaging a number of changes from the last months. You're a long-time user. Could you have a quick look at the installers (Windows and Linux VM based on Ubuntu server this time) and tell us if you see any issues? It should only take a few minutes each... Cheers Frank

Hi Diego, Sorry, there is no way to "debug" your code without seeing your code. There is a feature in PO to convert hours logged into days logged. But the system will probably never be able to allow users to enter "days", because all the internal data structures work on hours. Cheers Frank

Hi, You didn't mention the version you are running... This message means that for some reason the following Library has not been loaded: ~/packages/intranet-reporting-indicators/tcl/intranet-reporting-indicators-procs.tcl Please check if there are permission issues or similar. You can work around the error simply disabling the portlet in Admin -> Portlets -> check for the page in which the error appears. We're working on PO V5.2 currently. Maybe you want to try that as soon as it comes out. I'll...

Hi, we're working on a new version with the latest PG. I can't provide a date yet, but it shouldn't take too long. Please check again in 3 months.

Hi Diego, Did I get this correctly that you have manually edited the page? That's basically impossible for us to support, because we can't diagnose your errors... However, there is a parameter "TimesheetLastMonthClosingDay" that allows you to "close" the last month at the given day of the current month (not allow to log more hours to the past month). Have a look at this parameter and how it works, this might guide you. Bests Frank

Hi Tarek, We are currently working on a OAuth2 based SSO solution. We've got SSO running with Google Cloud as provider. You won't need the REST API for this one. Bests Frank

Hi JD, We will probably go with Debian for the next version, so no, Rocky won't officially be "supported". Also, we found incompatibilities in RHEL 8. This not definitive yet, but that's the direction we are thinking about. At the moment the safest move is to buy support for RHEL 7. Best regards Frank