5. Solution tab
5
Identify the
symptom or
problem
Identify the
symptom or
problem
Set the context of the
Solution including a
classification for more
structured search
Set the context of the
Solution including a
classification for more
structured search
6. Solutions tab – Cause
and Resolution
section
6
Identify the
cause relating to
the symptom
Identify the
cause relating to
the symptom
Identify the
resolution of the
symptom or
problem
Identify the
resolution of the
symptom or
problem
7. Specification tab
7
If the Classification
has attributes these
will be listed here
and can be edited
on the Solution
If the Classification
has attributes these
will be listed here
and can be edited
on the Solution
8. Ownership tab
8
The Ownership tab is
used to provide
governance and
ownership information
for the Solution
The Ownership tab is
used to provide
governance and
ownership information
for the Solution
Both ownership
and approvals can
be added here.
Both ownership
and approvals can
be added here.
Solutions are System
level records but this
section can be used to
filter records if needed
Solutions are System
level records but this
section can be used to
filter records if needed
9. Benefits tab
9
Add Impact records
to identify both
benefits and/or
losses associated
with the Solution
Add Impact records
to identify both
benefits and/or
losses associated
with the Solution
Estimated Benefit and
Estimated Benefit
Units are mandatory.
Default to zero if not
required
Estimated Benefit and
Estimated Benefit
Units are mandatory.
Default to zero if not
required
10. Log tab
10
Communication Log generated automatically
from Create Communication or Workflow
actions
Communication Log generated automatically
from Create Communication or Workflow
actions
Manually
created log
entries
Manually
created log
entries
14. Solution Statuses
Draft – All fields are editable.
Active – All fields are editable. Must be in
this status to be associated to another
record.
Inactive – All fields are read only.
14
15. Solutions –
Business rules
•Lessons Learned? Must be checked for a Solution to be
Associated with the Lessons Learned sub tab on an
Investigation.
•When Lessons Learned? Is checked the Solution record
cannot be associated with any records other than
Investigations (A Lesson Learned may be recorded but
not formally acknowledged as an agreed Solution for
access in other applications.
•When Self-Service Access? Is checked the Solution
record will be visible from the Search Solutions
application in the Self-Service Module, Service Requests
sub module.
15
16. Self Service
Module – Service
Request sub
module, Search
Solutions
application
16
Note: Search Solutions is not available from the standard Service Requests application
17. Incidents –
Solutions tab
17
Solutions are editable
on the Investigation or
can be copied over
from a Solution record
Solutions are editable
on the Investigation or
can be copied over
from a Solution record
18. Investigations –
Solutions tab
18
Whereas on Incidents only a
single Solution can be added on
Investigations multiple Solutions
may be added
Whereas on Incidents only a
single Solution can be added on
Investigations multiple Solutions
may be added
Multiple lessons
learned may be added
to an Investigation.
Lessons Learned?
Must be checked on
the Solution record
Multiple lessons
learned may be added
to an Investigation.
Lessons Learned?
Must be checked on
the Solution record
Solutions and Lessons
Learned are editable
on the Investigation
or can be copied over
from a Solution
record
Solutions and Lessons
Learned are editable
on the Investigation
or can be copied over
from a Solution
record
19. Solution Search
A ‘Search Solutions’ action is providing in
the following applications:
•Incidents
•Investigations
•Defects
19