You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Run a database refresh embedded in a rule from a Pipeline

in Planning 1 comment

I believe similar questions have come up but haven't seen a straight answer for this use case. I have a groovy business rule that performs this high level sequence:

  1. Conditionally adds members to a dimension (based on grid data)
  2. Runs a db refresh
  3. Runs calc script with RTP's who's values are based on members returned from the grid in step 1

Running this as a native rule is not an issue. However, running the rule from a pipeline doesn't work because it exits with a "cancelled" status( due to the "Stop all active requests" flag that must be set).

Has anyone found a workaround to handle this type of situation? I know I can split the process up into 3 distinct rules so that the refresh step doesn't conflict with the overall execution but I'd prefer not to do that.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!