AM/CM Integration Guide

Version AM 11.0 / CM 1.2

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this document may be reproduced, stored in or introduced into a
retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of Wolters
Kluwer.

© 2014 TeamMate Licensing B.V. All rights reserved.

Date created: 11/20/2014 4:08 PM

Table of Contents
Table of Contents iii
TeamMate AM and CM 4
Set Up CM Web Service Location 5
Email Settings 5
TeamStore Behavior Changes 7
Editing Shared TeamStore Content 7
Deleting Shared TeamStore Content 8
Shared Primary Dimension 9
AM/CM Primary Dimension - Deletion Rules 9
Lock/Unlock the Primary Dimension 10
Primary Dimension Attachments 11
Shared Users 12
Suite Level Role 12
Security Logging 12
Shared Taxonomy (Terminology and Categories) 14
TeamMate Support 15

iii
 TeamMate AM and CM
For reference in this guide, ‘AM’ refers to TeamMate AM as the audit management suite of applic-
ations and includes TeamStore, TeamEWP, etc. ‘CM’ refers to TeamMate CM as the compliance
management application.
TeamStore Content, Primary Dimension (Global Organization Hierarchy), Users and Taxonomy
(Terminology/ Categories) are shared between CM and AM:

AM/CM Integration Guide 4

 Set Up CM Web Service Location
There are some functions that require AM to behave in the same technical manner as CM. To
address these needs, a CM web service was created that allows for AM to make web service calls
for various shared functions when it detects CM is in use:
1. Terminology and Category changes made in TeamAdmin will automatically be updated,
CM only needs to reload the page to see the changes.
2. Deleting entities from the Global Organization Hierarchy in TeamAdmin needs to verify the
entities are not in use in CM.
3. Deleting items (i.e. objectives, risks, controls, tests) in TeamStore needs to verify these
items are not used in CM.
4. After completing the initial TeamAdmin setup, during a new AM installation and if CM is
also being used, the administrator should open CM and press  the “Clear Cache” button in
order to clean temporary configurations
For the web service to function correctly, the URL for TeamMate CM must be entered in TeamAd-
min. See Email Settings.

TIP: If the CM web service was not set correctly an error message will display when any of
the above actions are attempted: "An error occurred while trying to establish a connection
to web CM service. Contact your system administrator to update the service location in
CM Setup."

It will be displayed every time that you try to update data (objectives, risks, controls) that is shared
with CM.

Email Settings
In addition to setting up the CM web services, as discussed above, emails will also need to know
where TeamMate CM is installed for navigating from the email back to the application. This URL
can be set up in TeamAdmin as a row in the Application Web Address List will display for CM.

To update email settings:

AM/CM Integration Guide 5

 1. Log into TeamAdmin.
2. Navigate to Integration Setup.
3. Navigate to Email Settings.
4. In the Application Web Address List, find the row for ‘TeamMate CM.’
5. Add the URL for TeamMate CM.

AM/CM Integration Guide 6

 TeamStore Behavior Changes
TeamStore in AM and CM share content: Objectives, Risks, Controls, and Procedures. Accord-
ingly, there are some subtle behavior changes that take effect ONLY when both AM and CM are
in use.

Editing Shared TeamStore Content

In TeamMate CM certain fields for an Objective, Risk, Control and Procedure are considered
‘base’ or ‘master’ fields. These fields are used to ensure that the nature of an objective, risk, con-
trol or test is preserved everywhere that content is used in CM Assessments. It ensure that
‘apples-to-apples’ comparisons of results are possible.
The only place these ‘base’ fields can be changed is in TeamStore. Edits made in TeamStore will
be pushed to open/re-opened CM Assessments automatically.

Fields considered base are:

Objective Risk Control Procedure
Objective Title Risk Title Control Title Procedure Title
Objective Code Risk Code Control Code
ObjectiveText1 Descrip- RiskText1(Descrip- ControlText1 (Descrip-
tion) tion) tion)
ObjectiveCategory1 RiskCategory1 ControlCategory1 ProcedureCategory1

When content (Objective, Risk, Control or Procedure) is modified in AM TeamStore there are val-
idations performed before pushing the changes to CM Assessments:
1. If the modified content is only used in the AM applications and any field is updated (base
field or not) the “Changes will affect active Assessments and Projects. Do you want to push
these changes?” message will be shown. The user has the options to push or not the
changes only for Active Assessments and Projects.
2. If the modified content is only used in the CM application and the updated field(s) is a Base
Field only, no message is shown. The edits will automatically update Open CM Assess-
ments. Closed/ Finalized CM Assessments are not updated.
3. If the modified content is used in both applications and updated field(s) are base fields only,
the “Changes will affect active Assessments and Projects. Do you want to push these
changes?’ message will be shown to update the changes in AM applications. As noted in
#2, Open CM Assessments will receive the automatic updates

NOTE: If the updated field(s) is not a Base Field the changes are not pushed to
open CM Assessments.

When a Base Field edit is made in AM TeamStore and pushed to Opened CM Assessments, the
content’s history is updated in TeamMate CM by adding an action "Edited in TeamStore" and
including the user who made the edit and edit date.

AM/CM Integration Guide 7

 Deleting Shared TeamStore Content
From AM TeamStore, the user cannot delete content (Objective, Risk, Control, and Procedure)
that was added from TeamStore in any opened/re-opened CM Assessment.
The delete button will be enabled, but a message will be shown “Cannot delete items that are in
use in an Open Assessment”.
If the user tries to delete a Cabinet or Folder that contains content which is used in any open CM
Assessment, the same message will be shown.
Deletes are permitted if the content is associated with a closed/ finalized CM Assessment, as the
finalization process takes a copy (rather than references a link) of the content for archive pur-
poses.

AM/CM Integration Guide 8

 Shared Primary Dimension
In TeamMate AM, there is only one dimensional structure available. It is typically referred to as the
Global Organization Hierarchy.
In TeamMate CM, as many as six dimensional structures can be included with one identified as
the primary dimension. AM and CM share the primary dimension only.
The primary dimension is the structure used to create both AM and CM assessments from, is ref-
erenced in AM Audit Plans and is required for all AM TeamEWP projects.
Since the Primary Dimension is shared and CM allows multiple dimensions there some AM
impacts:
l TeamAdmin only displays the primary dimension.
l TeamAdmin Global Organization Hierarchy has an alert function for additions, edits and
deletions made in CM. It is optional to push these changes to AM Audit Plans. Editing the
Primary Dimension, in either application, requires a lock action before edits can be made.
This ensures that simultaneous edits are not made which may overwrite each other. Who
has the Primary Dimension locked is displayed.
l Attempts to delete an entity from the Primary Dimension will first verify that the entity is not
in use in either AM or CM before proceeding.
o Soft deleted entities are shown on the Primary Dimension in TeamAdmin when these
were deleted in CM.
l Attachments made to entities of the Primary Dimension will be visible to both AM and CM
regardless of which application was used to add the attachment.

AM/CM Primary Dimension - Deletion Rules

The deletion rules are slightly different in TeamAdmin (AM) when CM is in use to ensure data
integrity is appropriately managed.

The deletion rules are:

1. AM/CM Administrators cannot delete any entity node in the Primary Dimension if it is in use
in an Open CM Assessment. This includes entities that may not be directly used in a CM
Assessment, but are the parent nodes of entities used.
2. AM/CM Administrators can delete an entity that is used in a finalized or re-opened CM
Assessment. The finalization process creates a copy of the Primary Dimension and no
longer references the live Primary Dimension.
3. CM soft deletes an entity that is used in AM Assessment or Project, since the AM asso-
ciation really exists in the copy of the Primary Dimension taken when creating the Audit
Plan (referred to as the OH Snapshot).
This action removes the entity from the Primary Dimension structure in CM, and identifies
the entity as modified by CM; an AM Administrator can then decide to push the deletion to
one or more Audit Plans in TeamAdmin.
The entities that were deleted by a CM Administrator are shown in TeamAdmin in red and strike-
through style. Additionally, a message (also in red) is displayed ‘Entities that have been changed

AM/CM Integration Guide 9

 in CM are highlighted in red’. Below this message are the options to: Do Nothing; Push CM
Changes; or Clear Notification.

Message options:
1. Do Nothing:
l No "Audit Plan Chooser" dialog is displayed.
l Does not push CM changes.
l Continues displaying CM changes the next time.
l Alert message and Action combo will be displayed until cleared.
2. Push CM Changes:
l The "Audit Plan Chooser" dialog is displayed.
l Pushes CM changes to the selected Audit Plans.
l Alert message and Action combo will not be displayed again.
3. Clear Notification:
l No "Audit Plan Chooser" dialog is displayed.
l Does not push CM changes.
l Alert message and Action combo will not be displayed again.

Lock/Unlock the Primary Dimension

AM/CM Integration Guide 10

 CM has a feature to Lock/Unlock the Primary Dimension. The Administrator needs to lock the
Primary Dimension before any edits are possible.
The same is true for AM; a TeamAdmin Administrator will need to Lock/Unlock the Global Organ-
ization Hierarchy to made edits.
In both applications, the name of the Administrator who locked the Primary Dimension will be
shown.

If the Global Organization Hierarchy is locked in CM, it shows as locked in TeamAdmin and vice
versa. Both applications share the lock indicator so prevent simultaneous edits and to inform
either Administrator who currently is making edits.

Primary Dimension Attachments

In both AM (TeamAdmin) and CM, attachments can be added to entities in the Primary Dimen-
sion/ Global Organization Hierarchy. Regardless of where the attachment was added, users from
both applications can see and open the attachments assuming the application owning the doc-
ument is available (i.e. the user has Microsoft Word to open .docx files).
In CM, attachments can be replaced rather than adding new ones/ deleting previous ones.
This feature has been added to AM (TeamAdmin) as the ‘Replace’ button. In addition the create
date, and Administrator that added the attachment is also displayed.

AM/CM Integration Guide 11

 Shared Users

Suite Level Role

CM does not use the Suite Level Role as security is structured slightly differently.
In TeamAdmin, this database change has resulted in the following:
l When editing users, it is now possible to search for users without a Suite Level Role.
l When editing a user that was added in CM (rather than AM), the Suite Level Role will be
empty and indicate that a role must be selected before proceeding in the wizard.

NOTE: If a user does not need access to any AM applications, the identification of a Suite
Role will never be prompted for UNLESS an Administrator attempts to edit the user
account in TeamAdmin. If adding a Suite Role is not desired, then ensure the user
account is edited in CM.

Security Logging
CM has functionality for security logging.
For consistency, the same functionality has been added to AM:
l Display last successful login date/time in user profile: This information is available in
TeamAdmin.
o Navigate to User Management.
o Navigate to Edit User.
o the “Last Login” field displays the last successful login date and time for the last AM
application accessed.

l Display log of logins for a user: This information is available in TeamAdmin.

o Navigate to User Management.

AM/CM Integration Guide 12

 o Navigate to Edit User.
o The “Access Log” tab provides information about the users' login details as their logon
time, logoff time and access count for each AM application.

This tab will be only available in TeamAdmin. The Access Log tab will be hidden when the dialog
displays in other applications.

AM/CM Integration Guide 13

 Shared Taxonomy (Terminology and Categories)
Terminology and Categories are to be individually configurable as shared or dedicated CM or AM.
For shared Terminology and Categories:
l AM will take precedence over CM when defining fields.
l If a field label (terminology) is visible by AM then CM cannot change the label but the field
can be used or hidden in CM.
l By default, a category value created in AM will not be visible to CM. It can be enabled by
checking the box to the left of the category label in CM Taxonomy:
o Navigate to CM Setup.
o Navigate to Taxonomy Categories.
l Category values used in CM cannot be deleted in TeamAdmin but they can be disabled in
the global list or in templates.
When a label (terminology) or category value is added, edited or deleted in TeamAdmin, the CM
cache is reset. For clarification, if CM is being used independent of AM, then all taxonomy can be
edited.
AM applications are not using CM specific terminology and category values by default; they are
hidden from AM applications in order to avoid confusion to AM users.
Additionally, there are additional terminology fields available for objectives, risks, controls, tests
and issues/recommendations in CM that are not available in AM to ensure that both disciplines
can have a reasonable set of fields in common and for individual application use.

AM/CM Integration Guide 14

 TeamMate Support
If you are experiencing any Technical difficulties, contact our Technical Support Hotline or send
us an email using the appropriate contact information below.
S uppor t N um-
R egion ber s E mail A ddr ess Fax
North America [1] 800 449 8112 TeamMateSupport@wolterskluwer.com [1] 800 878
9605
Central & South [1] 773 866 3180 TeamMateSupport@wolterskluwer.com [1] 813 675
America 6245
Europe, Middle +44 (0)20 7981 TeamMateSupport@wolterskluwer.com
East, Africa 0555
Australia 1 300 728 236 TeamMateSupport@wolterskluwer.com
Asia Pacific +800 224 00 224 TeamMateSupport@wolterskluwer.com
Southern Africa +27 11 797 5111 TeamMate.Support@za.pwc.com

AM/CM Integration Guide 15