Bionic rule to rule chain?

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:

• 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).

For me, (at least with Cisco), this leaves my primary use case as Export to S3 - very much needed and welcome, and I'll be dumping lots of data on schedule soon.

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.

Hope that helps the case for prioritization!

You can add the bionic rules into rule chain from summer release.

Summer Release is out now and this feature is shipped.