Thanks Laune and sorry for a bit delayed reply. Now, I got some more
information from you. I will experiment on this part with your suggestions
and see.
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-define-keywords-that-represent-objects-in-facts-to-be-able-to-use-in
Hello Laune,
Yes, we can use parameters in DSL phrases. But the
problem here is rule author doesn't know which object to refer.
And, can we translate a business rule with keywords
into DRL?
You can use "$ContactNum" from the DRL translation. It's not "h
Hello manstis,
can you please see my reply to Laune describing what
actually my requirement is and suggest something? And why i felt ever
#condition and #action needs to be in DSL configuration.
Here, the keyword is something like this "PersonMobileContact" -->
Object
Laune, the problem is when i define a keyword like i said above
"PersonMobileContact" for Object1($ContactNum : contactNumber && contacttype
== "mobile"). In business rule, i can use this keyword.
This is ok, but if i want to set this $ContactNum into another object
i.e. Object2. I thin
Hello Laune,
Yes, the Object and attribute names are meaningful but in
our case they are a bit lengthy and wanted to give rule author more
convinience in writing rules.
For example, when we need to write Object1($contactNo :
contactNumber && contacttype == "mobil
r this?
Or is there any option/feature we can proceed with? Please let me know.
Thanks in advance.
Regards
San_Drools
--
View this message in context:
http://drools.46999.n3.nabble.com/How-to-define-keywords-that-represent-objects-in-facts-to-be-able-to-use-in-rules-tp4019065.h
