Business Rules
The Business Rules module is inspired on Rules module and allow site administrators to define conditionally actions execution based on events. It's based on variables and completely build for Drupal 8.
This module has a fully featured user interface to completely allow the site administrator to understand and create the site business rules.
It's also possible to extend it by creating new ReactsOn Events, Variables, Actions and Conditions via plugins.
Features
- Conditional event driven action execution
- If, then, else conditions
- Views result variable
- Loop action execution
- Custom form validations
- Custom form changes to make fields required, optional, read-only and hidden
- Dependent fields
- Explicity variables declaration
- Flowchat diagram to each business rule
- Extendable via plugins
- Full debug rule execution block
Project homepage
https://www.drupal.org/business_rules
Project documentation
https://www.drupal.org/docs/8/modules/business-rules
Similar projects
Rules
Although Business Rule's functionalities are very close Rules module, the main difference is that Business Rules is ready to be used on Drupal 8. This module was developed because of the need of use these functionalities in newer Drupal 8 projects. During the development of this module, we've also included some absent functionalities on Rules such as flowchart diagram, explicitly declared variables, views interaction and form change actions.
Git clone command
git clone --branch 8.x-1.x https://git.drupal.org/project/business_rules.git
cd business_rules
Comments
Comment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgprojectbusiness_rulesgit
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
yseki commentedThe remaining issues pointed by the automated review tools are not errors on the code.
1. /images/check.svg: ASCII text, with very long lines, with no line terminators
It's an SVG image, so that's no change needed.
2. The js errors pointed by ESLint related to non-used variables are not errors, but the external library initialization.
3. The two warnings pointed by Drupal Practice seems to be errors on the tool. It refers to a non-used private method that is currently being used and the prefix for the dependency at the info.yml file is just weird; I could not find any usage of this style at Drupal core.
4. The errors and warnings pointed by PAReview.sh are not in the code. Most of all are related to Equals sign not aligned that in fact are aligned in the code.
Comment #4
yseki commentedManual reviews added.
Comment #5
deepanker_bhalla commentedHi yuriseki,
Kindly see the automated review of your project as its showing some errors.
Link: https://pareview.sh/node/1621
Comment #6
yseki commentedHello deepanker_bhalla,
As I said in comment #3, those issues are false positive.
Thanks,
Yuri
Comment #7
PA robot commentedProject 1: https://www.drupal.org/node/2874030
Project 2: https://www.drupal.org/node/2869895
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #8
avpaderno