Creating a Constant

AFAIK,you cannot create constant dynamically from process model.You can update value of a constant using Update constant smart service.

May I know what is the use of creating the constant dynamically, instead write the data into the database, as the number of constants also keeps on increasing per instance.

What is your use case here? What if you save your data in the database for future reference? Alternately, if you know the result of process instance (like status, milestone etc), you can have one array constant created which will be used/checked against process instance output.

Also, creating a constant through each process instance is not a good approach all together. Please review your use case & provide more information here. thanks.

I am not trying to use this dynamic functionality in regular process models. We have to create more than 3000 constants as per requirement. So instead of creating manually, I am searching for an alternative way through one time use process model.

Ok, so, even if you find a way of creating these many constants, it will be very difficult to track & maintain these constants in future. One suggestion would be - can you check if you can sort and put values of similar data types into one constant? It will be easy for you to maintain, track & update the constants. Let us know your findings & final approach.

I agree with Durgesh. What's the use case for creating 3000 constants? This does not seem to be a typical "best practices" implementation, but if you clarify the use case, we could potentially provide other, more effective alternatives.

We are looking for maintain internationalization for labels through constants. what could be the best way to handle multiple languages for same label based on locale of loggedinuser()?

We want to create constant for each label like below example in attachment.

Did you get a way to create these many constants (with dynamic values based on the multi language)? Can you share your experience.

Rather than creating a constant you can store all the details into the database table and the data type should be NVARCHAR, so that the Unicode characters can store directly into the database table

Have you reviewed the Application Internationalization documentation here?

docs.appian.com/.../Application_Internationalization.html