How to Create a property dynamically on run time?
Is it possible to create new property while the case progresses.....the property should be created by the end users
Accepted Solution
Pegasystems Inc.
GB
rawap's answer is better; but here's something that might also help.
WARNING: This solution was reversed-engineered and I can't really say that this is doing the correct thing here (although it works in terms of what it sets out to do): so 'buyer-beware' here - and I welcome input on how to get this to work properly. (See below for a specific issue with this!)
This will create a series of Properties automatically: actually from the Designer Studio (rather than what you asked for): we put this together as a way of setting up a test where we needed a load of properties.
So: basically this just creates instances of 'Rule-Obj-Property' - using the default Data Transform 'Rule-Obj-Property.pyDefault' to set up most of the required settings (that is, Properties of Rule-Obj-Property - this is all a bit 'meta'); and then tweaking these meta-properties for our needs.
So first stage: create a data-transform in an open ruleset - but save-it to 'Rule-Obj-Property' ; make sure it calls the OOTB 'pyDefault' as a first step:
Note that here we are hardcoding classes and rulesets - you should alter these to match your scenario.
rawap's answer is better; but here's something that might also help.
WARNING: This solution was reversed-engineered and I can't really say that this is doing the correct thing here (although it works in terms of what it sets out to do): so 'buyer-beware' here - and I welcome input on how to get this to work properly. (See below for a specific issue with this!)
This will create a series of Properties automatically: actually from the Designer Studio (rather than what you asked for): we put this together as a way of setting up a test where we needed a load of properties.
So: basically this just creates instances of 'Rule-Obj-Property' - using the default Data Transform 'Rule-Obj-Property.pyDefault' to set up most of the required settings (that is, Properties of Rule-Obj-Property - this is all a bit 'meta'); and then tweaking these meta-properties for our needs.
So first stage: create a data-transform in an open ruleset - but save-it to 'Rule-Obj-Property' ; make sure it calls the OOTB 'pyDefault' as a first step:
Note that here we are hardcoding classes and rulesets - you should alter these to match your scenario.
Now we have an Activity (this can be built in any class; but it creates a Page of type 'Rule-Obj-Property' and the first 'Page-New' will apply our Data Transform above (which in turn calls 'pyDefault'):
Then (in a 'counter' loop) do some additional 'Property-Sets' and an 'Obj-Save' (with 'write-now' : normally not a very nice thing to do : but we are running this in the Designer Studio for a specific purpose) like this:
The loop looks like this:
And we have a single PARAMETER 'PropertyPrefix' - with a default of 'Auto' here:
When we run this, with the PARAM set to 'NewTest' we get the following Properties created (you have to refresh Designer Studio to see them):
And make sure you can open these up (just click-through):
NOTE: BE CAREFUL HERE - if you run this Activity TWICE (or more than twice) - the Activity WILL run; without error - but you will end up creating duplicates in the system; which will cause issues ; you won't be able to open the Properties from the Designer Studio Tree for instance.
To deal with duplicates; look for them in 'INSTANCES' of 'Rule-Obj-Property' (rather than using the Tree Control), and open them up individually and delete them.
Pegasystems Inc.
IN
Yes, you can use pxCreateRecord API to create a new property. Can we also know the use case to help you better.
Thanks
Accepted Solution
Pegasystems Inc.
GB
rawap's answer is better; but here's something that might also help.
WARNING: This solution was reversed-engineered and I can't really say that this is doing the correct thing here (although it works in terms of what it sets out to do): so 'buyer-beware' here - and I welcome input on how to get this to work properly. (See below for a specific issue with this!)
This will create a series of Properties automatically: actually from the Designer Studio (rather than what you asked for): we put this together as a way of setting up a test where we needed a load of properties.
So: basically this just creates instances of 'Rule-Obj-Property' - using the default Data Transform 'Rule-Obj-Property.pyDefault' to set up most of the required settings (that is, Properties of Rule-Obj-Property - this is all a bit 'meta'); and then tweaking these meta-properties for our needs.
So first stage: create a data-transform in an open ruleset - but save-it to 'Rule-Obj-Property' ; make sure it calls the OOTB 'pyDefault' as a first step:
Note that here we are hardcoding classes and rulesets - you should alter these to match your scenario.
rawap's answer is better; but here's something that might also help.
WARNING: This solution was reversed-engineered and I can't really say that this is doing the correct thing here (although it works in terms of what it sets out to do): so 'buyer-beware' here - and I welcome input on how to get this to work properly. (See below for a specific issue with this!)
This will create a series of Properties automatically: actually from the Designer Studio (rather than what you asked for): we put this together as a way of setting up a test where we needed a load of properties.
So: basically this just creates instances of 'Rule-Obj-Property' - using the default Data Transform 'Rule-Obj-Property.pyDefault' to set up most of the required settings (that is, Properties of Rule-Obj-Property - this is all a bit 'meta'); and then tweaking these meta-properties for our needs.
So first stage: create a data-transform in an open ruleset - but save-it to 'Rule-Obj-Property' ; make sure it calls the OOTB 'pyDefault' as a first step:
Note that here we are hardcoding classes and rulesets - you should alter these to match your scenario.
Now we have an Activity (this can be built in any class; but it creates a Page of type 'Rule-Obj-Property' and the first 'Page-New' will apply our Data Transform above (which in turn calls 'pyDefault'):
Then (in a 'counter' loop) do some additional 'Property-Sets' and an 'Obj-Save' (with 'write-now' : normally not a very nice thing to do : but we are running this in the Designer Studio for a specific purpose) like this:
The loop looks like this:
And we have a single PARAMETER 'PropertyPrefix' - with a default of 'Auto' here:
When we run this, with the PARAM set to 'NewTest' we get the following Properties created (you have to refresh Designer Studio to see them):
And make sure you can open these up (just click-through):
NOTE: BE CAREFUL HERE - if you run this Activity TWICE (or more than twice) - the Activity WILL run; without error - but you will end up creating duplicates in the system; which will cause issues ; you won't be able to open the Properties from the Designer Studio Tree for instance.
To deal with duplicates; look for them in 'INSTANCES' of 'Rule-Obj-Property' (rather than using the Tree Control), and open them up individually and delete them.