Large Text Prototype
OIPA supports fields that allow a user to enter large amounts of text. This text can be viewed in its entirety on the screen and in the Activity Results tab after an activity is processed.
Scenario
The Issue transaction has been configured with a TextArea field to enter free-form information. The character limit is 260. This field is used by the CSR to enter free-form information that is fed to the document system used to create policy pages. The CSR enters 230 characters and is able to see all information that was entered. An update is made to the text field that pushes the character amount to 270. The first 260 characters are visible to the CSR.
Prototype Examples
- A LargeTextPrototype transaction was configured to demonstrate the new TextArea field datatype, the BIGTEXT math variable datatype, and the new StringLength() function. Navigate to Global Explorer |Transactions | LargeTextPrototype | LargeTextPrototype (Functional Prototype Plan).
Two MathVariables were created:
BigTextMV1: the BIGTEXT datatype that assigns the field values of TextArea1 to a MathVariable.
- BigTextMV2: the BIGTEXT datatype that assigns the field values of TextArea2 to a MathVariable.
The two other MathVariables are TYPE=FUNCTION math variables. These math variables demonstrate the new StringLength() function.
TextArea1Length: INTEGER datatype that uses the TextArea1 field as the parameter in the function. When processed this math variable will display the length of the TextArea1 field.
- BigTextMV2Length: INTEGER datatype that uses the BigTextMV2 as the parameter in the function. When processed this math variable will display the length of the BigTextMV2 math variable. This value is originally derived from the TextArea2 field.
- An action using the IsEmpty() function is used to verify that screen functions work properly with the new TextArea datatype. If the TextArea1 field is empty, an OnSubmit validation message should display. Once TextArea1 is populated, the activity should allow processing.
- The LargeTextPrototype transaction, when processed, will spawn itself twice to demonstrate using fields and math variable values in the <SpawnFields> section. The first spawn will use the TextArea1 and TextArea2 fields as the <From> spawn fields. The second spawn will use BigTextMV1 and BigTextMV2 as the <From> spawn fields. Both spawned activities use TextArea1 and TextArea2 as the <To> spawn fields.
View Prototype in OIPA
- Log into the Prototype company in OIPA.
- Open an existing policy and click the activity link to open the Activity screen. If no policy exists, create a test policy with generic roles and segments.
- Click the Add Activity link in the Secondary menu and select the LargeTextPrototype activity.
- Enter a large amount of text in the two provided fields.
- Click OK to close the Add Activity window and add the activity to the Activity screen.
- Process the activity by clicking the lightning bolt icon. Notice that two new activities were spawned as a result.
- Click the Activity Detail icon to the left of the processed activity.
- Click the Entry Fields link at the top of the window to display the large text that was added.
Activity Results Window in OIPA showing Large Text Fields