Cron Syntax in timer boundary events and timer intermediary catch events Causing Parse Error.

Solution Verified - Updated -

Issue

  • Intermediate Timer Events with the “Cron” syntax option selected and a Time Cycle of “0/1 * * * * ?” throw a syntax parse error at build time.As a workaround, we assigned the cron string to a process variable “cronStr”, and set the Time Cycle to #{cronStr}. The build compiles, but throws the same syntax parse error at runtime.

Environment

  • BPMS 6.0.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In