An organization may configure to use the Program Level Authorization
strategy where the application case has one or more program types
associated, and separate integrated cases are used to manage the product
deliveries created as a result of authorization. An organization may want
its workers to authorize programs manually, without the requirement for an
authorization ruleset. In this instance, program level authorization can
be used because defining a ruleset for this authorization strategy is
optional.
The organization can configure that a new integrated case is created
for each program that is authorized, or that an existing integrated case
is used, or that the worker selects one or the other. The organization
must also configure the type of integrated case that is created as a
result of authorizing the program. If a product delivery is required, the
product delivery type must be specified for the program, along with the
client selection strategy, i.e., the strategy for determining which
clients on the application case will be added to the product delivery.
The following process is invoked when the worker selects to Authorize a
program:
- The system checks the configuration settings to determine if a new
integrated case should be created or an existing integrated case
selected. It also determines whether a product delivery should be
created and if so, how the clients to be added to the product delivery
will be selected.
- The worker must confirm the authorization. The worker may also be
presented with the option to select an existing integrated case, and the
clients, including the primary client, to be added to the product
delivery, based on the configuration settings.
- If a ruleset has been configured to select the product delivery
clients, this ruleset is executed.
- At this point the system knows the type of ongoing integrated case
required, the type of product delivery required and the clients who
should be added to each product delivery, including the primary
client.
- The set of application case evidence required to authorize the
selected program is determined. This is the evidence that will be copied
both to the integrated case and the product delivery (if one is being
created). See Copying Evidence to an Ongoing Case for
more information.
- The identified set of application case evidence is validated. If the
validation is not successful, the program authorization process is ended
at this point (the program remains in a 'Pending' state).
- If evidence validation is successful, the identified set of
application case evidence is activated.
- As determined by the previous steps, either a new integrated case is
created, or an existing integrated case is identified to host the
required product deliveries. If a new integrated case is created, all
application case clients are added to the integrated case. The primary
client is selected automatically by the system. If an existing case is
used, only application case clients not already present on the
integrated case are added.
- The application case evidence required by the integrated case is
copied to the integrated case. The evidence is automatically validated,
and if successful, activated on the integrated case. The program
authorization process continues regardless of the success of this step.
However, if unsuccessful a notification is sent to the integrated case
owner.
- If a product delivery is to be created for the program then it is
created at this point. The primary client and additional clients are
either determined by a ruleset or selected manually, depending on
configuration settings. The additional clients are added as members of a
product group. The application case evidence required by the product
delivery is copied to the product delivery. The evidence is
automatically applied (validated, and if successful, activated) to the
product delivery. The program authorization process continues regardless
of the success of this step. However, if unsuccessful, a notification is
sent to the product delivery owner. If evidence activation is
successful, the product delivery can be submitted automatically for
approval based on configuration settings. Otherwise it remains in the
'open' state.
- The status of the program is updated to 'Approved'.
- Information pertaining to the authorization event is saved including
the date, the programs authorized and the evidence used in the
authorization event. See Reviewing the Authorization Results for more
information.