Timer Does Not Run Based on the Elapsed Time of the Relative Date Attribute (Doc ID 2103679.1)

Last updated on FEBRUARY 11, 2016

Applies to:

Oracle BigMachines CPQ Cloud Service - Version 11.0 and later
Information in this document applies to any platform.

Symptoms

Use Case: Timer in a particular step is running immediately after the quote transitions to that step. However, the Timer should run 10 minutes after the relative date attribute. For example, the referenced date attribute used in Timer is called "modifiedDate_quote". This date attribute is given a value by the "Create Order" action.

  1. User clicks Create Order which transitions the quote from Pending to Order Created step.
  2. modifiedDate_quote is updated with a new value by Create Order action.
  3. In the Order Created step, there is a Timer that will run 10 minutes after modifiedDate_quote (note that date attributes also stores time).
  4. Timer runs immediately after the quote transitions to Order Created, ignoring the Timer setting of the elapsed time relative to the said attribute.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms