Task Check List and Approval Process v.8
The tool to make sure required jobs are carefully done on this task stage
Check lists are assigned per each task stage. Set of check list points is up to you
As soon as a task is moved to a certain stage, its check list is updated to a topical one from this stage. For example, actions for 'draft' and 'in progress' stages should be different, shouldn't they?
To move a task forward through your project pipeline, a check list should be fully confirmed. By 'moving forward' any change of stage with lesser sequence to a bigger sequence is implied
Confirmation might assume involvement of different user roles. Certain check list points might be approved only by top-level employees. For example, cost calculations are confirmed by Financial managers. In such a case just assign a user group for this check list item
For certain situations you do not need a check list fulfilment even a new stage is further. For example, for the 'Cancelled' stage. In such a case just mark this stage as 'No need for checklist'
Frequently Asked Questions about Task Check List and Approval Process Odoo v.8
If set to "true", a task might be moved to this stage without fulfilling a check list. Usually used for "cancelled" stage, since cancelling doesn't need any sort of extra actions. In such a case users can move any task to "cancelled" from any stage without doing anything (e.g. new > cancelled, in progress > cancelled).
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, "done" state requires certain actions. If you move a task from "under approval" to "done", you should confirm check points of the "under approval" stage. "False" is the default value for "no need for checklist" field.
Anybody who has access to stage settings can modify the value of check lists.
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.
Please, make sure, that your user hasn’t "Task Checklist Super User" rights. As they allow to confirm any checkpoints disregarding chosen security groups and to move any task further without fulfilling any of them.
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.
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).
In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes during 60 days after a purchase, while even after this period we are strongly interested to improve our tools.
Please include in your request as many details as possible: screen shots, Odoo server logs, full description of how to re-produce your problem, and so on. Usually it takes a few business days to prepare a working plan by an issue (if a bug is confirmed) or provide you with guidelines what should be done (otherwise).
Public features request 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 into our to-do list.
Such to-do list is processed on a regular basis and does not assume extra fees. Altough we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.
New features and extra Odoo services (individual development)
Each of our apps might be customized and extended to suit your specific requirements.
Our customization team fulfills not only such jobs but it also provides a full range of Odoo services. From simple modifications and consultations to complex enterprise projects. The team has completed over 100 implementations since 2012, and might help with any technical or business needs.
The tool to quickly access and simply reference tasks by automatic numbers
The tool to add new fields for Odoo projects without any technical knowledge38€
The tool to add new fields for Odoo project tasks without any technical knowledge38€
The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS298€
The core for Odoo integration with cloud file systems (ownCloud, Dropbox, Onedrive, etc.)245€
Manage Odoo documents in OwnCloud/NextCloud (bilateral sync)
The tool to automatically synchronize Odoo attachments with Google Drive files in both ways