| Name |
A Dynamic Issue must have a generic and clear
name because the same issue may be used in multiple work codes so
the naming convention is important. When a user attempts to use
a work code and is not allowed, they see the name of the Dynamic
Issue. It is very important that the Dynamic Issue name is clear and
includes the business reason. Dynamic Issues utilize Dynamic Arguments
to give the rule building process extra flexibility. Each Dynamic
Issue can be placed within multiple work codes so they do not have
to be duplicated because they can be reused. |
| Severity When... |
A different denial level may be selected for
each of the contexts that the target Dynamic Issue can be tested:
Adding, Removing, Approving, and Auctions. Depending on the selected
severity, when a Dynamic Issue is activated it denies the use of
a work code. |
| |
Depending on the selected Severity Level, when
the issue enables (triggers), the work code is denied or converted
to a Request. - Denied Level One: allows users with Authority
permission: Issues Override Deny Level One and Two to bypass
the selected Dynamic Issue.
- Denied Level Two: allows users with Authority permission: Issues
Override Deny Level Two, or Issues Override Deny Level One
and Two to bypass the selected Dynamic Issue.
- Ignore: - Does not display the selected issue.
- Illegal: - Prevents all Authority levels to bypass
the error.
- Warning:- Displays the selected issue and allows the
user to continue with the staffing procedure or request. Use for
instructions, reminders, how to instructions...
|
| Type |
Specifies the type of Dynamic Issue and how
the assigned work code behaves. Note: different fields will be enabled
depending on the type selected. Select a Type. Based on the Type
selected, different fields are enabled in the Dynamic Issue detail
window. |
| Condition |
Use to determine when a Dynamic Issue enables.
The Condition field enables the selected Dynamic Issue. This
field is similar to a light switch and used to turn the Dynamic
Issue ON. |
| Convert to a request if denied |
Select to convert work codes to a request when
the dynamic issue activates. Used with Severity when... mode Add, Edit.
When using Request if Deny, a separate dynamic issue must
be created to handle Severity when...Approve. |
| |
Important: The work code must be set
to Dynamic in Approval field. |
| NOT as follows |
Select to apply the opposite behavior of the
entered information. For example, a Concurrent Dynamic Issue
with Issue If Over set at 100, then the Issue is active when
the count hits 100 or more. However, if you select Not as follows,
then the Dynamic Issue is active only to a count of 100. |
| Test Condition |
Use with Type = Condition. This Dynamic
Condition enables the selected Dynamic Issue. The application tests
for the entered condition and if TRUE, then the Dynamic Issue is
active. This field can be used in conjunction with the Condition field.
The application looks first to the Test Condition and if
TRUE, then The application looks to the Condition. If both
conditions are TRUE, then the Dynamic Issue is active. |
| Vacancy Condition |
Use with Type = My Vacancy Condition.
This Dynamic Condition activates the selected Dynamic Issue. The
application tests for the entered condition and if TRUE, then the
Dynamic Issue is active. This Dynamic Argument field tests the potential
impact of the work code. The application dynamically builds a roster
to determine if there is already an alarm on the roster or if the use
of this work code will cause an alarm on the roster. In this field
the conditions that activate the selected Dynamic Issue are: - ROSTERCOUNTALARM: Checks
for existing or active alarms on the Roster.
- ROSTERCOUNTLOCK checks to see if the use of the work
code will cause an alarm. WARNING: This is a tedious test
and reduces roster performance (when viewing all activities on the
roster).
- My Vacancy Condition will not run a test if a vacancy
is not created.
|
| |
This Dynamic Issue tests whether there is an
alarm on the Roster (ROSTERCOUNTALARM) or if this action will cause
an alarm (ROSTERCOUNTLOCK). My Vacancy Condition only flags an issue
if 1) the attached work code causes a vacancy and 2) the Test Condition
is TRUE. Users are often confused when their issue does not trigger
because the vacancy is suppressed. This can happen because the work
code is a request, hidden, etc. or the target person is unassigned
and therefore the vacancy is suppressed by default. This is a tedious
test and reduces roster performance (when viewing all activities
on the roster) significantly. It should be avoided if possible. |
| List Plan |
Use with Type = Rules. Use to run advance
rule arguments. Requires set up prior to use. The dynamic issue
activates, if the person is found to be in violation of the List
Plan. Most commonly used to run fatigue rules when processing shift
trades. |
| Force vacancy creation |
Use with Type = My Vacancy Condition.
A system process used to create a vacancy in the back ground to
determine if this vacancy will drop your Roster below minimum staffing
levels. If TRUE, then Dynamic Issue is active. |
| Submit cover information too |
Use with Type = My Vacancy Condition.
Select to see if the person using a working code to cover the vacancy
meets all the conditions set for the vacancy. |
| From |
Use with Type = Count Occurrences or My
Vacancy Rules. This field requires a Dynamic, Date or Argument
to define your starting point within a range. Enter a Dynamic Date
or Dynamic Argument in proper format to begin the test. For example,
SHIFTSTART, targets the start of the shift. TODAY targets today. |
| Through |
Use with Type = Count Occurrences or My
Vacancy Rules. This field requires a Dynamic, Date or Argument
to define your end point within a range. Enter a Dynamic Date or
Dynamic Argument in proper format to end the test. For example,
SHIFTEND, targets the end of the shift. If active until January 1,
2012, then enter 01/01/2012. |
| From and Through target creation date |
Select to refer to the creation date of the
work code instead of the effective date. |
| Option |
Use with Type = Concurrent and Issue
if over field. Select to count all minimum ranks or all equivalent
minimum ranks in the different organizational hierarchy groupings. |
| Issue if Over |
Use with Type = Concurrent, Count Occurrences,
Sum Hours, or Sum Paybacks. Enter the specific numeric value
a count must reach before the Dynamic Issue is active. |
| or Under |
Use with Type = My Vacancy Rules or Rules.
Enter the specific numeric value a count must drop under before
the dynamic issue is active. This field is active only if the dynamic
issue requires a count. |
| Proposed Duration Too* |
Use with Type = Sum Hours, Count Occurrences,
Sum Paybacks, or Concurrent. Select an option below to control
if and how the proposed (to-be-inserted) durations are to be processed
by the rules: - Sum: sums the durations of proposed records
over the defined period.
- Yes: considers only the duration of the target.
- No: does not consider the proposed duration.
|
| Pattern |
Used with dynamic issue of type, Regular
Expression. In the Condition field, enter a pattern that defines
the type of information that must be entered within the Target field.
The pattern defines the format of the data entered by the user.
For example, if an a budgetary code must be entered into the Account
Code field, the pattern defines the type of characters, length,
etc. of the information entered. In this example, A pattern that
defines that the first letter of code must be an alphabetic character
of A - F must be used followed by 5 numeric characters. The resulting
pattern would require users to enter a budgetary code similar to
this one: B54590. |
| Ignore Case |
Used with dynamic issue of type, Regular
Expression. Select to ignore the size of the text (upper case
or lower case) of the information entered by the user. |
| Target |
Used with dynamic issue of type, Regular
Expression. Select the Target field to perform the Regular Expression
Dynamic Issue for that field based on the Pattern and Ignore Case
settings. Choices are: - Account Code
- Detail Code
- Note
|
| Target Person only |
Used with dynamic issues of type, Count
Occurrences, Sum Hours, or Sum Paybacks and Issue if Over. Select
this check box to apply this rule and value in Issue if Over to
the selected Person only. Clear the check box, to apply the rule
and value in Issue if Over for a group of people. |
| Rank |
When enabled, optionally use this list to narrow
consideration of the Dynamic Issue Type to a selected set of ranks.
Selections made in this list are in addition to other user selected
limitations. |
| Attribute List |
Staffing records have attributes that control
their behavior on the Roster. In this section you can choose to
target these records as follows: - Yes: includes this
record type
- No: excludes this records type
- Dash: ignores the selected attribute.
|
| Work Codes |
Used to assign a dynamic issue to the selected
work code or work codes. Choices are:- Applies- Applies
to the selected Dynamic Issue’s criteria
- Contributes to Group - Applies and contributes hours
or instances of this work code to the group total of the selected
Dynamic Issue’s criteria but will not affect the use or subsequent
use of this specific work code.
|
| |
For example, suppose your daily minimum count
allows two people off on vacation; however, sick people affect your
minimum count for the day which consequently affect people using
the Vacation code, and your business policy does not deny sick time.
In this case, the Vacation work code is set to Applies to deny people
from using the vacation work code once the limit has been reached. The
Sick work code is set to Contributes to Group so that instances
of the sick work code contribute to the minimum count, but the system
will not deny sick code entries. |
| Unique Identifier |
The application’s Internal ID. |