Skip to main content
Discovery

Bionic Rule Record Flagging

Related products:CS Rules Engine
  • March 28, 2017
  • 1 reply
  • 22 views
tony_tao
  • tony_tao
    tony_tao

wayne_baker
One of the goals for bionic rules is to cut down on the amount of rules needed to run actions.

I am attempting to set multiple scorecard measures from the same data source but running into an issue.

Setup:

The same source will be used to set scores for three different measures. Each scorecard measure is based off different Data fields. In one bionic rule fetch I have 16 different possible filters, utilizing advance logic such as, (A or B or C) AND (D or E or F) AND etc.

My goal was to source the same object twice and then merge. However, I would need to retain records from both in order to get the result I need. This would effectively set the score wrong for one of the other scorecard measures as the 'relationship id' will exist for all the actions and I do not have the ability to apply action criteria's as there is the case of 'OR' logic.

This sparked an idea, the ability to be able to flag a record in a fetch job. Essentially creating a temporary field that gives you a field to mark true for that record from that task. Then in the next task you can setup another field to be marked true. This would be able to give someone the ability to flag a record if there are 'or' conditions or they are needing to use the same source to do different things/set different scores. This way all an admin needs to do is apply the criteria where that temporary field = true.

I.E.
Fetch source 1 that meet certain conditions - Mark task 1 boolean field as true
Fetch source 2(The exact same source) that meet certain conditions - Mark task 2 boolean field a true
Merge data on common id to reduce amount of records, this merge dataset now has both those boolean fields that are true and false on the same row

Action 1 set score if Task 1 boolean = true
Action 2 set score if Task 2 boolean = true

1 reply

jitin_mehndiratta
Hi Wayne,

The "OR" condition in Action filters is on the roadmap and is most likely to be shipped with fall release. This will help to solve your problem.
I will keep you posted on this.

Regards,
Jitin

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings