Hi,
The SetAttributeValue function only updates the settings temporarily, it does not store them in the database.
There's an open enhancement request asking for a way to have these updates committed to the database.
In the meantime, although fairly complex, a workaround solution for it would be to automate the production and load of an xml file containing the attribute values you are looking for.
Regards,
Fred
Hi Fred,
Is there any alternate way to perform this usinng database, anyclue on this?
manthangandhi - You can try with the WFText1 value. This could be workaround vs updating the table directly. My 2 Cents. I am not sure about the complete use case, trying to put some ideas.
1. Create a Extender BR to populate the text1 Value of the WF profile.
2. Ignore the WF Profile in your BR based on the Text1 value.
The properties are all there in the WorkflowProfileAttributes table... You might get some frowns from updating it on here but if its working around a bug then maybe it is the best way. You might need to run the setAttributeValue as well if that command is doing an in-memory/cache update as your DB table change might not be visible to clients (and perhaps even get overwritten? not sure).
