2012-08-03 15:46:41 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<openerp >
[REF] document_page: refactored the module, towards using it in website_blog
Main modifications:
- category is now a blog.catory object, instead of a document.page with type='category'
- added blog.tag model, to be able to tag posts
- cleaned document.page, now blog.post model, removing type and unnecessary features
- added chatter on blog.post, blog.category
- added subtypes to enable direct follow of posts when following a category
- updated document.page.history (now blog.post.history)
- commented menu creation, because this does not seem to be necessary anymore considering the new website
- updated wizard.document.page.history.show_diff, now blog.post.history.show_diff
- updated all views accordingly, as well as demo data
- removed the use of document_user group, simplified rules on blog.post (not done for new models)
- misc cleaning
Next step: merge with website_mail
bzr revid: tde@openerp.com-20130920111221-qy3x5eoyih26axn8
2013-09-20 11:12:21 +00:00
<!-- <data noupdate="1"> -->
<data >
<!-- TAGS -->
<record id= "blog_tag_1" model= "blog.tag" >
<field name= "name" > functional</field>
</record>
<record id= "blog_tag_2" model= "blog.tag" >
<field name= "name" > pos</field>
2012-08-11 18:34:44 +00:00
</record>
[REF] document_page: refactored the module, towards using it in website_blog
Main modifications:
- category is now a blog.catory object, instead of a document.page with type='category'
- added blog.tag model, to be able to tag posts
- cleaned document.page, now blog.post model, removing type and unnecessary features
- added chatter on blog.post, blog.category
- added subtypes to enable direct follow of posts when following a category
- updated document.page.history (now blog.post.history)
- commented menu creation, because this does not seem to be necessary anymore considering the new website
- updated wizard.document.page.history.show_diff, now blog.post.history.show_diff
- updated all views accordingly, as well as demo data
- removed the use of document_user group, simplified rules on blog.post (not done for new models)
- misc cleaning
Next step: merge with website_mail
bzr revid: tde@openerp.com-20130920111221-qy3x5eoyih26axn8
2013-09-20 11:12:21 +00:00
<!-- POSTS -->
<record id= "blog_post_1" model= "blog.post" >
<field name= "name" > OpenERP 7.0 Functional Demo</field>
<field name= "category_id" ref= "blog_category_1" />
<field name= "tag_ids" eval= "[(6, 0, [ref('blog_tag_1')])]" />
2012-08-11 18:34:44 +00:00
<field name= "content" >
2012-09-10 14:20:35 +00:00
< ![CDATA[
<br >
<br >
The news is out, OpenERP's latest version 6.1. is here. It's more<br >
user-friendly, even more business oriented and efficient to manage your company<br >
<br >
How to discover the latest version 6.1.?<br >
<br >
Demo : <a target= "http://demo.openerp.com" href= "http://demo.openerp.com" style= "background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAFZJREFUeF59z4EJADEIQ1F36k7u5E7ZKXeUQPACJ3wK7UNokVxVk9kHnQH7bY9hbDyDhNXgjpRLqFlo4M2GgfyJHhjq8V4agfrgPQX3JtJQGbofmCHgA/nAKks+JAjFAAAAAElFTkSuQmCC") no-repeat scroll right center transparent;padding-right: 13px;" > </a> <br >
Online: <a target= "http://openerp.com/online" href= "http://openerp.com/online" style= "background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAFZJREFUeF59z4EJADEIQ1F36k7u5E7ZKXeUQPACJ3wK7UNokVxVk9kHnQH7bY9hbDyDhNXgjpRLqFlo4M2GgfyJHhjq8V4agfrgPQX3JtJQGbofmCHgA/nAKks+JAjFAAAAAElFTkSuQmCC") no-repeat scroll right center transparent;padding-right: 13px;" > </a> <br >
Download: <a target= "http://openerp.com/downloads" href= "http://openerp.com/downloads" style= "background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAFZJREFUeF59z4EJADEIQ1F36k7u5E7ZKXeUQPACJ3wK7UNokVxVk9kHnQH7bY9hbDyDhNXgjpRLqFlo4M2GgfyJHhjq8V4agfrgPQX3JtJQGbofmCHgA/nAKks+JAjFAAAAAElFTkSuQmCC") no-repeat scroll right center transparent;padding-right: 13px;" > </a> <br >
<br >
We have also put together a functional demo that presents 6.1. Watch this video<br >
to learn directly from us what OpenERP 6.1. can do for you. Share it in your<br >
company, with your clients and implement it now for your business.<br >
<br >
<h3 > Watch on Youtube!</h3> <br >
<br >
<iframe width= "480" height= "390" src= "http://www.youtube.com/embed/7jES2jxKMso " frameborder= "0" allowfullscreen= "" > </iframe> <br >
<br >
<br >
]]>
2012-08-03 15:46:41 +00:00
</field>
2012-08-11 18:34:44 +00:00
</record>
2012-08-03 15:46:41 +00:00
[REF] document_page: refactored the module, towards using it in website_blog
Main modifications:
- category is now a blog.catory object, instead of a document.page with type='category'
- added blog.tag model, to be able to tag posts
- cleaned document.page, now blog.post model, removing type and unnecessary features
- added chatter on blog.post, blog.category
- added subtypes to enable direct follow of posts when following a category
- updated document.page.history (now blog.post.history)
- commented menu creation, because this does not seem to be necessary anymore considering the new website
- updated wizard.document.page.history.show_diff, now blog.post.history.show_diff
- updated all views accordingly, as well as demo data
- removed the use of document_user group, simplified rules on blog.post (not done for new models)
- misc cleaning
Next step: merge with website_mail
bzr revid: tde@openerp.com-20130920111221-qy3x5eoyih26axn8
2013-09-20 11:12:21 +00:00
<record id= "blog_post_2" model= "blog.post" >
2012-08-03 15:46:41 +00:00
<field name= "name" > Personalise Dashboards</field>
[REF] document_page: refactored the module, towards using it in website_blog
Main modifications:
- category is now a blog.catory object, instead of a document.page with type='category'
- added blog.tag model, to be able to tag posts
- cleaned document.page, now blog.post model, removing type and unnecessary features
- added chatter on blog.post, blog.category
- added subtypes to enable direct follow of posts when following a category
- updated document.page.history (now blog.post.history)
- commented menu creation, because this does not seem to be necessary anymore considering the new website
- updated wizard.document.page.history.show_diff, now blog.post.history.show_diff
- updated all views accordingly, as well as demo data
- removed the use of document_user group, simplified rules on blog.post (not done for new models)
- misc cleaning
Next step: merge with website_mail
bzr revid: tde@openerp.com-20130920111221-qy3x5eoyih26axn8
2013-09-20 11:12:21 +00:00
<field name= "category_id" ref= "blog_category_1" />
2012-08-11 18:34:44 +00:00
<field name= "content" >
2012-09-10 14:20:35 +00:00
< ![CDATA[
<br >
You like OpenERP, but feel like you want to personalise it more? Now, OpenERP<br >
goes a step further and lets you customize your dashboard. Thanks to a new<br >
feature that allows you to customize your dashboard by adding new boards of any<br >
search view.<br >
<br >
<h3 > How is it done?</h3> <br >
<br >
Step 1: access one search view <br >
<br >
Step 2: apply the filter you want to see at each connection to the application<br >
(eg. on sales, manufacturing, etc)<br >
<br >
Step 3: add it into the dashboard in the same space where you can save the filter<br >
<br >
Step 4: choose the application you want it visible on and the name of the array<br >
<br >
Look at this simple example below from Purchase, where I want to put on the<br >
application's dashboard "Purchases to Approve". After I access the search view<br >
and apply the filter for "Purchases to Approve", I can add it immediately to my<br >
Purchase dashboard.<br >
<br >
<img src= "http://www.openerp.com/sites/default/files/fileattach/dashboard2_1(1).png" alt= "" > <br >
<br >
In less than a minute, the search view is visible on the dashboard<br >
<br >
<img src= "http://www.openerp.com/sites/default/files/fileattach/dashboard2_2.png" alt= "" > <br >
<br >
Of course, you are free to delete what you don't need or like, but just in case<br >
you change your mind there is a reset button to return to the default view.<br >
<br >
<br >
]]>
2012-08-03 15:46:41 +00:00
</field>
2012-08-11 18:34:44 +00:00
</record>
2012-08-03 15:46:41 +00:00
[REF] document_page: refactored the module, towards using it in website_blog
Main modifications:
- category is now a blog.catory object, instead of a document.page with type='category'
- added blog.tag model, to be able to tag posts
- cleaned document.page, now blog.post model, removing type and unnecessary features
- added chatter on blog.post, blog.category
- added subtypes to enable direct follow of posts when following a category
- updated document.page.history (now blog.post.history)
- commented menu creation, because this does not seem to be necessary anymore considering the new website
- updated wizard.document.page.history.show_diff, now blog.post.history.show_diff
- updated all views accordingly, as well as demo data
- removed the use of document_user group, simplified rules on blog.post (not done for new models)
- misc cleaning
Next step: merge with website_mail
bzr revid: tde@openerp.com-20130920111221-qy3x5eoyih26axn8
2013-09-20 11:12:21 +00:00
<record id= "blog_post_3" model= "blog.post" >
2012-08-03 15:46:41 +00:00
<field name= "name" > Touchscreen Point of Sale</field>
[REF] document_page: refactored the module, towards using it in website_blog
Main modifications:
- category is now a blog.catory object, instead of a document.page with type='category'
- added blog.tag model, to be able to tag posts
- cleaned document.page, now blog.post model, removing type and unnecessary features
- added chatter on blog.post, blog.category
- added subtypes to enable direct follow of posts when following a category
- updated document.page.history (now blog.post.history)
- commented menu creation, because this does not seem to be necessary anymore considering the new website
- updated wizard.document.page.history.show_diff, now blog.post.history.show_diff
- updated all views accordingly, as well as demo data
- removed the use of document_user group, simplified rules on blog.post (not done for new models)
- misc cleaning
Next step: merge with website_mail
bzr revid: tde@openerp.com-20130920111221-qy3x5eoyih26axn8
2013-09-20 11:12:21 +00:00
<field name= "category_id" ref= "blog_category_1" />
<field name= "tag_ids" eval= "[(6, 0, [ref('blog_tag_1'), ref('blog_tag_2')])]" />
2012-08-11 18:34:44 +00:00
<field name= "content" >
2012-09-10 14:20:35 +00:00
< ![CDATA[
<br >
The brand new OpenERP touchscreen point of sale available with 6.1 allows you<br >
to manage your shop sales very easily. It's fully web based so that you don't<br >
have to install or deploy any software and all the sales shops can be easily<br >
consolidated. It works in connected and disconnected modes so that you can<br >
continue to sell if you lose your internet connection.<br >
<br >
<img src= "http://www.openerp.com/sites/default/files/fileattach/POS(2).png" alt= "" > <br >
<br >
<h3 > Here's a summary of its main features and benefits:</h3> <br >
<br >
100% WEB based<br >
<br >
<ul > <li > available for any touchscreen device (ipod, ipad, any tablet)mobile (with portable devices)</li> <li > no installation required</li> <li > no synchronization needed, completely integrated</li> <li > continue working even when your connection is down if you close your browser, data won't be lost</li> <li > fully web based with a clean interface smart interface</li> </ul> <br >
<br >
You have different options to select your products. You can do it through the<br >
barcode reader, just browse through the categories you have put in place (ie.<br >
drinks, snacks, meals, etc.), or text search in case neither of the other<br >
options work for you. If you need to use the POS for your restaurant, for<br >
example, your employees can record at the same time multiple tickets without<br >
having to wait to do one transaction at a time. Along, to facilitate payment,<br >
the application allows multiple payment methods.<br >
<br >
The POS application is so simple and accessible to use that your shop or<br >
restaurant will never need any other tool to manage orders. Due to its smart<br >
and user-friendly interface you don't need any training to learn how to use it.<br >
Think of it as an out-of-the-box solution to boost your business' productivity.<br >
<br >
]]>
2012-08-11 18:34:44 +00:00
</field>
</record>
2012-08-03 15:46:41 +00:00
</data>
2012-08-10 00:09:08 +00:00
</openerp>