Max length of Integer control

amarie

March 21, 2016 at 5:43 am #1531

It seems that the BPM Integer data type only allows around 10 digits (i.e. 1234567890).  The out of the box Integer control will clear the control if the value is over this digit limitation and prompts the user that the data is out of range.  The Spark Integer control allows the data to be submitted, but throws an error on submit.

Is there a plan to add the maximum restriction to the control like the out of the box control has?  Alternatively, is there an easy way to add this restriction to every Spark Integer control?

 

 

SPARK Support

March 21, 2016 at 8:29 am #1534

The character limitation appears to be a bug with the integer control. A bug has been filed and we will work on a fix as soon as possible. Thank you for bringing this to our attention.

 

Regards,

Salient Support

SPARK Support

March 21, 2016 at 10:27 am #1535

Hey Amarie,

Thanks for your question. I experienced the same error as you did, and this is a known bug by our development team. For now, to achieve what you need, you could use the Masked Text control. By applying a mask (in your case: ##########), the user will be prevented from entering more than 10 numbers. It is important to note that the Masked Text returns a String data type, and this will need to be converted to an integer.

Hope this helps,

Elliot

amarie

March 21, 2016 at 10:51 am #1536

Thank you for your suggestion, we may try to implement that.

Along these lines, we also noticed that when a relatively long integer value (12345678901234567000) was typed into the Integer control, the value would change when we clicked off the control.

I’m assuming these issues are related.

SPARK Support

March 21, 2016 at 12:48 pm #1541

For the record.  There is a bug here which we will address in that we allow the service to fail.   The bottom line however is that the type of integer is limited to what fits in a 32-bit signed integer, so the minimum value is -2147483648 and the maximum value is 2147483647.  So not even all 10 digit values are valid.  Another workaround would be to bind the Integer control to a variable of type decimal.  Note that to do this when you bind the control you will have to remove the check from the “Show matching variables only” checkbox, AND this will give you a warning in Process Designer, but that warning can be safely ignored.

Regards

John