Can't we have a Bionic rule to be part of rule chain?
Page 1 / 1
Not today. This is on the roadmap.
Can't stress enough how critical this is to make Bionic rules truly viable at Jupiter level -- particularly for those already implemented and doing a lot of processing.
In many cases, we (SAs) use rule chains heavily for these implementations - it's a great feature.
The problem is that, although there are cases where I could apply a bionic rule and replace 5 or 6 rules in the middle of a chain that's pivoting data, I can't make that change in a scalable way:
Adoption for day-to-day usage will be minimal at Cisco, though, until we can either:
In many cases, we (SAs) use rule chains heavily for these implementations - it's a great feature.
The problem is that, although there are cases where I could apply a bionic rule and replace 5 or 6 rules in the middle of a chain that's pivoting data, I can't make that change in a scalable way:
- I'd have to leave the first few rules of the chain scheduled at "x" time, followed by
- A separately-scheduled bionic rule, then
- the end of my chain scheduled a 1/2-hour later (minimum space between chains).
Adoption for day-to-day usage will be minimal at Cisco, though, until we can either:
- work bionic rules into existing rule chains, or
- have some 'Unified Scheduler' UI where I can consecutively schedule, and then see the full schedule, across both rule types.
You can add the bionic rules into rule chain from summer release.
Summer Release is out now and this feature is shipped.
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.