How to provide a consistent Home dashboard for new Homer Users

[jagnetta]

I have created a set of call search criteria for the "Admin" user on our system. I have managed to export that data, and I can apply it to other systems, and allow the Admin user on the next system to have the same experience as on the original system.

Now the challenge is for adding a new user (i.e., other than Admin or Support), and have the Home dashboard have the same Call SIP Search boxes presented to the new user in the panel.

Thanks for your time.

[github-actions]

Your report is appreciated. Please star this repository to motivate its developers! ⭐

[bilalrao12]

Probably you can add a new custome dashboard with required fields and set it as shared.

[jagnetta]

Hi @bilalrao12 ,

I found this stanza in webapp_config.json which looks oood, but it doesn't seem to be working.

"dashboard_settings": { "_comment": "Here you can define a customs dashboards home", "dashboard_home": "/usr/local/homer/etc/Home_8x8.json" },
If I add a new user the new users' dashboard does not render.....

Please review and advise.

Home_8x8.json

[Dletta]

Please make sure it's set to 'Shared', otherwise it will not show up for the user.

[jagnetta]

Hi Dletta, I hope you're well. There is a line in the json file "shared," I have set it to true. The new user does not see the dashboard on login unfortunately.

I'll repeat the process, but I'm going to generate the file from the "support user" instead of "admin"

LMK if you have any logs or anything you think I should check.

PS - What I'm trying to do is have a standardized dashboard to be displayed when a new user logs in to homer.

[lmangani]

Hi Jim,

This is quite normal and should work out of the box and so far our team could not reproduce the problem.
Do those users at least see the default dashboards when accessing?

[jagnetta]

Hi Lorenzo, yeah, I thought so. I seem to have lost the original dashboard_home.json, if you have a copy somewhere, might you send it along? Maybe it's in the repo, I'll look there.

At this point, no, the new users see no dashboards. Only the Admin and Support users can see it. So that's why I kind of wanted to start fresh.

[jagnetta]

Hi Lorenzo,

I have retested this on several machines. I cannot get a specific dashboard to become a "defaut dashboard" for all users to share a common experienced. I've tried a variety of tricks to make it work, and it really isn't working.

If there's anything I can provide, I' happy to send it along.

Thanks!

[jagnetta]

I've attached dashboard_home and webapp_config for your review.

When the dashboard json file is loaded the user does not see all the extra search filters, and the clock TZ is not updated.

webapp_config.json
dashboard_home.json

[AlexeyOplachko]

Thanks for your data, managed to replicate it, should provide a fix soon @jagnetta

[jagnetta]

@AlexeyOplachko - Thanks for the update. Please let me know if you need any other information.

[AlexeyOplachko]

So main issue turned out to be due to slightly incorrect format on export. Once we release new version you should be good to go to export new .json file for your dashboard and put it as you did before as default @jagnetta

[jagnetta]

@AlexeyOplachko thanks for the great news. I look forward to the new release.

[jagnetta]

@AlexeyOplachko - has the new version been released yet?

[naqashsaeed]

I try to test this issue on Homer-app 1.5.3 using following steps:

1. Create shared dashboard from admin user.
2. Now create brand new user and Login from that user.
3. Now this new user can also see that shared dashboard.

This issue in unable to reproduce.

[github-actions]

Your report is appreciated. Please star this repository to motivate its developers! ⭐

[jagnetta]

1. create admin user "newguy" via the admin UI
2. Login to homer as "newguy" no dashboard available
3. Applog:

{"level":"debug","msg":"57 \u003cnil\u003e","time":"2024-08-27T11:05:17Z"}
{"level":"debug","msg":"55 \u003cnil\u003e","time":"2024-08-27T11:05:17Z"}
{"level":"debug","msg":"Current time : 2024-08-27 11:05:18.801423029 +0000 UTC m=+721.118190419","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Local time : 2024-08-27 11:05:18.801423029 +0000 UTC m=+721.118190419","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Expire Local time : 2024-08-28 07:05:18.801423029 +0000 UTC m=+72721.118190419","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:18Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"*** Database Session created *** ","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:19Z"}
{"level":"error","msg":"Dashboard has null in the name....","time":"2024-08-27T11:05:19Z"}
{"level":"error","msg":"Dashboard has null in the name....","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Token access has been disabled: api_settings.enable_token_access","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"Claims","time":"2024-08-27T11:05:19Z"}
{"level":"debug","msg":"\u0026{newguy true admin false  New Guy  { 1724828718  0  0 }}","time":"2024-08-27T11:05:19Z"}
{"level":"error","msg":"Dashboard has null in the name....","time":"2024-08-27T11:05:19Z"}
{"level":"error","msg":"Dashboard has null in the name....","time":"2024-08-27T11:05:19Z"}

Complains about "null in the name" the DB shows no "name" column, and none of the "name" entries in the xml are null. The UI shows null in this list:

[jagnetta]

Didn't even notice in the screenshot from the last comment, it shows 4 entries for "newguy" one of which is not circled which appears before the three in the list which are circled. the DB shows 4 entries for "newguy" as well, but everyone else has 3.

All the others were added by loading entries in the user_settings table directly through a file using postgres COPY commands to automate deployment.

This is happening with homer-app 1.5.3, and 1.4.59

[jagnetta]

Good morning,

I found a pretty good reason for most of the user account and dashboard problems, and ofc, mostly my problem. This is mainly down to my efforts to automate homer deployments and homer user management. Basically, I'm importing the user and user_config tables into the homer_config. What I was doing wrong was not allowing some space for new users to be added. I was using id numbers in those tables which homer wanted to use for any new users. So, I moved my manual additions to have user id numbers greater than 10000, which seems to have fixed the problem of a new user created with no dashboard.

Does the attached dashboard.json file (below) have the "slight formatting error on export" as referenced above?

dashboard_homer_8x8_initial.json

Thanks,
Jiim

[AlexeyOplachko]

Good morning,

I found a pretty good reason for most of the user account and dashboard problems, and ofc, mostly my problem. This is mainly down to my efforts to automate homer deployments and homer user management. Basically, I'm importing the user and user_config tables into the homer_config. What I was doing wrong was not allowing some space for new users to be added. I was using id numbers in those tables which homer wanted to use for any new users. So, I moved my manual additions to have user id numbers greater than 10000, which seems to have fixed the problem of a new user created with no dashboard.

Does the attached dashboard.json file (below) have the "slight formatting error on export" as referenced above?

dashboard_homer_8x8_initial.json

Thanks, Jiim

Hi Jim, yes, this is correct json.
Correct json starts with alias field, while incorrect one is wrapped into data and has auth field above