|
|
Mapping users |
|
|
|
|
|
||
Mapping users |
|
|
|
|
|
|
|
|
Mapping users |
|
|
|
|
|
||
Mapping users |
|
|
|
|
|
|
Migrating an existing CaseMap or TextMap case to CaseMap Server is two-step process. First you import the existing case using the SQL Import Utility and then register the imported SQL case to the CaseMap Server using the CaseMap Admin Console. We recommend you set up CaseMap Server users with assigned roles in the CaseMap Admin Console before registering an imported SQL case. This process allows you to map users from the CaseMap or TextMap Case Staff Member list to users defined in the CaseMap Admin Console after case registration succeeds.
Once users are mapped in the CaseMap Admin Console, they should automatically be assigned to the case and able to open the case in CaseMap or TextMap. Users set up in the CaseMap Admin Console must match the user account in the client version of the local case (CaseMap > Tools > Manage Case Staff or TextMap > Tools > Case Staff). You can also add new users to the SQL case while mapping users. Click the New CaseMap Server User button to access the New User dialog box.
Mapping user considerations:
| • | If you do not map users after registering an imported case, this task can be completed later in the CaseMap Admin Console by selecting the SQL case, clicking the Action menu, and then clicking Map Case Staff Members. |
| • | If there are no non-mapped users, a message box displays stating that all users in the original case have been mapped. This message box will not display any CaseMap Server users that are already mapped to the case database. |
| • | If there are no users in the case when you register it, no message displays regarding whether to map users. If you right-click on the case without users, a message will display indicating that you need to assign users to a case. |
| • | The bottom list of mapped users remains empty and is only populated when you select a user combination and click the Map Users button. |
Example of the mapping user process:
Refer to the above graphic for the examples noted below.
| • | AttorneyC and ParalegalD are existing case staff that can be successfully mapped when an existing case is registered, because they already have user accounts set up in the CaseMap Admin Console. |
| • | InvestigatorF and LitigatorS are existing case staff that need user accounts set up in the CaseMap Admin Console before they can be mapped and access the new SQL case version. |
| • | SysAdmin and AttorneyD already have user accounts set up in the CaseMap Admin Console, but need to be assigned to the new SQL case, once it is registered, in order to access it. |
Or click on the Action menu and select Map Case Staff Members.
The user now displays in the Mapped users box.
New users added display in the Unmapped CaseMap Server users list so they can be mapped. For more information, see Creating users.
The mapped users can now access the SQL case version of this case. Remember to assign users to roles. See Creating roles. |
 |
