I cannot find a detailed documentation that talks about this aspect of customizing activities (To-dos) in Odoo 11 CE. I managed to programmatically (i.e. in Python) create new activities, associate them to a specific model instance, and assign them to a particular user.
But I still need to customize them further, and here are my questions:
When an activity appears in the activities menu (i.e. in the top bar of Odoo), it shows an icon, title, and few stats (i.e. number of Late, Today, and Future activities).
How can I customize the icon?
How can I customize the title?
How can I customize the stats?
How can I group the the activities based on some field in the model instances? (This will allow me to give different custom icons, titles, and stats to different groups, and also open different custom views upon clicking the groups)
When an activity is clicked, the default view of the associated model is opened; how can I open a custom view?
Thank you!
I think that your questions lead you to a non-existing activities/to-do features in Odoo. To be able to get it done you would need to extend it and customize it by yourself with a deep knowledge of Odoo internals and somehow re-make the activities widget and templates in the mail module
Related
I have been using Sitecore for a couple of years, and now looking to begin utilizing the Experience functionality found in Sitecore 8.
I have a view that will capture some user-provided data. How do I go about creating a "person" (don't know the correct Sitecore terminology) in the Analytics database from custom code.
You'll need to create a Contact. Contacts are a kind of profile store for xDb and allows you to store data about your visitors. A contact has a built in list of facets (email, phone number, name etc) that make up the contact record, but it's also possible to create your own facets.
If you are building a form to capture data you can use the new Tracker api to identify and update facets on a contact.
Here's some code to do this:
https://github.com/ianjohngraham/CoreBlimey.Utils/blob/master/CoreBlimey.Utils/xDB%20Contact%20Creator/CreateContact.aspx.cs
There's a walk through of how the code fits together here:
https://m.youtube.com/watch?v=Jq6TpMgUGAk
(Apologies for the sound quality)
Also if you are using the WFFM module in Sitecore 8 there are some new save actions that will create contacts and store xDB data.
You may want to spend time on the docs. Please refer here for articles and guides related to Personalization and Personas.
Most of the configuration can be specified in Experience Analytics within Sitecore and you can leverage Rules Engine to perform actions.
I'd like to create a tooltip bubbles for my site for new users - many other sites do this (most google apps). I'd like to show them for all accounts created within the last week, unless the user specifically 'dismisses' the tip.
I thought about doing this with cookies - ie. set a "-dismissed=True" value that I could check as well as the account creation date and determine whether to show the tips.
However - this doesn't work across browsers, since cookies aren't shared between browsers. So if a user logs into chrome, dismisses the tip then logs in in FF the tip will reappear.
Does anyone know if there is common way to do this sort of thing? Or at least a better way than what i've described?
I'm using browser length sessions so I can't store it in the session.
You could have a user preferences model, with a one-to-one relationship to the main user model, which stores preferences like this. Create an instance when the user entry itself is created, and default the 'show tips' field to True.
You could also use the new custom user model functionality in 1.5 to store this in the user model itself, but that seems like overkill here.
It's a fairly simple idea, but I'm not sure where I should start reading.
All I want to do is add an extra action to a model in the Django Admin.
For example, I have a basic client management system, in that I have models for Clients, Companies, and Invoices to keep track of who owes what. All I want to do is add an action or button that when used, pulls information from the Invoices, Clients, and possibly Companies and then puts that information into a PDF document.
Any suggestions?
You'll have to override your admin templates for each of your models to add a button => Overriding Admin Templates
To generate a PDF define a view that is called once your button is pressed. Make sure to set the right permissions for your admin users.
I'd like all my wordpress posts to be editable by all users, guests included.
does anybody know if this is possible?
I already tried all the "wiki" plugins but without success.
it's absolutely possible. However, there are certain step that require manual programming.
The step is:
create an edit page in non admin area
do the editing there (you can mimic admin's edit page or you just display the body only)
upon saving, you can, either create new user programmatically and assign that user as the editor (this, off course will require another table or another mechanism) or leave the editor as post's previous owner
I have a custom list created in Sharepoint 2007 and displayed by a content query web part.
I would like to
Show all items to general admin users except those items created by two users.
The two admin users need to see all items in the list.
The first requirement is easily done by adding a filter to the view on the created by field.
The second one is where I need help, is there a way to set the view of a list based on the user logged in to acheive the second requirement?
Or is this achievable another way?
Many Thanks,
Nav
If user has SPBasePermissions.ManageLists permissions, he will have permissions to view all items in the list.
If its not about permissions, but just which view which user sees by default, then it will involve some sort of coding :
Either you create webpart which will switch to desired view for desired user. (Involves coding, building, deploying)
Use content editor web part to switch with javascript - not that nice solution. (Because page would reload when you open it).
In the end I created two pages one called restricted and the other for all users configured the views on each page for each group of users. Then I restricted access to the 'restricted' page to the relevant users.
I used audiencing to display a link to the 'restricted' page to selected users