CommentScreen
This business rule controls the appearance and behavior of various comment screens of OIPA.
Element/Tag | Definition | Attribute | Element/Attribute Value and Description |
---|---|---|---|
<CommentsScreen> |
Start and end tag of the business rule. |
|
|
<GroupCustomerComments> | Dynamic field section that will be visible only if Comments Screen is accessed from the Group Customer Screen. | ||
<UseTemplates> |
Optional element. Indicates if Comment Templates will be used. |
||
If set to Yes Comment Template drop down box will display on Comment Screen, list will include applicable Comment Templates. | Yes | ||
If set to No, field will not be displayed. Default is No. | No | ||
<FixedFields> | Standard Screen Fixed Field configuration is applicable. | ||
<Fields> | Standard Screen Field configuration is applicable. e the Fields Element page. | ||
<Events> | Standard Event Field configuration is applicable. Action/Events are only applicable to Fields within the GroupCustomerComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page | ||
<Actions> | Standard Action configuration is applicable. See the ActionEvents page. | ||
<DefaultComments> |
Optional element: if all applicable comment types have a unique section configured. DefaultComment section configuration is used if a comment type does not have specific configuration. This streamlines the configuration process if one or more comment types use the same fields, etc. Dynamic field section that will apply to all comment types unless they are specifically configured. Note: Client comments are configured in this section. |
||
<UseTemplates> |
Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> |
Allows for configuration of "below the line" fields—standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> |
Allows for configuration of events. Standard screen event configuration is applicable, but events configured here will only apply within the DefaultComments section. See the ActionEvents page. | ||
<ScreenMath> |
Allows for configuration of Screen Math—standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> |
Allows for configuration of actions—standard screen event configuration is applicable, but actions configured here will only apply within the DefaultComments section. See the ActionEvents page. | ||
<PolicyComments> |
Optional element: Allows configuration of the dynamic field section that will only display if the Comments Screen is accessed from a policy. If not present comments accessed from Policy will use the DefaultComments configuration. |
||
<UseTemplates> | Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> | Standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> | Standard screen event configuration is applicable, but events configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> | Standard screen event configuration is applicable, but actions configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<SegmentComments> |
Optional element: Allows configuration of the dynamic field section that will only display if the Comments Screen is accessed from a segment. If not present comments accessed from Policy will use the DefaultComments configuration. |
||
<UseTemplates> | Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> | Standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> | Standard screen event configuration is applicable, but events configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> | Standard screen event configuration is applicable, but actions configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<SuspenseComments> |
Optional element: Allows configuration of the dynamic field section that will only be visible if the Comments Screen is accessed from the Suspense Screen. If not present comments accessed from Policy will use the DefaultComments configuration. |
||
<UseTemplates> | Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> | Standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> | Standard screen event configuration is applicable, but events configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> | Standard screen event configuration is applicable, but actions configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<ActivityComments> |
Optional element: Allows configuration of the dynamic field section that will only be visible if the Comments Screen is accessed from an Activity Screen. This configuration controls activity comments accessed via the Policy, Plan or Client Activity screens. If not present comments accessed from Policy will use the DefaultComments configuration. |
||
<UseTemplates> | Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> | Standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> | Standard screen event configuration is applicable, but events configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> | Standard screen event configuration is applicable, but actions configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<RequirementComments> |
Optional element: Defines the dynamic field section that will only be visible if the Comments screen is accessed via the Activity Requirement screen. |
||
<UseTemplates> | Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> | Allows for configuration of "below the line" fields—standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> | Standard screen event configuration is applicable, but events configured here will only apply within the RequirementComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> | Standard screen event configuration is applicable, but actions configured here will only apply within the RequirementComments section. See the ActionEvents page. | ||
<ImpairmentComments> |
Optional element: Defines the dynamic field section that will only be visible if the Comments screen is accessed via the Assessment screen. |
||
<UseTemplates> | Optional element:
Indicates if comment templates are used. This element can be repeated in all comment screen sections (e.g. <PolicyComments>, <SegmentComments>, etc.). |
Yes:The Comment Template drop-down box will display on the comment screen, and the drop-down list will include all applicable Comment Templates. No: The Comment Template drop-down box will not display on the comment screen. This is the default value. |
|
<Fields> | Standard screen field configuration is applicable. See the Fields Element page. | ||
<Events> | Standard screen event configuration is applicable, but events configured here will only apply within the ImpairmentComments section. See the ActionEvents page. | ||
<ScreenMath> | Standard Screen Math configuration is applicable. See the ScreenMath Element page. | ||
<Actions> | Standard screen event configuration is applicable, but actions configured here will only apply within the ImpairmentComments section. See the ActionEvents page. |
XML Schema
<CommentsScreen>
<DefaultComments>
<UseTemplates>Yes|No</UseTemplates>
<FixedFields/>
<Fields/>
<Events/>
<ScreenMath/>
<Actions/>
</DefaultComments>
<GroupCustomertComments>
<UseTemplates>Yes|No</UseTemplates>
<FixedFields/>
<Fields/>
<Events/>
<ScreenMath/>
<Actions/>
</GroupCustomerComments>
</CommentsScreen>
XML Example
<CommentsScreen>
<DefaultComments>
<UseTemplates>Yes</UseTemplates>
<Fields>
<Field>
<Name>HiddenCommentReason</Name>
<Display>Hidden Comment Reason</Display>
<DataType>Text</DataType>
<Expanded>Yes</Expanded>
<Hidden>Yes</Hidden>
</Field>
<Field>
<Name>FunctionalDepartment</Name>
<Display>Functional Department</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT '', '', 1 FROM DUAL UNION SELECT AsCode.CodeValue, AsCode.LongDescription, 2 FROM AsCode WHERE AsCode.CodeName='AsCodeCommentsFunctionalDepartment' ORDER BY 3, 1</Query>
</Field>
<Field>
<Name>Category</Name>
<Display>Category</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT '', '', 1 FROM DUAL UNION SELECT AsCode.CodeValue, AsCode.LongDescription, 2 FROM AsCode WHERE AsCode.CodeName='AsCodeCommentsCategory' ORDER BY 3, 1</Query>
</Field>
<Field>
<Name>ClientCommentField</Name>
<Display>Client Comment Field</Display>
<DataType>Text</DataType>
</Field>
</Fields>
<Events>
<Event TYPE="ONLOAD">
<ActionSet ID="OnLoadTest"></ActionSet>
</Event>
<Event TYPE="ONCHANGE" FIELD="Hidden">
<Math ID="GlobalScreenMath"></Math>
<ActionSet ID="OnChangeActionSet"></ActionSet>
</Event>
<Event TYPE="ONSUBMIT">
<ActionSet ID="FinalValidation"></ActionSet>
</Event>
</Events>
<ScreenMath>
<Math ID="GlobalScreenMath" GLOBAL="Yes">
<MathVariables>
<MathVariable VARIABLENAME="Checked" TYPE="VALUE" DATATYPE="TEXT">CHECKED</MathVariable>
<MathVariable VARIABLENAME="UnChecked" TYPE="VALUE" DATATYPE="TEXT">UNCHECKED</MathVariable>
<MathVariable VARIABLENAME="OnLoadTest" TYPE="VALUE" DATATYPE="TEXT">Client Data</MathVariable>
</MathVariables>
</Math>
</ScreenMath>
<Actions>
<ActionSet ID="OnLoadTest">
<Condition IF="IsEmpty(ClientCommentField)">
<Action ACTIONTYPE="ASSIGN" FIELD="ClientCommentField">GlobalScreenMath:OnLoadTest</Action>
</Condition>
</ActionSet>
<ActionSet ID="FinalValidation">
<Condition IF="IsEmpty(FunctionalDepartment)">
<Action ACTIONTYPE="ERROR">Functional Department must be entered.</Action>
</Condition>
</ActionSet>
<ActionSet ID="OnChangeActionSet">
<Condition IF="Hidden=GlobalScreenMath:UnChecked">
<Action ACTIONTYPE="HIDE" FIELD="HiddenCommentReason"></Action>
<Else>
<Action ACTIONTYPE="SHOW" FIELD="HiddenCommentReason"></Action>
</Else>
</Condition>
</ActionSet>
<ActionSet ID="FinalValidation">
<Condition IF="IsEmpty(FunctionalDepartment)">
<Action ACTIONTYPE="ERROR">Functional Department must be entered.</Action>
</Condition>
</ActionSet>
</Actions>
</DefaultComments>
<SuspenseComments>
<UseTemplates>Yes</UseTemplates>
<Fields>
<Field>
<Name>HiddenCommentReason</Name>
<Display>Hidden Comment Reason</Display>
<DataType>Text</DataType>
<Expanded>Yes</Expanded>
<Hidden>Yes</Hidden>
</Field>
<Field>
<Name>FunctionalDepartment</Name>
<Display>Functional Department</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT '', '', 1 FROM DUAL UNION SELECT AsCode.CodeValue, AsCode.LongDescription, 2 FROM AsCode WHERE AsCode.CodeName='AsCodeCommentsFunctionalDepartment' ORDER BY 3, 1</Query>
</Field>
<Field>
<Name>Category</Name>
<Display>Category</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT '', '', 1 FROM DUAL UNION SELECT AsCode.CodeValue, AsCode.LongDescription, 2 FROM AsCode WHERE AsCode.CodeName='AsCodeCommentsCategory' ORDER BY 3, 1</Query>
</Field>
<Field>
<Name>SuspenseCommentField</Name>
<Display>Suspense Comment Field</Display>
<DataType>Text</DataType>
</Field>
</Fields>
<Events>
<Event TYPE="ONLOAD">
<ActionSet ID="OnLoadTest"></ActionSet>
</Event>
<Event TYPE="ONCHANGE" FIELD="Hidden">
<Math ID="GlobalScreenMath"></Math>
<ActionSet ID="OnChangeActionSet"></ActionSet>
</Event>
<Event TYPE="ONSUBMIT">
<ActionSet ID="FinalValidation"></ActionSet>
</Event>
</Events>
<ScreenMath>
<Math ID="GlobalScreenMath" GLOBAL="Yes">
<MathVariables>
<MathVariable VARIABLENAME="Checked" TYPE="VALUE" DATATYPE="TEXT">CHECKED</MathVariable>
<MathVariable VARIABLENAME="UnChecked" TYPE="VALUE" DATATYPE="TEXT">UNCHECKED</MathVariable>
<MathVariable VARIABLENAME="OnLoadTest" TYPE="VALUE" DATATYPE="TEXT">Suspense Data</MathVariable>
</MathVariables>
</Math>
</ScreenMath>
<Actions>
<ActionSet ID="OnLoadTest">
<Condition IF="IsEmpty(SuspenseCommentField)">
<Action ACTIONTYPE="ASSIGN" FIELD="SuspenseCommentField">GlobalScreenMath:OnLoadTest</Action>
</Condition>
</ActionSet>
<ActionSet ID="FinalValidation">
<Condition IF="IsEmpty(FunctionalDepartment)">
<Action ACTIONTYPE="ERROR">Functional Department must be entered.</Action>
</Condition>
</ActionSet>
<ActionSet ID="OnChangeActionSet">
<Condition IF="Hidden=GlobalScreenMath:UnChecked">
<Action ACTIONTYPE="HIDE" FIELD="HiddenCommentReason"></Action>
<Else>
<Action ACTIONTYPE="SHOW" FIELD="HiddenCommentReason"></Action>
</Else>
</Condition>
</ActionSet>
<ActionSet ID="FinalValidation">
<Condition IF="IsEmpty(FunctionalDepartment)">
<Action ACTIONTYPE="ERROR">Functional Department must be entered.</Action>
</Condition>
</ActionSet>
</Actions>
</SuspenseComments>
</CommentsScreen>