This chapter will walk through the process of defining a simple Dynamic Evidence Type, and will introduce the key concepts and components of Dynamic Evidence. The chapter assumes that you have a Runtime installation of the Cúram Platform.
Prior to Cúram 6.0, the definition and maintenance of Evidence Types was a development-time activity. In order to define or modify an Evidence Type, a number of artifacts had to be defined in the Cúram Development Environment, Java code had to be written, screens had to be designed and specified, and the entire application had to be built, deployed and tested before the new Evidence Type could be used in practice.
In Cúram 6.0, an alternative to this traditional development-time version of Evidence (hereafter termed 'Non-Dynamic Evidence') has been provided called Dynamic Evidence. Rather than involving Development-time activity, creation and maintenance of Dynamic Evidence Types is a purely administrative exercise. Using the Cúram Administration Suite and the Dynamic Evidence Editor, administrators can dynamically define equivalent artifacts to those specified by a Cúram developer of Non-Dynamic Evidence.