Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.3.1
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-1819Move rules and expression implementations out of routetemplate package
      KULRICE-10887Allow for navigation items to be hidden based on an expression
      KULRICE-1664Generalize KRA meta-rule implementation
      KULRICE-11583Key Value should allow expressions in their key and value content
      KULRICE-8242decrease log noise with BSF rule expression exceptions
      KULRICE-10395Allow for disabled expressions to be partially evaluated server side
      KULRICE-10053ParentLocation no longer works - cannot evaluate expression
      KULRICE-11584Allow required to use expressions (like disabled)
      KULRICE-1396Add DDL for rule expression enhancements to upgrade script
      KULRICE-6424Complete JavaDocs for functional areas: Actions, Rules, Propositions & Expressions
    • Rice Module:
      KEW
    • Application Requirement:
      KC
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I am developing a workflow rule using Groovy, and I ran across a seemingly arbitrary limitation that my rule expression can not be longer than 4096 characters (LongStringType.) Please remove this restriction.

        Activity

        Hide
        Ken Geis added a comment -

        I see that rule expressions are saved in a database column that does not handle long text. This is unfortunate. In the Rice Oracle installation, it is defined as VARCHAR2(4000), the longest possible VARCHAR2. So if you have an expression that is longer than 4000 characters but shorter than 4096 characters, you get this error:

        java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column

        Show
        Ken Geis added a comment - I see that rule expressions are saved in a database column that does not handle long text. This is unfortunate. In the Rice Oracle installation, it is defined as VARCHAR2(4000), the longest possible VARCHAR2. So if you have an expression that is longer than 4000 characters but shorter than 4096 characters, you get this error: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column

          People

          • Assignee:
            Unassigned
            Reporter:
            Ken Geis
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel