Usage: Search and replace COMMUNITY_ID
Search and replace
COMMUNITY_NAME
Search and replace billing
abbrev
Adjust descriptions as needed
and follow instructions
--*** DEVELOPMENT
1. Select from FC_OBJ_OWNER.COMMUNITIES table to
identify community for name, abbrev change.
select * from COMMUNITIES where lower(COMMUNITY_NAME)
like '%providence%';
2. Update FC_OBJ_OWNER.COMMUNITIES table -
COMMUNITY_NAME, KB_USERNAME columns.
update COMMUNITIES set COMMUNITY_NAME = 'American House
Wildwood', KB_USERNAME = 'help.ahw' where community_id=670;
commit;
3. Update FC_OBJ_OWNER.TERMINALS table -
TERMINAL_DESCRIPTION column.
select * from terminals where community_id=670;
update terminals set description = 'American House
Wildwood Station 1' where serial_number = '5M43792';
update terminals set description = 'American House
Wildwood Station 2' where serial_number = '5M43792';
update terminals set description = 'American House
Wildwood Salon' where serial_number = '5M43791';
update terminals set description = 'American House
Wildwood Bar' where serial_number = '5M43702';
update terminals set description = 'American House
Wildwood' where serial_number = '5M63255';
commit;
4. Update FC_OBJ_OWNER.USER_PROFILES table -
USER_NAME column for existing internal application users.
select * from USER_PROFILES where DEFAULT_COMMUNITY_ID =
670 and ACCOUNT_STATUS = 'A' and substr(USER_NAME, instr(USER_NAME, 'pi', 1),
length(USER_NAME) - instr(USER_NAME, 'pi', 1) + 1) = 'pi';
select 'update USER_PROFILES set user_name = ''' ||
substr(USER_NAME, 1, instr(USER_NAME, 'pi', 1) - 1) || 'ahw'' where
DEFAULT_COMMUNITY_ID = 670 and ACCOUNT_STATUS = ''A'' and USER_PROFILE_ID = '
|| USER_PROFILE_ID || ';' from USER_PROFILES where DEFAULT_COMMUNITY_ID = 670
and ACCOUNT_STATUS = 'A' and substr(USER_NAME, instr(USER_NAME, 'pi', 1),
length(USER_NAME) - instr(USER_NAME, 'pi', 1) + 1) = 'pi';
5. Update FC_OBJ_ADMIN.COMMUNITIES table -
COMMUNITY_NAME columns.
select * from COMMUNITIES where lower(COMMUNITY_NAME)
like '%providence%';
update COMMUNITIES set COMMUNITY_NAME = 'American House
Wildwood' where COMMUNITY_ID = 670;
commit;
6. Update FC_OBJ_ADMIN.COMPUTERS table -
DESCRIPTION column.
select * from computers where community_id=670;
update computers set description = 'American House
Wildwood - Primary Server' where serial_number = 'VMware-56 4d 34 ae 83 5d 58
fa-5f 27 3a 94 8f 4c 48 43';
update computers set description = 'American House
Wildwood Bar' where serial_number = '5M43702';
update computers set description = 'American House
Wildwood Salon' where serial_number = '5M43791';
update computers set description = 'American House
Wildwood Station 2' where serial_number = '5M43793';
update computers set description = 'American House
Wildwood Station 1' where serial_number = '5M43792';
update computers set description = 'American House
Wildwood' where serial_number = '5M63255';
commit;
7. Update FC_OBJ_ADMIN.HOST_LOCATIONS table - NAME,
TS_URL columns if community is remotely hosted.
a. Update NAME column.
select * from HOST_LOCATIONS where lower(NAME) like
'%providence%';
--0 rows
update HOST_LOCATIONS set NAME = '' where
HOST_LOCATION_ID = ?;
commit;
b. If community determines they would like to
update URL for remote application(s), the following items need to be completed.
i. Update Tracker on FC - Support splash
page under Server - Network Info (Host Location URL).
ii. New SSL cert.
iii. Coordinate DNS change with community/local IT.
iv. Coordinate URL change on local machines for
Back Office users.
v. Coordinate restart for remote devices
(TS,tablet,KDS,Print Server) to use new URL
c. If community determines they would like to
update URL for remote application(s), the TS_URL column will need to be
updated.
-- Generate a "community code" (an abbreviation
that is used for Resident Portal redirect rules) for communities in
COMMUNITY_CONFIG that do not already have a community code.
-- CMS_CODE column is the recommended abbreviation based
on COMMUNITY_NAME column in COMMUNITIES table.
-- CC_CODE column is the current value from the
COMMUNITY_CODE column in COMMUNITY_CONFIG table.
select cms.community_id,
lower(regexp_replace(community_name,
-- Remove the words "at", "of", and
"the".
'((^| )([Aa]t|[Oo]f|[Tt]he|[Cc]ommunity| )*)', null)
cms_code, length(lower(regexp_replace(community_name,
-- Remove the words "at", "of", and
"the".
'((^| )([Aa]t|[Oo]f|[Tt]he|[Cc]ommunity| )*)', null)) )
length, cc.community_code cc_code
from
communities cms
join community_config cc on
cms.community_id = cc.community_id(+)
where cc.community_id=670;
--Update row in HOST_LOCATIONS table with TS_URL built
from output from above query.
commit;
8. Resident Portal changes
a. Update FC_OBJ_OWNER.DEPARTMENT_EMAIL_ADDRESSES
table - EMAIL_ADDRESS column.
select * from DEPARTMENT_EMAIL_ADDRESSES where
COMMUNITY_ID = 670;
--0
update DEPARTMENT_EMAIL_ADDRESSES set EMAIL_ADDRESS = ''
where EMAIL_ADDRESS = '' and COMMUNITY_ID = 670;
commit;
b. Update FC_OBJ_ADMIN.COMMUNITY_CONFIG table -
COMMUNITY_CODE column.
i. If we change COMMUNITY_CODE column and community
uses Resident Portal, we need to coordinate with community:
1. If they do want to change URL, we just need to
change in COMMUNITY_CONFIG table.
2. Do they also want to change graphics in the
event the community logo has changed?
--Identify row for community in COMMUNITY_CONFIG table.
select * from FC_OBJ_ADMIN.COMMUNITY_CONFIG where
COMMUNITY_ID = 670;
-- Generate a "community code" (an abbreviation
that is used for Resident Portal redirect rules) for communities in
COMMUNITY_CONFIG that do not already have a community code.
-- CMS_CODE column is the recommended abbreviation based
on COMMUNITY_NAME column in COMMUNITIES table.
-- CC_CODE column is the current value from the
COMMUNITY_CODE column in COMMUNITY_CONFIG table.
select cms.community_id,
lower(regexp_replace(community_name,
-- Remove the words "at", "of", and "the".
'((^| )([Aa]t|[Oo]f|[Tt]he|[Cc]ommunity| )*)', null)) cms_code,
length(lower(regexp_replace(community_name,
-- Remove the words "at", "of", and "the".
'((^| )([Aa]t|[Oo]f|[Tt]he|[Cc]ommunity| )*)', null)) ) length,
cc.community_code cc_code
from
communities cms
join community_config cc on
cms.community_id = cc.community_id(+)
order by cms.community_id desc;
update FC_OBJ_ADMIN.COMMUNITY_CONFIG set COMMUNITY_CODE =
'' where COMMUNITY_ID = 670;
9. Update Username Community Suffixes located on
the J drive under FC - Implementations, J:\FullCount\FC - Implementations.
10. Update directory names under J:\FullCount\FC -
Implementations.
11. Verify information changed on FullCount
Customers Google map.
b. User must have pre-approved access via Google to
access it.
12. Update community information on KB under the
article Community Names and Abbreviations.
13. Update Username and E-mail address for kb user
on help.fullcount.net.
a. Accessible under People page.
14. Update community id and community abbreviation
in Tracker.
a. Organization page
i. Set Billing Abbreviation.
ii. Set old name as a Search Alias.
iii. Add Persistent Notes to explain history of
change.
iv. Set Parent Organization (If the
management company has changed as part of the name change).
b. FC - Support splash page
i. Set Community Login Abbreviation.
ii. Set Management / Owner Info (If the
management company has changed as part of the name change).
c. People page
i. Update information for contacts if these
have changed (domain for e-mail, for example).
--*** SYSTEMS
15. Update name in Ansible and any other Systems
scripts.
a. Be sure script name changed under
/srv/ansible/inventory/group_vars/ on fcadmin01.
--*** SUPPORT
16. Update DEFAULT_USERNAME and DEFAULT_PASSWORD
under TERMINALS page in Back Office.
17. Update MODE_DESCRIPTIONS under MODES page in
Back Office.
--*** COMMUNICATION
18. Send internal communication to make sure change
is coordinated with Sales and Accounting.
19. Send external communication to make sure end
users are aware of changes.
a. New Help user.
b. New community name on receipts, etc.