The dynamic required attribute feature in Rational Change
Set an attribute as required based on values defined on other attributes
From the developerWorks archives
Date archived: December 20, 2016 | First published: April 22, 2014
This article helps administrators learn how to define dynamic required attributes, set up rules for this feature and understand how it works on various Rational Change forms. Use dynamic required attributes to gather relevant data from users when a change request is entered, transitioned, or modified, outside of the Lifecycle Editor in Rational Change. This article also explains how the end user is affected by dynamic required attributes.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.