PolicyActivityScreen

<PolicyActivityScreen>

The opening and closing tag of the Policy Activity Screen Business Rule.

<MaximumRows>

Defines the maximum number of Activities that will display on each page of the PolicyActivityScreen. If Tag is not present or their is an illegal value (non-integer) the default is 100.

Integer: Valid values are 5, 10, 15, 20, 100.

<FromDate>

Defines the From Date field as the start date the user wants to display Activities from.

BeginningOfYear: Displays beginning of the year based upon current system date.
BeginningOfMonth: Displays beginning of the month based upon current system date.
PreviousDay: Displays previous day of system date.
Blank: Displays blank value
If the element is not present default is blank.

<FixedFields>

Allows configuration of fixed fields.

<Field>

The opening tag for each Fixed Field being configured.

<Name>

Exact name of the Field (database name).

String

<Display>

Display name of the field, indicates how the field will display on the screen.

MASK

Display Name
 
Optional Attribute;
Date/SSN

<Disabled>

Indicated if the Fixed Field should be visible but no entry is allowed.

Yes/No/ReadOnly

<Hidden>

Indicates if the Fixed Field should be hidden.

Yes/No

<Fields>

Allows configuration of dynamic fields. Press <Fields> link for additional information on the <Fields> Element configuration.

<Field>

The opening tag for each dynamic Field being configured.

Only applicable data type is Label.

<Calculated>

Defines the type of query.

TYPE

Required Attribute;
SQL

<ScreenTimes>

Optional element
This element is used to limit the access to the activities based on the Time of day, Business day (or Non-Business day), End of Month or Quarter or Year or through the Tests conditions (Security Role, Activity columns, Effective Date of the Activity, Client Number etc )

Note: <ScreenTimes> section is backward compatible. i.e. If this section does not exist in this business rule then the system will use the <ScreenTimes> section defined in TransactionTimes Business rule.

<Prohibit>

Required/Repeatable element;
This element is used to specify the list of actions that can be restricted and display the necessary alert messages.

TYPE

Optional attribute

Delete - To restrict the User from deleting a Pending activity, by clicking the Delete button.

Add - To restrict the User from adding an activity in this screen, by clicking the ADD button.

Edit - To restrict the User from editing the details of a Pending activity, by clicking the Edit button.

Process - To restrict the User from processing a Pending activity, by clicking the Process button

Reverse - To restrict the User from reversing an active activity, by clicking the Delete button

Recycle - To restrict the User from recycling an active activity.

Notes:

If this attribute is not present, then no restriction is applied to any of the actions

If a button is made inaccessible, then a custom message shall be configured to communicate the same to the User.

Recycle button refers to the icon (blue and pink arrows) on the right of a processed activity.

Delete button refers to the trash can icon on the right of an active activity.

Process button refers to lightening bolt icon right of the pending activity.

Edit button on the PolicyActivityScreen refers to the icon on the left of a Pending activity.

Add button is displayed next to the Activity dropdown box in the PolicyActivityScreen.

Delete button on the activity screen refers to the trashcan icon on the right of a pending activity.

Optional attribute;
="Warning Message"
If a button is made inaccessible, then a custom message shall be configured to communicate the same to the User

Note: In the absence of this attribute, a default message will be displayed.

<StartTime>

Optional element;

This element is used to specify the Starting time from when the User should be restricted from performing certain tasks.

Note: If this element is included, then <EndTime> element MUST exist. Action is prohibited during this time range.

Required element value;

Integer - Time of day expressed in Military time

String

a) FieldName from AsSystemDateField
e.g.: MarketStartTime

b) SystemDate from AsSystemDate
e.g.: SystemDate

<EndTime>

Optional element;
This element is used to specify the Ending time until when the User should be restricted from performing certain tasks.

Note: If this element is included, then <StartTime> element MUST exist. Action is prohibited during this time range.

Required element value;

Integer - Time of day expressed in Military time

String -

a) FieldName from AsSystemDateField
e.g.: MarketEndTime

b) SystemDate from AsSystemDate
e.g.: SystemDate

<BusinessDayIndicator>

Optional element;

This element can be used to find if the current System date is a Business day or not and apply the restrictions accordingly.

Note: This element can be used instead of using <StartTime> and <EndTime> elements.

The presence of this element in this business rule itself invokes the verification of whether a System Date is a business day or not

The values are stored in the BusinessDayIndicator column of AsSystemDate.

Required element value;

Yes - Indicates that if the current System Date is a Business day, only then the specified access should be restricted

No - Indicates that if the current System Date is not a Business day, only then the specified access should be restricted.

<MonthEndIndicator>

Optional element;
This element can be used to find if the current System date is the last day of the Month or not and apply the restrictions accordingly.

Note: This element can be used instead of using <StartTime> and <EndTime> elements.

The presence of this element in this business rule itself invokes the verification of whether a System Date is a last day of the Month or not

The values are stored in the MonthEndIndicator column of AsSystemDate.

Required element value;

Yes - Indicates that if the current System Date is the last day of the Month, only then the specified access should be restricted
No - Indicates that if the current System Date is not the last day of the Month, only then the specified access should be restricted.

<QuarterEndIndicator>

Optional element

This element can be used to find if the current System date is the last day of the Quarter or not and apply the restrictions accordingly.

Note: This element can be used instead of using <StartTime> and <EndTime> elements.

The presence of this element in this business rule itself invokes the verification of whether a System Date is a last day of the Quarter or not

The values are stored in the QuarterEndIndicator column of AsSystemDate.

Required element value;

Yes - Indicates that if the current System Date is the last day of the Quarter, only then the specified access should be restricted
No - Indicates that if the current System Date is not the last day of the Quarter, only then the specified access should be restricted.

<YearEndIndicator>

Optional element

This element can be used to find if the current System date is the last day of the Year not and apply the restrictions accordingly.

Note: This element can be used instead of using <StartTime> and <EndTime> elements.

The presence of this element in this business rule itself invokes the verification of whether a System Date is a last day of the Year or not

The values are stored in the YearEndIndicator column of AsSystemDate.

Required element value;

Yes - Indicates that if the current System Date is the last day of the Year, only then the specified access should be restricted
No - Indicates that if the current System Date is not the last day of the Year, only then the specified access should be restricted.

<Tests>

Optional element

Start of the test section for the action being prohibited. Restriction is invoked if test condition is met. If all of the tests evaluate to true then the restriction will apply. Activity, client, security, security role and system date columns will be available using the colon notation. System date will be used as an auxiliary field and will also be available for tests.

<Test>

The value of this tag will be an expression. This expression will determine if the restriction should be invoked.

String: Expression. Conditional test.

Activity, client, security, security role and system date columns will be available using the colon notation. System date will be used as an auxiliary field and will also be available for tests. See the below that has the possible options for the tests section.
 
Activity columns can be all columns in AsActivity table.
Client columns can be all columns in AsClient table.
SystemDate columns can be all columns in AsSystemDate table.

Security columns can be all columns in AsSecurity table.
SecurityRole columns can be all columns in AsSecurityRole table.
 
Exp. Activity:EffectiveDate = System:SystemDate.

<Warnings>

Defines the warnings node, warning messages are defined via business rules and are optional. They may exist at the Screen Rule level or at the Transaction Cosmetics Rule level. Warnings defined in the Transaction Cosmetic Rule take priority over the Screen Rule.

<DeleteWarning>

Controls if warning is given when Activity is Deleted. If Tag is not present no warning will be displayed.

MESSAGE

String

Displays message as specified when MESSAGE attribute value is specified.

Displays default message, "Are you sure?" when MESSAGE="" i.e. When MESSAGE attribute value is not specified.
 
Yes - Tag/Element value
No - Tag/Element value

<ReverseWarning>

Controls if warning is given when Activity is Reversed. If Tag is not present no warning will be displayed.

MESSAGE

String

Displays message as specified when MESSAGE attribute value is specified.

Displays default message, "Are you sure?" when MESSAGE="" i.e. When MESSAGE attribute value is not specified.
 
Yes - Tag/Element value
No - Tag/Element value