Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

NOTE: The CAWIS release of April 2022 gave ADMIN users the ability to Alter existing User-ids under the following conditions :

  1. You cannot change a TC userid (user exists on TC-Directory -or- has an email domain tc.gc.ca)

  2. You cannot change a SYSID ( examples : ccarcsupd, CLIENT, AAIRRUN, AARDG ) A list of SYSIDs can be seen at (Select * from Z980_term_conversion where Term_type_cd = ‘SYSID’)

  3. The New USERID cannot ALREADY exist on A01_user

  4. You cannot change a USERID “BACK” to what it originally was on the same day. An old/previous Userid remains on the A01 table until its deleted by the overnight sync job (synchronize_ccarcs_cawis)deleted by the overnight sync job (synchronize_ccarcs_cawis)

  5. No special characters. Data_compression is applied to New Userid. (A THRU Z, 0 THRU 9 are the only values permitted)

  6. At present, User-id changes can only be performed via the CAWIS admin menu, not from the WSDRS User maintenance module

SITUATION #1 - WSDRS USERID CONFLICTS WITH TC USERID

The notes below are retained for backup purposes only. The function described in the introductory notes should be sufficient to perform any cleanups.

...

When an external WSDRS userid is found to conflict with the userid of a new TC employee (or anyone on TC directory) , the external Userid needs to be altered to have a numeric on the end (SMITHJ should become SMITHJ1 ) For now, this is a manual process - However, it should be available to the SDR manager on the side menu - as this comes up often - see Enhancements section. for example )

This procedure can also be used for a simple USERID change as well. Frequently the SDR submitters will request a change of userid when someone leaves a company, but many reports are tied into a given account.

...

UPDATE A01_USER SET PARTY_ID = NULL, ACTIVE_IND = 'N'
WHERE USER_ID =
(SELECT TRIM(FROM_TXT) FROM Z980_TERM_CONVERSION WHERE TERM_TYPE_CD = 'USERCHANGE') ;

commit;

SITUATION #2 - ELIMINATION OF INACTIVE WSDRS USERS

The query below identifies inactive WSDRS users having submitted SDR reports.

...

  1. move all SDR reports submitted by those users, under User #1  in each organization

  2. remove user from M79 table

  3. set the password for each user to DELETE on A01

The Overnight routines DELETE any external Userid where password is DELETE

...

  1. Any inactive external user who has never submitted a report, is auto-deleted already

  2. Reports submitted from inactive accounts are in a read-only state until transferred to an active account

  3. User #1 of any organization is always maintained as ACTIVE

...