Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
slmetro

Member
Registered:
Posts: 18
Reply with quote  #1 
We have a requirement to allow 2 decimal places within a variable we had previously defined as "Integer".  So, our previous entries of 1 or 2, now need to be able to save as either a whole number or integer, like 1.00 or 1.50.

When you add a new integer field to a form, the options tab lists a decimal places setting, but once you associate the field with a variable (from Calculated), the decimal places option becomes inactive - the help documentation is consistent and states it will be inactive if using a variable.  Even though it allows you to enter the value as ex. 1.25, it rounds upon save as 1.00.

It seems like such a simple task, but we are stuck.  Has anyone had experience with integers and decimal places?  I really do not want to change this to a text field, but cannot figure out how else to be able to enter and save a decimal in Metastorm.

Attached demo.

Thanks!

 
Attached Files
xep Decimal_Test.xep (1.54 KB, 2 views)

0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #2 
while associated with na int variable it behaves like this. You jut need to associate it with a real variable, ie floating point. Then set the dec places.

Easiest way is to create a new fp variable.

You can change the existing variable to a fp field by updating the database manually, then droppting it in the designer and adding it as fp. You will lose association with fields, which can cause interesting issues due to the default field usage setting changing to readonly.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
slmetro

Member
Registered:
Posts: 18
Reply with quote  #3 
Thanks Jerome, you are spot on (as usual!).  I got tripped up in the backend making the change to REAL, but it needed to be FLOAT.

I deleted and readded the variable as REAL in Metastorm, re-associated with the fields, set their default setting etc.  Then forced a sql update of the column to FLOAT. 

Cheers!
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!