Cheatography
https://cheatography.com
Make updates to the digital forms and see them reflect on the New Account Opening wizard.
This is a draft cheat sheet. It is a work in progress and is not finished yet.
Update the Query Fields Worksheet
For Salesforce fields to be used and referenced in the digital platform, we need them to be queried from the Salesforce database. The exhaustive list of queries are stored in the Query Fields tab in the Configurations spreadsheet.
Add Suffix to the Financial Account Role query.
Connectors
So far, Suffix has been added to the Financial Account Role query in the Configurations sheet and to the appropriate layout in the Modules sheet.some custom UI level rules around Suffix has also been adjusted.
What connects what we see on NAO screen and the Salesforce schema? Connectors! |
Saving value from NAO screen into Salesforce field
To save the value enters by the Advisor in the Suffix field on the screen into the Suffix field on Financial Account Role, a Connector needs to be updated.
Based on the scenario, different Connector sheets are to be updated.
To save from NAO to FAR and given NF is the custodian in question, we will need to look at the mapNAOOwnerNF tab.
Loading the value from SF field into NAO screen
To load the field level value back to the NAO screen on edit of FA, a (reverse) Connector needs to be updated.
To load from FAR suffix field to NAO and given NF is the custodian in question, we will need to look at the mapFARoleToNAONF tab.
Prefilling values from Contact on Load of NAO
This requires update of a connector sheet to map values from the underlying Contact record associated with the role into the screen when NAO loads.
Given NF is the custodian in question, MapOwnerModulesNF is the sheet to be updated to prefill Suffix from Contact. |
|
|
A Note about Modules worksheets
Based on which screen you want the field in, different Modules sheets are to be updated..
For Account Instructions/Account Details screens and given NF is the custodian in question, NFS NAO worksheet is to be updated. |
A Note about Built-In functions
SKIF, SKAND, etc. are SKDP defined built-in functions. Refer to the Built-in spreadsheet in the google folder To see the exhaustive list of SKDP built-in functions and what each of them does.Your own built-in functions can be written on separate worksheets of the Built-In spreadsheet if your implementation demands it. |
A Note on Picklists tab of Modules
Note on Saving to JSON versus Discrete Field
Which Connector to update when also depends on whether the screen value is being saved into/loaded from the actual field or from the Json Long Text field present in the object. |
Note on Orchestrations
Orchestrations are a collection of Modules.
Orchestrations are updated at the beginning of each impementation to bring up a bundle of screens specific to the product company.
If any new screen is to be added, the orchestrations will have to be updated with the newly added screen.
More about Orchestrations sheet |
Note on Components
Components sheet defines all the UI components used in Modules. Eg: sk-inputtext.
Our own Components can be defined if our implementation demands it. |
|