CRM Check List and Approval Process
by faOtools https://faotools.com/apps/15.0/crm-check-list-and-approval-process-624$ 26.35
| Required Apps |
CRM (crm)
|
| Lines of code | 363 |
| Technical Name |
crm_checklist |
| License | See License tab |
| Website | https://faotools.com/apps/14.0/crm-check-list-and-approval-process-518 |
| Also available in version | v 15.0 v 13.0 v 8.0 v 12.0 v 10.0 v 11.0 v 9.0 |
| Required Apps |
CRM (crm)
|
| Lines of code | 363 |
| Technical Name |
crm_checklist |
| License | See License tab |
| Website | https://faotools.com/apps/14.0/crm-check-list-and-approval-process-518 |
| Also available in version | v 15.0 v 13.0 v 8.0 v 12.0 v 10.0 v 11.0 v 9.0 |
Making a customer from an opportunity is the only goal of CRM pipeline. To achieve that goal sales staff needs to undertake a specific sequence of actions. Each of those actions is important on a definite funnel stage. Efficient companies know that missing of any step might result in a long-run failure. This is an Odoo tool to make sure such a failure will not happen. The app provides a check list for each pipeline stage to control over requirements' fulfillment, and to make sure that each action is fully approved by responsible users.
Stage-specific CRM checklists
Check lists are assigned per each opportunity stage. For instance, actions for 'new' and 'proposition' stages might be different. Prepare any number of check points for each CRM stage
Actions ensured to be done
To move a CRM lead forward in your funnel, its check list should be fully confirmed ('moving forward' implies any change of stage with lesser to a bigger sequence). For certain stages - e.g. for 'Canceled' - you may want to avoid such restriction. Then, mark this stage as 'No need for checklist'
Highlighted opportunity progress
Fulfillment progress is shown on opportunities kanban and form views for instant overview
Approval history for managerial control
Check list actions are saved in history. If an opportunity is moved back, already done check items would be recovered. Turn on the setting 'not saved' to avoid that behavior for specific approval points
Multiple CRM check list roles
The app let assign security groups for each check list point. In such a case, only users from that groups would be able to confirm a related item
Super approval admins
The special role 'CRM Checklists Super User' allows (a) to confirm any check points disregarding defined security groups and (b) to move any opportunity further without fulfilling check lists.
Anybody who has access to stage settings can modify the value of check lists.
If set to "true", a lead/opportunity might be moved to this stage without fulfilling a check list. Usually used for "lost" stage, since it doesn't require any sort of extra actions. In such a case users can move any lead/opportunity to "lost" from any stage without doing anything (e.g. new > lost, proposition > lost).
If set to "false", a checklist of a current stage is required to be entered if moved to this stage (in case it is further through the pipeline). For example, "won" state requires certain actions. If you move a lead/opportunity from "proposition" to "won", you should confirm check points of the "proposition" stage. "False" is the default value for "no need for checklist" field.
When making a checklist you can choose the user groups for each checklist's statement. Only these user groups will be able to mark the statement as done. If someone else tries to mark the statement done, then the system will not let them save it and the warning will appear.
According to the current Odoo Apps Store policies:
- every module bought for the version 12.0 and prior gives you an access to the all versions up to 12.0.
- starting from the version 13.0, every version of the module should be purchased separately.
- disregarding the version, purchasing a tool grants you a right for all updates and bug fixes within a major version.
Take into account that faOtools team does not control those policies. By all questions please contact the Odoo Apps Store representatives directly.
The easiest approach is to use the Odoo store built-in workflow:
1. Open the module's page and click the button Deploy on odoo.sh
2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project
3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.
These steps would install the app for your project production branch. If you wanted to deploy the apps for other branches or update the module, you should undertake the following actions:
1. Upload the source code for the app from the Odoo store
2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions
3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.
Unzip source code of purchased tools in one of your Odoo add-ons directory
Re-start the Odoo server
Turn on the developer mode (technical settings)
Update the apps' list (the apps' menu)
Find the app and push the button 'Install'
Follow the guidelines on the app's page if those exist.
Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.
No, we distribute the tools only through the official Odoo apps store
Regretfully, we do not have a technical possibility to provide individual prices.
No, third party apps can not be used on Odoo Online.
Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.
Red / orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.
So, first of all, please check deployed database features. Does everything work correctly?
If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).
The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.
Opportunity check list per stages
Opportunity stage check lists
Check list to be confirmed before going further
Approval process distributed by various user roles
Opportunities check list progress kanban view
Opportunity check list tree view
The super rights to approve any check items and move opportunities
Odoo demonstration databases (live previews)
For this app, we might provide a free personalized demo database.
To demand such a database, press the button "Live Preview" on the top of this page or copy the link https://faotools.com/s/ghghei
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
By your request, we will prepare an individual live preview database, where you would be able to apply any tests and check assumptions for 14 days.
Bug reporting
In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.
To send us a bug report: press the "Website" link on the top of this page and push the button "Bug Report" (the tab Support). Alternatively, copy the link https://faotools.com/s/q9r36i
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
Please include in your request as many details as possible: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).
Public features requests and module ideas (free development)
We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those in our to-do list.
Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.
To share ideas: press the "Website" link on the top of this page and push the button "Share Features Ideas" (the tab Support). Alternatively, copy the link https://faotools.com/s/m0gw5m
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
Questions and misc issues
Feel free to contact us with any other concerns, doubts, or questions: press the "Website" link on the top of this page and push the button "Raise Question" (the tab Support). Alternatively, copy the link https://faotools.com/s/r2ciqg
About the team
faOtools (faotools.com, former odootools.com) is the team of developers and business analysts to help you extend Odoo's potential. We have been communicating with end users to whom the software became the main business tool since 2012. As a result, we are proud of dozens of successful Odoo apps developed. We are open for new ideas and challenges to create the best Odoo apps for business needs all over the world.
You may like the tools
The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS
The tool for time-based service management from booking appointment to sale and reviews
The tool to notify salespersons of topical activities by leads and opportunities
28
The tool for real-time control of customers' and opportunities' duplicates
The tool to calculate sale trends and make prediction for future sales statistically. Sales Forecast
198
The tool to make sure a sale order is ready for the next stage. Sale checklists
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module