1. Introduction
This document summarizes the steps required for post-installation of the Smart Onboarding product. These steps must be completed by all Smart Onboarding customers that will run the Smart Onboarding application on their premises.
NOTE: This document contains screenshots taken from tools release 8.56.03. So some screens may significantly vary from your current tools in appearance
Intended Audience
This document is intended primarily for those involved in setting up the system. A basic familiarity with PeopleSoft admin and web-based applications is expected.
2. Post-installation Steps
a) Deployment Options, Global Variables Sequencing setup and Web Profile Time Out
i) Navigate to Main Menu > Smart Solutions > Common Utilities > Core Setup > Installation > Installation Options
Ensure the Deployment Mode is set to "On-Premise" and Phase as "Development/Configuration/Staging" etc depending on your installation environment and with the HR Data in Sync box checked.
Click Save.
ii) Navigate to Main Menu > Smart Solutions > Common Utilities > Core Setup > Installation > Maximum Sequence Setup
Click on '+' button to add a row and add the variable SM_CO_GBL_VAR for CO product id and provide a high number as shown. This is to prevent collision with already delivered Global Variables along with installation/migration.
iii) Navigate to Main Menu > PeopleTools > Web Profile > Web Profile Configuration
a) Pull up SMINT/SMEXT Web Profiles one by one and change the Time Out Warning Script by clicking 'Override' button
Record (Table) Name: WEBLIB_SM_CO
Field Name: SM_TIMEOUTWARNING
PeopleCode Event Name: FieldFormula
PeopleCode Function Name: IScript_TIMEOUTWARNING
b) SMEXT Web Profiles after overriding with SmartERP's parameters
b) Creation of Roles and User IDs
1) Creation of new Roles (If they are not already delivered by SmartERP) with the permission lists shown in the below table.
NOTE: These permission lists may be changed in future as functionality is changed and will be updated here as we change
Roles | Permission Lists |
---|---|
Cloud Login | SMCD5010, SMCD6010, SMCD7010 |
Smart User | SMCD6005, SMCD_PTPT1000, SMCD_PTPT1200 |
Cloud New Hire | SMCD3062, SMCD4062, SMCD5062, SMCD6062, SMCD7062, SMCD8062 |
Illustration of Smart User role creation
2) Creation of new Users (If they are not already delivered by SmartERP)
Users | Roles |
---|---|
INVITEE (This was created in Pre-Installation phase) | Cloud Login, Smart User |
MODELCLOUDUSER | Smart User |
SmartNewHire | Cloud New Hire, Smart User |
Assign the roles from the above table to the INVITEE User which was created earlier.
Create a PeopleSoft User with User ID “MODELCLOUDUSER” as shown below and this user can be locked (Check Account Locked out).
Role(s) creation for MODELCLOUDUSER. In the ID tab assign ID as 'NONE' (Not shown in the figure).
Creation of new User 'SmartNewHire'.
Role assignment for the newly created user. In the ID tab assign ID type as NONE (Not shown in the figure).
c) Import Message Catalogs
Navigate to Main Menu > Smart Solutions > Common Utilities > Utilities > Import Message Catalogs.
Select all the messages and import the messages by clicking the Import button.
Ignore the initial warning that pops up and click OK.
If you get the message shown below that the messages are in use, click OK.
d) Sync Prefix & Suffix CO tables with delivered HR tables data
Please find the script given below to sync data between tables:
DELETE FROM PS_SM_CO_NAME_PRF;
DELETE FROM PS_SM_CO_NAME_SUF;
%InsertSelect(SM_CO_NAME_PRF A,NAME_PREFIX_TBL B) FROM PS_NAME_PREFIX_TBL B;
%InsertSelect(SM_CO_NAME_SUF A,NAME_SUFFIX_TBL B) FROM PS_NAME_SUFFIX_TBL B;
INSERT INTO PS_SM_CO_NAME_PRF (NAME_PREFIX , DESCR , DESCRSHORT) SELECT B.NAME_PREFIX , B.DESCR , B.DESCRSHORT FROM PS_NAME_PREFIX_TBL B;
INSERT INTO PS_SM_CO_NAME_SUF (NAME_SUFFIX , DESCR , DESCRSHORT) SELECT B.NAME_SUFFIX , B.DESCR , B.DESCRSHORT FROM PS_NAME_SUFFIX_TBL B;
Note: For Gender and Marital Status, we are using the delivered fields.
Gender:
In Smart Onboarding product, we are using delivered field (SEX) for gender and no customization has been made in any of the activities.
Marital Status:
For Marital Status, we are using delivered field "MAR_STATUS". However, we have a customization in the Employee Biographic Information to hide all the xlats except S(Single) and M(Married) values.
Note: In case, there is any other requirement on Marital Status, please reach out to us for customization.
e) Create Organization and add first System Administrator
i) Create your Organization
Note: Please provide 'Cloud Service Provider' role to the user who will be performing this task.
Navigate to Main Menu > Smart Solutions > Organization > Consoles/Review and then click on Service Provider Console.
Note: Note that prior to adding your Organization you must have an Internal user who you would want to designate as a Tenant Administrator.
Click Smart ORG-Invite push button to create your own Organization that you will be using for utilizing Smart Modern Onboarding product.
Add new Org details and click Save.
ii) Setup System Administrator roletype
Navigate to Main Menu > Smart Solutions > Cloud Foundation > Core Setup > Organization Specific Setup > Invite/Edit Tenant User.
For the organization you have created add System Administrator.
iii) Navigate to Main Menu > People Tools > Security > User Profiles > User Profiles
Go to the respective User Profile SMART_APPLICANT_<Org Number> where Org Number is the value saved above and associate the below role names to it.
- Cloud New Hire
- Smart User
f) Setup Organization Site Details, User Categories and URL Identifiers
i) Organization Site Details
Navigate to Main Menu > Smart Solutions > Organization > Core Setup > Organization Site Details.
When you click search, the organization that you have created in the above step will be listed in the ‘Find an existing value’ tab.
Update the Host name and the site name for Classic URL’s highlighted below to map the correct Host Name, port and node of the model entity. Host name could be a sample name along authentication domain following your DNS entry standards.
ii) User Categories
Navigate to Main Menu > Smart Solutions > Business Process Management > Core Setup > User Categories
This is system maintained and you need not add any new user category.
Select CLD_ROLETYPE_CUST, EXTERNAL_USER, SM_CO_USER and SMART_EV_USER user categories for the On-Premise installations and click on Organization Specific Portals link against them to open the organization specific details. For the organization ID created, adjust the site name with the new DNS that you have given in Org. Site details.
Click on Organization Specific Portals link against CLD_ROLETYPE_CUST to open the organization specific details to adjust site name for the delivered organization.
This will be used to provide appropriate navigations links to your own organization(s) that you create later and will help provide the system with accurate links to traverse between various activities when users are going through onboarding or when HR users are performing post onboarding activities for the users using Modern UI pages
Please Note that this is for HR Internal user navigation links and site name you have to provide is the Internal Modern site you created in the Pre-Installation phase.
Click on Organization Specific Portals link against EXTERNAL_USER to open the organization specific details to adjust site name for the delivered organization.
This is used by the system to provide accurate navigational link for external candidates being onboarded.
Click on Organization Specific Portals link against SM_CO_USER to open the organization specific details to adjust site name for the delivered organization.
This is used by the system to provide accurate navigational link for the tenant users through their onboarding activity after self registration.
Click on Organization Specific Portals link against SMART_EV_USER to open the organization specific details to adjust site name for the delivered organization.
This is specific to Smart I-9 product and is used by the system to provide accurate navigational links for the New Hires being onboarded.
iii) Setup the URLs
Below are the URLs that you need to setup.
Navigate to People Tools > Utilities > Administration > URLs.
URL1: Search for URL Identifier = SM_AUTH_SSO_LOGIN_URL.
URLID: Enter the traditional URL that you used to login to this environment.
URL2: Search for URL Identifier = SM_AUTH_INTERNAL_SITENAME.
Update the highlighted URLID and Comments.
The value to enter in the URLID field is the ‘Internal Site name’ that you have created for onboarding. Comments is optional and it is for your reference.
URL3: Search for URL Identifier = SI9_NFS_MOUNT_URL.
Check to make sure the path to the temp directory is entered in the URLID. Update the URLID field if the value doesn't exist.
After the setup is done, navigate to Main Menu > Smart Solutions > Smart Modern UI Landing Page. This should take you to your onboarding landing page.
g) Configure Authentication for Candidates (PeopleSoft User signon using bypass site)
Navigate to PeopleTools > Security > SecurityObjects > Signon PeopleCode.
1) Set Invoke as user to an active PeopleSoft User ID.
2) You would by default see Sequence Number 1 as Record: FUNCLIB_PWDCNTL. Change that to any number after 7 and Save, eg: 11 as shown in the screenshot below.
3) Now add Sequence Number 1 on the top and add the below. Ensure that FUNCLIB_SM_AUTH is sequentially first as shown in the screenshot below.
Record: FUNCLIB_SM_AUTH
Field Name: LDAPAUTH
Event Name: FieldDefault
Function Name: SMSSO_AUTHENTICATION
Check the Enabled and Exec Auth Fail check boxes.
h) DHS Client Setup
DHS Client Setup is used to set up the user and password information for accessing the USCIS E-Verify system. If you are not planning on using E-Verify through our smart onboarding process, this step is not needed.
Navigate to Main Menu > Smart Solutions > Smart Modern UI Landing Page.
Login as 'System Administrator' and access DHS Client Setup through left navigation.
Click on Add a New Value.
Set DHS User ID and Password for the Legal Entity Driver chosen for processing the I-9s. Here, Business Unit is chosen as the I-9 Legal Entity Driver.
Select the Business Unit. Enter the DHS User ID and the Password that is registered in the DHS Site.
Save the page. Click on Verify Connectivity to ensure the connection works correctly.
Likewise, create one row each for all the Business Units that are associated with your Organization.
i) Check PS URLs for E-Verify
Check to make sure the PS URLs for E-Verify is pointing to Version 30. Update the URLIDs if not correctly pointing to the corresponding environments.
SM_I9_PRODUCTION URL should point to Version 30 of the DHS production URL and SM_I9_TEST_URL should point to Version 30 of the DHS test URL.
Navigate Main Menu > PeopleTools > Utilities > Administration > URLs.
Production Environment:
Search for URL Identifier = SM_I9_PRODUCTION_URL.
Make sure the highlighted URLID field has the value "https://everify.uscis.gov/api/v30/soap/cases/action".
Otherwise, update the URLID with the link given above.
Non-Production Environment:
Search for URL Identifier = SM_I9_TEST_URL.
Check to make sure the URLID field has the value "https://stage-everify.uscis.gov/api/v30/soap/cases/action".
Otherwise, update the URLID with the link given above.
Change the URLs in Routings:
Change the URLs in the following three Routings to point their Connector Properties URL to v30.
- SCANANDUPLOAD
- DOWNLOADFURTHERACTIONNOTICE
- DOWNLOADREFERRALDATECONFIRMATI
Navigate Main Menu > PeopleTools > Integration Broker > Integration Setup > Routings.
SCANANDUPLOAD
Search for the Routing Name = SCANANDUPLOAD.
Select "Connector Properties" tab and enter the value in PRIMARYURL field.
Depending on the environment (production and non-production) that you are working in, make sure you have entered the right value in PRIMARYURL field.
The value to enter in production environment is "https://everify.uscis.gov/api/v30/soap/cases/action" and non-production environment "https://stage-everify.uscis.gov/api/v30/soap/cases/action".
DOWNLOADFURTHERACTIONNOTICE
Search for the Routing Name = DOWNLOADFURTHERACTIONNOTICE.
Select "Connector Properties" tab and enter the value in PRIMARYURL field.
Depending on the environment (production and non-production) that you are working in, make sure you have entered the right value in PRIMARYURL field.
The value to enter in production environment is "https://everify.uscis.gov/api/v30/soap/cases/action" and non-production environment "https://stage-everify.uscis.gov/api/v30/soap/cases/action".
DOWNLOADREFERRALDATECONFIRMATI
Search for the Routing Name = DOWNLOADREFERRALDATECONFIRMATI.
Select "Connector Properties" tab and enter the value in PRIMARYURL field.
Depending on the environment (production and non-production) that you are working in, make sure you have entered the right value in PRIMARYURL field.
The value to enter in production environment is "https://everify.uscis.gov/api/v30/soap/cases/action" and non-production environment "https://stage-everify.uscis.gov/api/v30/soap/cases/action".
j) Check Remote Database access
Navigate to Main Menu > PeopleTools > Utilities > Administration > Remote Database Connection
Check the setup for Remote Database access and make changes if settings are incorrect. Make sure the "Local Connect?" checkbox is checked.
Click on "Test Connection" to verify the User ID and Password setup.
k) Report Category
Navigate to Main Menu > Reporting Tools > BI Publisher > Setup > Report Category
Ensure you have the “Smart User” Security ID assigned as shown below for Report Category ID: ALLUSER
Click Save.
l) EOCF Install Options
Navigate to Main Menu > Enterprise Components > Active Analytics Framework > Setup > Install Options
Ensure that Only “Enable Runtime” Checkbox is checked with Log File Name Prefix EOCF.
Click Save.
m) Migrate the SmartERP Customization Code
Customizations that are needed for the Document Framework are listed below. The code given below for each of the customization has to be placed in the path mentioned.
1) To build tree structure for the policies in a given trigger point
Path: EOCF_CLF_RB:UI:ManageTriggerPoint
Method: ManageTriggerPoint
Code:
/*Smart ERP Customization Begin*/
If %Component = "SM_DF_MANAGE_TP" Then
&iPageName = Page.SM_DF_MANAGE_TP;
End-If;
/*Smart ERP Customization End*/
2) To access term value even with the spaces in it
Path: EOCF_CLF_DL:Contexts:CtxVarTerm
Property: get isString
/*SmartERP Customization Begin*/
/* Alpha numeric is returning false for the string that has spaces, so commenting IsAlphaNumeric and returning false*/
Return True;
rem Return IsAlphaNumeric(%This.CtxTermOverrideValue);
/*SmartERP Customization End*/
3) To add the property “Context Variable” in the results structure for identifying or for processing all types of the context variables
Path: EOCF_CLF_DL:Runtime:Results:DataLibraryResultStructure
Added property “DataLibraryResultStructure” in the interface.
Code1:
/* SmartERP Customization Begin*/
import EOCF_CLF_DL:Contexts:ContextVariable;
/* SmartERP Customization End */
Code2:
/* SmartERP Customization Begin */
property EOCF_CLF_DL:Contexts:ContextVariable objContextVariable;
/* SmartERP Customization End */
4) To retrieve the context variable for all the term types like Rowset, Record, Field
Path: EOCF_CLF_DL: Runtime: AccessMethods:AccessMethodCtxVar
Method: Process
Code1:
/* SmartERP Customization Begin*/
&oResults.objContextVariable = &oCtxVar;
/* SmartERP Customization End */
Code2: /* SmartERP Customization Begin*/
&oResults.objContextVariable = &oCtxVar;
/* SmartERP Customization End */
Code3:
/* SmartERP Customization Begin*/
&oResults.objContextVariable = &oCtxVar;
/* SmartERP Customization End */
5) To access the property ContextVariable as Field
Path: EOCF_CLF_DL:Runtime:Results: ResultsField
Method: ResultsField
Code1:
/* SmartERP Customization Begin*/
import EOCF_CLF_DL:Contexts:ContextVariable;
/* SmartERP Customization End*/
Code2: Class ResultsField
/* SmartERP Customization Begin */
property EOCF_CLF_DL:Contexts:ContextVariable objContextVariable;
/* SmartERP Customization End */
Code3:
Method: ResultsField
/* SmartERP Customization Begin*/
%This.objContextVariable = Null;
/* SmartERP Customization End */
6) To access the property ContextVariable as Record
Path: EOCF_CLF_DL:Runtime:Results:ResultsRecord
Code1:
/* SmartERP Customization Begin */
import EOCF_CLF_DL:Contexts:ContextVariable;
/* SmartERP Customization End*/
Code2: Class ResultsRecord
/* SmartERP Customization Begin */
property EOCF_CLF_DL:Contexts:ContextVariable objContextVariable;
/* SmartERP Customization End */
Code3:Method ResultsRecord
/* SmartERP Customization Begin */
%This.objContextVariable = Null;
/* SmartERP Customization End */
7) To access the property ContextVariable as Rowset
Path: EOCF_CLF_DL:Runtime:Results:ResultsRowset
Method: ResultRowset
Code1:
/* SmartERP Customization Begin */
import EOCF_CLF_DL:Contexts:ContextVariable;
/* SmartERP Customization End */
Code2:Class ResultsRowset
/* SmartERP Customization Begin */
property EOCF_CLF_DL:Contexts:ContextVariable objContextVariable;
/* SmartERP Customization End */
Code3:Method ResultsRowset
/* SmartERP Customization Begin*/
%This.objContextVariable = Null;
/* SmartERP Customization End */
8) To access the buffer rows irrespective of the buffer change
Path: EOCF_CLF_DL:Contexts:CtxVarCBuffer
Method: addRowsToCollection
/*SmartERP Customization Begin*/
%This.CollectionRows.Push(&rw1);
&iCount = &iCount + 1;
/*SmartERP Customization End*/
/*SmartERP Customization Begin*/
/*If &rw1.IsNew And
Not &rw1.IsChanged Then
Else
%This.CollectionRows.Push(&rw1);
&iCount = &iCount + 1;
End-If;*/
/*SmartERP Customization End*/
9) To retrieve scroll path for the online component access the property ContextVariable as Rowset
Path: EOCF_CLF_DL:Utility: ScrollPath
Method: ScrollPath
Code1:
/*SmartERP Customization Begin */
try
/*SmartERP Customization Ends */
Code2:
/*SmartERP Customization Begin */
catch Exception &e
end-try;
/*SmartERP Customization -- Ends */
10) Start page customization in the record field
This will avoid the errors caused by the invalid characters being assigned/converted after passing the URL text.
Copy the below code snippet in record field WEBLIB_PTBR.ISCRIPT1.FieldFormula in the Function IScript_StartPage.
/* SmartERP Customization Start */
If (%OperatorId = "INVITEE" Or
%OperatorId = "REGISTER") And
%Portal = "SMART"
rem And
%Node = "ONBRD";
Then
Local string &sURLParams = %Request.QueryString;
Local array of string &tokens = Split(&sURLParams, "URL=");
Local integer &i;
If &tokens.Len = 2 Then
rem %Response.RedirectURL(Unencode(&tokens [2]) | "&httpredirect=true");
%Response.RedirectURL(Unencode(&tokens [2]));
Return;
End-If;
End-If;
/* SmartERP Customization End */
11) Customization specific to PeopleTools 8.55 and below
This will avoid the errors caused by the special characters in field values while updating the value into the target component.
Class Name: EOCF_CLF_DL:Runtime:Results:ResultsScalar
Method Name: getResultValue
Before Customization:
Adjust the logic as below:
12) HR Customizations
i) The following customization is needed to avoid issues during CI push for future dated transactions
Remove EFFDT condition with %CurrentDateIn
ii) Add the code in the below given record fields to bypass the execution of the PeopleSoft code during CI push.
STATE_TAX_DATA.RESIDENT.FieldFormula
If /***** SmartERP Customization - Start *****/(
/***** SmartERP Customization - End *****/
%Menu = MenuName."MAINTAIN_PAYROLL_DATA_(USF)" Or
%Menu = MenuName."MAINTAIN_PAYROLL_DATA_US" Or
%Menu = MenuName."MAINTAIN_PAYROLL_INTERFACE" /***** SmartERP Customization - Start *****/) And
Not Substring(%CompIntfcName, 1, 6) = "SM_OB_"
/***** SmartERP Customization - End *****/
Then
STATE_TAX_DATA.UI_JURISDICTION.FieldFormula
If /***** SmartERP Customization - Start *****/(
/***** SmartERP Customization - End *****/
%Menu = MenuName."MAINTAIN_PAYROLL_DATA_(USF)" Or
%Menu = MenuName."MAINTAIN_PAYROLL_DATA_US" Or
%Menu = MenuName."MAINTAIN_PAYROLL_INTERFACE" /***** SmartERP Customization - Start *****/) And
Not Substring(%CompIntfcName, 1, 6) = "SM_OB_"
/***** SmartERP Customization - End *****/
Then
iii) Add the code in the following record field to restrict selecting only Work State for UI Jurisdiction.
/* If more than 1 state has been assigned UI Jurisdiction, error */
If %CompIntfcName = "CI_TAX_DATA" /***** SmartERP Customization - Start *****/ Or
Substring(%CompIntfcName, 1, 6) = "SM_OB_"
/***** SmartERP Customization - End *****/
Then
n) PeopleTools 8.58 Customizations
- Corrects a search category display issue seen while using the Elastic Search.
Path:PTS_NUIL:SearchResultGrid
Method: RefreshList
/* SmartERP 8.58 Fix for %3 Substitutions , swap %3 and %2 substitutions */
&sTitle4Val = Substitute(&sTitle4Val, "%3", &srchRslt.Title);
&sTitle4Val = Substitute(&sTitle4Val, "%2", &sNewUrl);
/* SmartERP 8.58 Fix End */
o) Build Cache (sm_df_cache)
Navigate to Main Menu > People Tools > Process Scheduler > System Process Requests.
Create a Run Control ID and run the SM_DF_CACHE (Build Cache) process.
Create a Run Control ID and run the SM_DF_CACHE (Build Cache) process.by picking it from a list of processes as shown below and clicking OK.
p) Maintain Cache
Navigate to Main Menu > Enterprise Components > Active Analytics Framework > Setup > Maintain cache.
Ensure "Check Synchronization" is selected and all options are chosen, as shown below. Click on the "Examine Cache" button and it will launch the process. Ensure the process runs to a successful completion.
Once the process runs to Success, click on the Results tab.
Make sure the Invalid Cache Entries are 0. If not zero, run the process again by clicking on Examine Cache again. Ensure you validate it is all 0’s before moving on. For example, DEV and TEST may take 2 times.
Once the above process has completed successfully, re-run the process using the following options. Please notice the “Bulk Load” option is now selected and the "Check Synchronization" option is not selected. The "Examine Cache" button will launch the process. Ensure the process runs to a successful completion.
q) Refresh SJT_OPR_CLS
Navigate to Main Menu > Setup HCM> Security > Core Row Level Security > Refresh SJT_OPR_CLS
Run the SJTOPCLS Process with Refresh All Rows checked and click OK. This Process is a standard security process that all PeopleSoft HCM clients run when ever new users are added/changed. So please keep that in mind and run as many times as you need.
Ensure the process goes to success.
r) Run Portal Security Sync
Navigate to Main Menu > PeopleTools > Portal > Portal Security Sync
Click Add button and add a new run control and add any valid run control id and run the process for All Portals with delete invalid security turned on.
s) Service Operations
Navigate to Main Menu > PeopleTools > Integration Broker > Integration Setup > Service Operations
Security Instructions:
Go to the navigation and regenerate the routings by selecting "Regenerating Local to Local" highlighted below for the "two" service operations listed below.
- SM_OB_IB_APPLICANT_DTLS_ASYNC
SM_OB_IB_APLCNT_CALLBACK_ASYNC
t) Assign Branding Themes
Navigate to PeopleTools → Portal → Branding → Assign Themes, Change to SMART portal, make sure below setup are available.
u) Disable IDCS event in Provider Setup
Navigate to Main Menu > Smart Solutions > Cloud Foundation > Core Setup > Global Setup > Provider Definitions
The Provider Definitions page displays as below.
Search for "ORACLE_IDCS" Provider ID. Click on the Provider ID link in the search results.
Click on "Define URLs".
You will notice the Request Types as shown below. Change Request Type "IDCS_ENABLED" to "FALSE".
If that row doesn’t exist then you should add a row with the exact Request Type name = "IDCS_ENABLED" and then set URLs value to "FALSE". Click OK and save the settings.
v) WebLogic settings when modern UI is not rendering some multibyte ASCII characters
Note: This setup must be used only when you encounter issue with ASCII character rendering otherwise default settings should used.
Append -Dfile.encoding=utf8 to JAVA_OPTIONS parameter corresponding to platform webserver is hosted on in serEnv.sh file.
Example : On Linux platform
Original Value looks similar to this,
JAVA_OPTIONS_LINUX="-server -Xms1024m -Xmx1024m -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"
Modify it append encoding,
JAVA_OPTIONS_LINUX="-server -Xms1024m -Xmx1024m -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dfile.encoding=utf8 "
This change requires a webserver bounce to be effective.
w) Sync SmartERP attributes with HR data (Business Unit, Company, Department, Location, Job Code)
Step 1) Navigate to Main Menu > Smart Solutions > Cloud Foundation > Utilities > Sync PeopleSoft HR Data
Create a new Run Control ID and choose the HR attributes that need to be synced to SM Attributes tables and run the process. Make sure process runs to a success in the Process Monitor.
Note: Run the above process twice in case if all attributes are not synced when the AE is run first time.
The attribute sync is required only
- if the value has to be used for configuring route criteria or branding
- if the Homepage has to be configured different for HR attributes like BU, Company, Department, Location and Job Code.
x) Set up attributes related to invitation in Attribute Preferences
Click on "Configure Attribute Preferences" link to access Attribute Preferences through Process Revision.
In Attribute Preferences, uncheck Invitation Field for all attributes. Attributes that are listed here but not present on the invitation creation page, can be added to the invitation by selecting them here and marking as required. Also for such attributes, if the values are not synced from HR tables, then the values need to be defined through Attribute Revisions.
Note: Please ignore the CJD column on this page even if the fields are enabled. The CJD column has no significance for on-prem implementation as the page configured for on-prem is different. If any changes need to be made to the CJD page, then please approach SmartERP for customization.
3. Final Note
After doing all the post installation steps reboot the web server (both external and internal) and app server by deleting cache.