I am using this Inbox component. This needs a user object. So I have done
User usr = AppBeans.get(UserSessionSource.class).getUserSession().getUser();
and provided this as input to
messageService.sendMessage(usr,"test","New Object created ", newTestEnitity);
This will send a mail to current user. But if I need to send it to a list of users, I can maintain the list some where, how do we initialize the user object. Means, I have just a name like Thomas and I need to initialize a user object with this string.
Also can we use this to send mails when a workflow activity is assigned? I know there is a process task, but such a mail would help users.
Also, is there a way, to upgrade this component from 6.9 to current 7? I have currently created a 6.9 project.
Unrelated question, as I do not want to create a new thread. In BPM example shown, we see that manager and controller is assigned in run time. Can we have a template stored, which we can bind to the workflow. It will make it dynamic.
user-inbox application component for Cuba Platform is released in version 0.6.0 with CUBA 7 support. Check it out: GitHub - mariodavid/cuba-component-user-inbox: CUBA component that gives users a mailbox for user-to-user and system-to-user messages
Thank You. I will check this out.
I added the component to an existing project of mine and see the following error. I had been able to use the older version with out these error.
It looks like you didn’t trigger db updates.
You can use studio: run > update db. You should see them log entries regarding Sql scripts from the addon.
Which RDBMS is used?
Thanks Mario. That was indeed the problem. Currently it is running on the regular HSQL DB.
I have a few questions:
Installing the add-on has led to the application menu now located on the left. How and where can I fix it (web-menu.xml has not changed after installing the add-on)?
I want to add localization for buttons and other elements of add-on screens. Tell me how to do it? (I cannot find required *.property files)
here are the answers to it:
1.the addon offers two main window screen with out of the box buttons for the user inbox (see: GitHub - mariodavid/cuba-component-user-inbox: CUBA component that gives users a mailbox for user-to-user and system-to-user messages). Currently this addon activates a particular main window layout (side menu). If you want to change that, set the other main window in the web-menu.xml as follows:
or set your own main window if you have other mechanisms in place.
- You can find the messages.properties file in the sources of the addon:
You can override the values as you would normally do it for other platform translations.
Mario, thank you very much!
My first question solved!
About second question:
If I do RUssian localization for all messages.properties files of your add-on, will you be able to include it in the new version of the add-on? And how to do it right, if you will agree with it (I’ve never done this on GITHUB)?
I have one more question, if I may. I need to associate a message ID with some entity in my application. More precisely, to record correspondence within one object in my application. Is there such a possibility?
I installed v.0.6.0 version of this component on 7.1.0 platform. I installed also Declarative controller v.0.8.0.
I’am trying on new project. I added on web-screens.xml follow lines
but on side menù I can’t see nothing.
What I wrong ?
Hi @mario, can you help me ?
the UserInbox add-on is supported by platform version 7.1?
Yes this is possible. You can associate a message to a business entity. See here: cuba-component-user-inbox/README.md at master · mariodavid/cuba-component-user-inbox · GitHub and also the programmatic usage section in the docs.
I did not released a 7.1 version of the addon yet. Probably it will just work though. You can just try it out and see if any error occurs.
Can you share an example app that shows the problem? Thanks
Is there plans to upgrade this User Inbox to 7.2. It works though, how ever I still see the old style application menu. 7.2 come with new style menu and I tried adding the entry in web-screens.xml, but it did not work. Any suggestions?