Changing a FootPrints User ID in version 11

Version 1
    Share This:

    This guide comes with no guarantees and user accepts all responsibility.

     

    workspace membership, license type, and roles

      1. System Administration > User Management > edit user > enter old id.
      2. Make note of workspace membership, license type, supervisor, and roles
      3. Add new user id with same properties found in previous step – assumption is new id will have different email address. If not, create user with temporary bogus email address

    Teams

      1. In every workspace, go to Administration > Workspace > Teams. Click link for popup summary of all teams.
      2. Make note of all teams containing old id.
      3. Add new id to all teams found in previous step. Set new id as team leader where old id is current team leader

    reassign tickets

      1. In every workspace, create an escalation rule to reassign tickets:
        1. Criteria:
          1. Assignees=old id
          2. Age=5 minutes
          3. Re-escalate=on
          4. Action:
            1. Assign to=new id

    "reassign" Requests

      1. In every workspace, create an escalation rule to update Requester:
        1. Criteria:
          1. Requester ID=old id
          2. Age=5 minutes
          3. Re-escalate=on
          4. Action:
            1. Change workspace fields > Requester ID =new id

    Submitted By DATA

      1. Connect to database with SQL Server Management studio
      2. For each workspace (MASTERx table) run

    update MASTER15

    set mrsubmitter = '<new id>'

    where mrsubmitter = '<old id>'

     

    Descriptions
    Updating association between description entries and user is prohibitively messy. The descriptions entered under old id will appear with "Entered by <old id>…" in their time stamps. This data is not tied to any functionality.

     

    HISTORY
    Updating ticket history (what you see on the History tab) is prohibitively messy. Some history entries will be attributed to <old id>. This data is not tied to any functionality.

     

    VOTING HISTORY

      1. Connect to database with SQL Server Management studio
      2. For each workspace (MASTERx_APPROVALVOTES table) run

    update MASTER15_APPROVALVOTES

    set mrVOTEUSER = '<new id>'

    where mrVOTEUSER = '<Old id>'

                   For each workspace (MASTERx_APPROVALVOTESHIST  table) run

    update MASTER15_APPROVALVOTESHIST

    set mrVOTEUSER = '<new id>'

    where mrVOTEUSER = '<Old id>'

     

    ASSIGNMENT HISTORY

      1. Connect to database with SQL Server Management studio
      2. For each workspace (MASTERx_ASSIGNMENT table) run

    update MASTER15_ASSIGNMENT

    set Assignee = '<new id>'

    where Assignee = '<Old id>'

     

    Time TRACKING DATA

      1. Connect to database with SQL Server Management studio
      2. For each workspace (MASTERx_TIMETRACKING table) run

    update MASTER15_TIMETRACKING

    set mrTIMEUSER = '<new id>'

    where mrTIMEUSER = '<Old id>'

     

    References by Escalations

      1. In every workspace, go to Escalations admin page. Click link to get summary of all escalations
      2. Find any References to Old ID by Escalations such as in criteria or actions
      3. Change escalations identified in previous step

     

    Auto-Assign rules

      1. In every workspace, go to Auto-Assign admin page
      2. Look for any rules that assign the old id
      3. Change rules identified in previous step to assign new id instead

     

    Auto-FIELD rules

      1. In every workspace, go to AutoField admin page
      2. Look for any rules that result in changing assignment of ticket.
      3. If any found, click Edit Rules button.
      4. Look for rules that assign old id.
      5. Change rules identified in previous step to assign new id instead

     

    Change Management

      1. In every workspace, go to Change Management admin page
      2. Open every phase
      3. Look for any instances where old id is specified as an approver, new assignee or notification recipient
      4. Change instances identified in previous step to new id

     

    Searches and reports

      1. On application server, open the \etc\SearchList file
      2. Search and replace old id with user id. This will reassign ownership of saved searches and reports
      3. On application server, open the \etc\Search file
      4. Search and replace old id with user id (be careful about old id possibly being found as a substring of some other string). This will fix any instances where old id is used as criteria for a saved search or report

     

    SUPERVISOR of Others

    This fixes any case where old id is supervisor of some other user

    1. Connect to database using SQL Server Management Studio.
    2. Run

    update user_profiles

    set supervisor_user_id = '<new id>'

    where supervisor_user_id= '<old id>'

     

    PERSONAL PREFERENCES

      1. User is responsible for setting own preferences to how they were with old id. Advise user to take screenshots of preferences page for reference.
      2. For homepage dashboard preference, admin can port these over by:
        1. Remote into server
        2. Go to FootPrintsServiceCore\db folder
        3. Run search for old id>
        4. For every result in the format of <old id>.txt found under a folder named "Homepage", rename file to <new id>.txt

     

    APPOINTMENTS

      1. Connect to database with SQL Server Management studio
      2. Port personal appointments to new id using
        update FPCalMain
        set calName = '<new id>'
        where calname = '<old id>'
      3. Find upcoming appointments where old id is invited using
        select * from FPCalMain
        where invitees like '%<old id>%' and stime > SYSDATETIME()
      4. Update invitees on appointments found in previous step either by opening each through web interface or using SQL

     

    CMDB SAVED Searches and other CMDB Activity, CMDB USER ROLES, etc.
    are not covered by this guide.

     

    Last editED by field on tickets is not covered by this guide

     

    Executive Dashboard personal settings are not covered.

     

    Personal Quick Descriptions are not covered

     

    BILLING RATES are not covered

     

    Custom Workspace Fields

      1. Any custom workspace fields holding old user id can be updated en masse using escalation rules
      2. For each custom workspace field that might contain the user id, create a new workspace escalation rule:
        1. Criteria:
          1. <custom field> = <old id>
          2. Age=5 minutes
          3. Re-escalate=on
          4. Action:
            1. Change workspace fields > <custom field>=<new id>

     

    Finally, Delete old ID

      1. Using Administration > System > User Management, delete old account.
      2. If new account was given a temporary email address, it can now be changed to correct email address