Previously, when the Set Multiple Property Value from WorkView Workflow action was configured using an attribute, the attribute name was used as the id. When the attribute name was changed, the action would no longer function properly. A change was made to use the attribute's numeric ID in this action. Previously configured actions can be updated to the new attribute ID model using WorkView Doctor.
Previously, composite key values were stored in the database with padding, extending the value out to the maximal character number of the column. Currently, the padding is trimmed. In Oracle database, if the values do not match exactly, a new composite key is created. Padding from the keys can be trimmed using the WorkView Doctor to avoid duplicated keys. The Check for duplicate Composite Key due to padding in Oracle option is shown only for Oracle databases.