|

Sign up for a trial of the Giva Service Management Suite™


Clarify your solution requirements


Compare and evaluate vendors


Learn about current industry best practices

|
"Day in the Life" Demonstration
Giva eKnowledgeManager User
<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>
The Knowledge Record – Optional Fields
- First and last name of Approver(s)
- Approval dates of all approvals
- Knowledge Hot or Not? This only pertains to Proposed or In Progress knowledge.
This is used for when the person proposing the knowledge wants to quickly allow knowledge to
be shared. Knowledge can immediately be marked "Hot" after it is proposed,
but before approval has occurred. For example, perhaps a solution to a problem has been
found and the problem affects a lot of customers. Best Practices suggest
that users are allowed access to this knowledge before it can be approved.
- Knowledge Team Approval Date – Date the knowledge status
is changed to Approved
- Last Modified By
- Last Modified Date
- Last Used Date
- File attachments – Each attachment has a number. An attachment can be
associated with multiple records. There is only one copy of the attachment in the system so that if
you update the attachment in one place. That is all that is necessary. Many different knowledge
records may point to many different documents. There is the capability to associate and disassociate
file attachments from records. All attachments are searched when any search is performed.
- Record History Display Field – This is a diary where the
history of any changes made to the knowledge record is maintained.
- New History Note – This is where information is entered that
will be displayed in the Record History Display Field.
- Problem Solving Score
- User Score
- Knowledge Source
- Security Level Fields – A knowledge record can be given
a security level. Also, all users and customers that use the system can also be given
security levels so that access is restricted to only knowledge records with a specified
security level. Sensitive knowledge records can be limited to a select group of people.
- Knowledge Record Rejection Reason – This is a field for
a reason why the knowledge was rejected and not approved. This field is
displayed only if the knowledge record is not approved.
<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>
|