Summary

This article defines the instruction additionallyHandleFormWithType.

Table of Contents

• Instruction additionallyHandleFormWithType
  • Restriction
  • Overview
  • Question Id
  • Value
  • Input value
  • Examples

Instruction additionallyHandleFormWithType

Restriction

This instruction is usable for table exports only. Typically this will be a custom export to text, Excel or SAS. This instruction is not available for XML exports.

Overview

Instruction ‘additionallyHandleFormWithType’ triggers that the currently selected form is (additionally) handled with another ‘export form type’. The name of the additional export form type is usually not a real form type for the application. It exists only to be triggered for execution from this command.
Example: with the normal form type expression “adverseEvent,AE” a form of type ‘adverseEvent’ is exported to the ‘AE’ domain. This instruction with a value of “otherAdverseEvent” would result in the export handling of the current adverseEvent form with the export type id otherAdverseEvent. When there would be a configured export form type “otherAdverseEvent,SAE”, then the ‘adverseEvent’ form would be exported to the ‘SAE’ domain with the “otherAdverseEvent” configuration. Typically there will not be a real form type ‘otherAdverseEvent’. While this instruction does not add functionality for normal form exports (you could configure ‘adverseEvent,AE’ and ‘adverseEvent,SAE’), it makes sense in case that you are iterating over multiple selected values of one question, see instruction rowIterationOnSelectedValues).

Question Id

Unused.

Value

When the value is the name of an export form type for which the current form should be handled with.

Input value

The input value for this instruction is passed unchanged as output value. No processing with the input value is done.

Examples

Need more help?

Please visit the Fountayn Contact Information page.