It's all about the answers!

Ask a question

Issue of mandatory attributes in bulk modification


iRAM Administrator (3152146135) | asked Aug 25 '10, 12:52 p.m.
We need to bulk modify many assets to change their categories from old to new values.
The issue is for the assets which do not have values for any mandatory fields.
As a workaround to resolve this issue we planned the activity containing following steps :
1) Community wise Modify the asset types and make the mandatory attributes to non mandatory attributes by using Override the configuration from the global asset type option of the corresponding Asset Type under in Administration - > Communities - > Asset Types.
2) Bulk modify those assets.
3) Again open the particular community and modify the asset types and make the respective non-mandatory attributes to mandatory attributes by using Override the configuration from the global asset type option.
Please let is know if there are any risks or any issues with this workaround.
Or, suggest us if there is some other workaround for this issue.

3 answers



permanent link
Jonathan Stinton (11) | answered Aug 30 '10, 4:46 p.m.
If you are using the bulk asset modify feature in the web client, community administrators have the option to "override review processes." This not only prevents them from having to to re-review the assets, but also allows them to update assets that may now contain validation errors.

In your case an asset may have been submitted without attribute "Foo" which has since been added as required. Performing a standard update would be blocked unless "Foo" is provided. However, using the bulk tool admins can bypass the review and perform only the updates they want without providing a value for "Foo."

It is generally discouraged to temporarily disable review process or required attributes for the entire community. There is no way of knowing who is submitting an asset at that time, and they may be able to submit invalid assets without permission.

permanent link
Bob Newman (1123) | answered Nov 15 '10, 6:08 p.m.
JAZZ DEVELOPER


In your case an asset may have been submitted without attribute "Foo" which has since been added as required. Performing a standard update would be blocked unless "Foo" is provided. However, using the bulk tool admins can bypass the review and perform only the updates they want without providing a value for "Foo."


Yes, but the big gotcha' with that procedure is the asset with the empty 'FOO' attribute (and thereby with a validation error) will be tossed into Draft state when it is Bulk Updated. That is an unacceptable outcome. Imagine bulk Updating 1,000 such assets and having them all tossed back into Draft state. Now each of those 1,000 assets must be shepherded back through the Lifecycle reviews to approved state. Not very practical. Now imagine bulk updating a 75,000 asset repository and having maybe 25,000 end up tossed into Draft state because of this. Now that is a real problem :-)

permanent link
Rich Kulp (3.6k38) | answered Nov 15 '10, 6:53 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Bulk update has an option (as of 7.2.0.2) for Admins to bypass review
processes.

If that option is selected on the bulk update page then asset will not
be pushed into Draft state. It should, as I understand it, be left in
the current state.

--
Rich Kulp
Rational Asset Manager developer

Your answer


Register or to post your answer.