How to create Guided Decision Table in Drools

1. Create new project UPLOAD <project-name>.

2. Add data object asset (e.g., upload).


3. Add asset Guided Decision Table using “Add asset” option from home page.

4. Enter GDT name, choose package and select an option from Hit Policy drop down. You can select from any of the listed policies based on the requirement. In this example, we are using First Hit.


5. Click OK button, then you will see the GDT as below.


6. Insert columns by clicking on Columns tab, there will be a popup window as below.


7. We should configure the mentioned options as in below screenshot.


7.1 New Column:

Add a condition -> next ->

7.2 Pattern:


Then click on create a new fact pattern button, it will show a new popup.


We must provide the Binding value and click Next.


7.3 Calculation type:

Select literal value radio button and click next.

You can select other options based on your requirement.


7.4 Field:

Choose field value from dropdown and Binding is optional.


7.5 Operator:

Choose equal to option from drop down and then next


7.6 Value options:

Here we can provide multiple options with comma separate in value list. Then it will show in Default tab in drop value like below.


I have given gold and diamond; it is showing same in drop down. Then click next.

7.7 Additional Info:

Header filed is mandatory filed and click finish button.

Picture148.Below is the table structure.


9. Here we can add rows using Append row under insert button drop down.


10. We can add multiple rows using same option. And if we double click on gold tab it shows list of options which are, we added in previous steps.


11. Do not forget save.


12. Using above steps, we can add multiple columns as per our requirement.

13. Here adding one more column action.

14. Click on insert tab and choose insert column.


15. Select set the value of a field and click on next.


16. Choose upload[auto] pattern by clicking dropdown of pattern filed and then click next.


17. Select discount filed from field dropdown.


18. Provide optional values then it will show in drop down like below.


19. Given Header description as Action and click Finish.


20. Below is the GDT final structure.


21. Click on save button and then click on validate button and it should be successfully validated.


Use Test Scenario Asset for testing instead of POSTMAN:

1. Once deployment got completed, add Test Scenario Asset using add asset option.

2. Below is the normal Test Scenario Asset.


3. We provided condition and action details below.


4. Then start testing using play option and the response is like below.


5. If something is wrong, it will show like below.



CI/CD Email Alert Configuration on Specific File Change


A notification has to be sent to the developer who made a commit to a configuration file, such that the retrofit of the file to the other repos would not be missed and there by avoid issues upfront. At present in git there is a feature for notification by using the “GIT Integrator service call email on push”. However, this service is not able to restrict the mail notification to a particular file change which is creating the issue as the inboxes are flooded with emails for every check-in.

Steps to achieve

  • To configure an email notification for any specific file changes during git commit, we can use git tag “only”. Following is an example for the git script which is used for the same.

send_email: —-Git Stage

  stage: notify

  only: —-Git Command Only


      – sb/temp/azu/*.prop


    – echo `git log -p -2 *.prop | head -50 > commit_history.txt`

    – |

      if [[ -z “$REPO”]]; then

         curl -s –user “api:$API_KEY” “$DOMAIN/messages” -F from=’Gitlab <>’ -F to=$GITLAB_USER_EMAIL -F to=$GITLAB_USER_TLD -F to=$GITLAB_USER_NLD -F cc=$GITLAB_USER_TWO -F cc=$GITLAB_USER_PM -F subject=’Gate Property file Modified’ -F text=’Retrofit property files to other Repos’ -F attachment=’@commit_history.txt’


         echo “It’s not allowed to trigger”


  • In the above yml code snippet, it’s the “only” tag where we have condition for the execution of the script. Whenever there is a change in the property files then immediately it recognizes the change and triggers this job.
  • An Email is sent using the mail gun service provider for the particular property file change. Without having our own SMTP Service provider, we can create an account in the Mail gun, it provides an API which can be hit with the required parameter such that it does the job of sending notification for us. It’s a pretty cool feature and easy to use. The service is ‘Free’ for a couple of months that is accompained with 5000 emails per month.
  • Sample curl command to hit the email API:

curl -s –user “api:$API_KEY” “$DOMAIN/messages” -F from=’Gitlab < >’ -F to=$GITLAB_USER_EMAIL -F to=$GITLAB_USER_TLD -F to=$GITLAB_USER_NLD -F cc=$GITLAB_USER_TWO -F cc=$GITLAB_USER_PM -F subject=’Property file Modified’ -F text=’Retrofit property files to other Repos’ -F attachment=’@commit_history.txt’

  • Private Key and service domain from Mailgun are required to put them in yml. Below steps help us to find the following things from mail gun.
  • Create an account with mail gun using the below link:

1.  (Don’t click on the Add payment info now, we can sign up to the site without credit/debit card details.)

2. Provide all the sign-up details like email and name

3. Once login you will be able to see the below screen:


4. Once login you will be able to see the below screen:


5. Click on the domain then you will be able to see the domain name, also, in the right side we will have the recipients where we have to add the mail id of the person to whom the notification should be sent, currently, using free account we can only send it to 5 people.


6. Click on the setting and then API keys to get the private key:


7. All the variables are given in the GITLAB-UI under settings/ci-cd/variables as a global part.


  • We can also use the smtp parameters instead of the API: sample for the same is below:

./swaks –auth \

        –server \

        –au \

        –ap 583627bfa8d4a292c4aa779f9b61aafb-ba042922-a9cb1219 \

        –to \

        –h-Subject: “Alert!!! Property file changed” \

        –body ‘check the commits’



Custom Library

To perform custom manipulations and logic in a process and to accomplish unique and advanced requirements that fail outside of the native functionality of the Boomi platform, Custom scripting is been written. Such integrations need custom files, a thirdparty custom scripting libraries or specific libraries for connectors. 

Custom Library components are collections of Java Archive (JAR) files that you can use to support those in Boomi integration processes. 

Creating and deploying Custom Library components enables you to manage JAR files through the Boomi Integration UI. You can deploy Custom Library components to any Atom, Molecule, Atom Cloud, or environment. 

To configure the custom library in atom management below are the steps: 

Upload external libraries to the Boomi account:

Setting>Account details>manage Account libraries>upload a JAR file. 

Create a custom library component in Boomi: 

In custom librarytype in Boomi, we have three types of components: General, Scripting and Connector. 

Click on create new Custom Library Component from the process and in the configuration tab, define Custom library, Component Name, and Folder and click on create. Once you create a component in dropdown list select the library we want to create, if we select customer library type as a connector, we have to provide connector type and we can add JAR files from the previously uploaded custom JAR files and click on save. 


Deployment of the custom library component: 

To Deploy the Custom library: Create Package component with all details and create it. 

Once all package components successfully created, click on the Attachments tab to attach environment and version and click on Deployment tab to deploy the component. 

Restart Atom: 

Before you can use the library in your integration process, we will need to restart the atom. Manage > Atom Management > 

Select an atom > click on Atom information tab > click on “Restart Atom”. 

 Removing files from a custom library: 

You can remove custom JAR files from a Custom Library component, but you should not do so if the component is currently deployed. 

Custom library component > Select Jar File > Delete > Save. 

 Migrating existing JAR files to use custom libraries: 

Existing JAR files that were placed in user library folders manually continue to work as they did before the introduction of Custom Library components. However, as a best practice, Boomi recommends that you migrate any manually deployed JAR files to custom libraries that can be managed through the Boomi Integration UI. 

To make existing JAR files known to Boomi Integration, follow the normal custom library deployment flow: 

 Upload JAR file > Create Custom library component > Deploy. 

 When the JAR files are deployed, Boomi Integration checks for existing files of the same name: 

  • If the file name and the contents of the file are the same, the file is not replaced. 
  • If the file name is the same but the contents are different, the new JAR file is deployed with a unique suffix to avoid a naming conflict. The existing file is marked for deletion. 

In either case, the JAR file is now recognized by the Boomi Integration and can be managed through the UI.