Phire 15.

1
Application Configuration
Copyright © 2020, Phire. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited. The information contained in this
document is subject to change without notice. If you find any problems in the documentation, please report
them to us in writing. This document is not warranted to be error-free. Unless permitted in your license
agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form
or by any means, electronic or mechanical, for any purpose.

Default Assignments
The Issue and Change Request Management modules of Phire provide the ability to specify
default assignments for newly created Issues and Change Request tasks. This feature enables
organizations to set up queues to spread out work assignments, facilitate the switching of the
workflow tasks in change requests, and make the entire process of creating assignments more
efficient.

Copyright @ 2020 Phire Inc. All rights reserved. Page 1 of 5

Issue Default Assignment
The Issue Management module of Phire provides the ability to automatically assign personnel to
work on a new Issue based on predefined criteria that include the Issue Type and Functional
Area. This information is used to make an initial assignment of an Issue once it has been
submitted. The Issue Assignment component is where the criteria matrix is maintained:

Issue Assignment Logic

The Issue Assignment Queue page contains a matrix of Issue Type, Functional Area, and Assigned
To values for a given Domain. This information is queried to determine who should be assigned
to the issue when a user submits the Issue on the Issue Management component. Once the
assignment is made, the specific Issue will be populated into that assignee’s Worklist.

Issue Type and Functional Area values can be left blank which allows the assignment to be
applied to all Issue Types or to all Functional Areas. Additionally, entries can be made inactive
to temporarily disable an assignment. This is useful if an individual is on vacation, eliminating
the need to delete the entry. The entry can be reactivated when necessary.

The Assigned To value can be set to a user profile or a role. The use of a role has the effect of
assigning the issue to everyone who is a member of the role. Each user in the role will have equal
access to work the issue and the issue will appear in their worklist.

The rules for the default assignments are configured as follows.

1. Exact match on the Domain, Issue Type and Functional Area.

2. Match on the Domain and Issue Type only.
3. Match on the Domain and Functional Area only.
4. Match on the Domain only.

At each level, if no match is found, it proceeds to the next level. The resulting users are tested to
ensure that they have the necessary permissions to the combination of Domain, Issue Type and
Functional Area. If more than one matching user is found, Phire will choose the user profile or
role with the fewest number of open issues.

The default assignment queue can be built and maintained to a degree of granularity that suits
the organization’s needs. For example, a single entry with the Issue Type and Functional Area
left blank would result in all submitted issues for that Domain to be assigned to the named user

Copyright @ 2020 Phire Inc. All rights reserved. Page 2 of 5

profile or role. At the other end of the spectrum, every combination of Domain, Issue Type, and
Functional Area can be added explicitly to provide very granular control.

CR Default Assignment
The Change Request Management module in Phire provides the ability to define default
assignments to each task in the workflow based on predefined criteria that includes the Domain,
Change Request Type, Functional Area and Task Type. This information is used to assign Change
Request Tasks to a user profile or a role when a Change Request is initially created, or when an
unassigned Task becomes current in the workflow. The CR Task Assignment component is
where the criteria matrix is defined and maintained:

CR Assignment Logic
The Task Assignment Queue page contains a matrix of CR Type, Functional Area, Task Type and
Assigned To values for a given Domain. When a CR is created, the CR Type and Functional Area
must be populated by the user. With that information, the workflow tasks are generated, and the
assignment of the Tasks are made.

The following rules are followed when determining how the task assignment is to be made. Note
that Phire Security is checked at every point to ensure that the task is assigned to a user with
permission to the combination of values.

1. If there is a Default User identified in the CR Type’s workflow definition, then that user
or role is assigned automatically. The default user can be one of the following values:

a. A specific user profile forcing the assignment to that individual.

b. A specific role, allowing the CR Task to be accessible to all the members of the role.
c. A default value of %UserId can be specified, which will dynamically set the initial
assignment to the current user.
d. A default value of %Customer can be specified, which will dynamically set the
assignment based on the value in the Customer field on the main CR page.
Subsequent changes to the Customer value will result in the task assignments being
changed.
e. A default value of %Assignee can be specified, which will be replaced by the value in
the field PHI_TASK_ASSGN_TO and returned by the view PHI_ASSIGNEE_VW

Copyright @ 2020 Phire Inc. All rights reserved. Page 3 of 5

 based on the current user. This view is delivered with default SQL that will simply
return the current user. However, a customer can modify this view to return a value
that meets any special requirements, such as retrieving the user’s supervisor. This is
the SQL as it is delivered in the view:

SELECT DISTINCT OPRID, OPRID

FROM PSOPRDEFN

A customer may, for example, want to replace this SQL with something like the
following, which will return the supervisor based on the current user:

SELECT DISTINCT OPRID, SUPERVISOR_ID

FROM PS_EMPLOYMENT

Note. Any customizations made to this view needs to be documented and may need
to be reapplied when future versions of Phire are delivered.

2. If there is a successful assignment of a Task in the workflow, all the tasks that are of the
same Task Type are automatically assigned to the same user profile or role.

3. The CR Task Assignment Queue is read in the following progression:

a. Exact match on Domain, CR Type, Functional Area and Task Type.

b. Match on Domain, CR Type and Functional Area only
c. Match on Domain, CR Type and Task Type only
d. Match on Domain and CR Type only
e. Match on Domain, Functional Area and Task Type only
f. Match on Domain and Functional Area only
g. Match on Domain and Task Type only
h. Match on Domain only.

At each level, if no match is found, Phire proceeds to the next level. The resulting users are
validated to ensure that they have permission to the combination of Domain, CR Type, Functional
Area and Task Type. If an assignment is found to be in violation of the Segregate Task rule (see
document entitled Change_Request_Workflow.pdf) defined in the workflow, then the
assignment is discarded, and the analysis continues. If more than one matching user is found,
then the assignment is made to the user profile or role with the fewest number of current open
change requests.

If there are no matching user profiles or roles found, then the task assignment is left blank. When
the task without an assignment becomes the current task, then the user is prompted to manually
make the task assignment by selecting a valid value from the prompt list before the Change
Request can be saved.

The default assignment queue can be built and maintained to a degree of granularity that suits
the organization’s needs. For example, a single entry with the CR Type, Functional Area, and
Task Type left blank would result in all submitted Change Requests for that Domain to be
assigned to the defined user profile or role. At the other end of the spectrum, every combination

Copyright @ 2020 Phire Inc. All rights reserved. Page 4 of 5

of Domain, CR Type, Functional Area, and Task Type can be added explicitly to provide very
granular control.

Copyright @ 2020 Phire Inc. All rights reserved. Page 5 of 5