Hello.
Indeed, I have tested with the @expires and the objects are discarded in
this case. What I had understood in the documentation is precisely the other
way that the engine is expected to control the events expiration : "Inferred
Expiration" (8.8.2), when no temporal constraint involves the obj
Hello.
Indeed, I have tested with the @expires and the objects are discarded in
this case. What I had understood in the documentation is precisely the
other way that the engine is expected to control the events expiration :
"Inferred Expiration" (8.8.2), when no temporal constraint involves the
I think that if you want the automatic event lifecycle management to delete
your events, you first need to notify the engine when an event is old enough
to realise it should be removed. This has to be managed adding the @expires
annotation to the event declaration:
declare Notification
@role( e
Hi David,
sorry but it's impossible for us to figure out what's going wrong in your
case just looking at the stack trace you sent. Have you been able to
consistently reproduce this problem? If so could you open a ticket on jira
and share your reproducer there?
Thanks,
Mario
--
View this messag
Roles assigned to repositories or OUs are on top of the application roles
(admin, user, developer, analyst, etc) so to be able to logon to kie-wb you’ll
need to have one of the application roles and then roles specific to repository
and/or OU.
There is a mechanism to map different application r
Click on the pencil icon and choose the value type (literal, formula etc).
The red error indicator should then disappear.
On 25 August 2014 20:14, rsureshbe wrote:
> We have bought BRMS 6 from JBOSS recently. Currently configuring an BRMS
> rules setup in DEV and INT, encountering an issue wit
