Modification to Services to process Datetime and add error toast
This commit is contained in:
1 parent
a33604b498
commit
26423a7f33
5 files changed
+77
-28
No files matched your search
@@ -1,18 +1,44 @@
|
||||
# Salesforce DX Project: Next Steps
|
||||
# Smart Clone - Opportunity Cloner
|
||||
|
||||
Now that you’ve created a Salesforce DX project, what’s next? Here are some documentation resources to get you started.
|
||||
The purpose of the Smart Clone is to provide the user with the functionality to clone an opportunity, but with added
|
||||
benefits.
|
||||
|
||||
## How Do You Plan to Deploy Your Changes?
|
||||
- The ability to select only fields that need to be edited during the cloning
|
||||
- The ability to select fields that must be cleared of their original value
|
||||
- The ability to clone other child objects than just Opportunity Products
|
||||
|
||||
Do you want to deploy a set of changes, or create a self-contained application? Choose a [development model](https://developer.salesforce.com/tools/vscode/en/user-guide/development-models).
|
||||
The Project consists of the following components:
|
||||
| Item | Description |
|
||||
| ---- | ----------- |
|
||||
| OpportunityCloneService | Apex class that contains the Apex functionality |
|
||||
| OpporutnityCloneserviceTest | Code coverage and unit test class |
|
||||
| TestCloneUtility | Utilities used in the Code coverage and unit test class |
|
||||
| SmartCloneChildList custom label | Custom Label used as a setting to store semi-colon separated list of child objects to select from |
|
||||
| opportunityCustomClone | Lightning web component that is the visual interface |
|
||||
| OppCustomCloneAura | Aura Lightning Component that is used to wire to a QuickAction |
|
||||
| Opportunity.SmartClone QuickAction | The QuickAction button to use on the Opportunity Detail Layout |
|
||||
| Opportunity.ClonedFields fieldset | the fieldet used to configure displayable and cleared fields for input |
|
||||
|
||||
## Configure Your Salesforce DX Project
|
||||
### Additional Notes
|
||||
|
||||
The `sfdx-project.json` file contains useful configuration information for your project. See [Salesforce DX Project Configuration](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm) in the _Salesforce DX Developer Guide_ for details about this file.
|
||||
- This application currently will not support the cloning of a hierarchy of children. This means it is only designed to support
|
||||
the cloning of direct children to the Opportunity, and the Opportunity itself
|
||||
|
||||
## Read All About It
|
||||
## Setup
|
||||
|
||||
- [Salesforce Extensions Documentation](https://developer.salesforce.com/tools/vscode/)
|
||||
- [Salesforce CLI Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm)
|
||||
- [Salesforce DX Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_intro.htm)
|
||||
- [Salesforce CLI Command Reference](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference.htm)
|
||||
### Prerequisites
|
||||
|
||||
- You need to have the Salesforce CLI installed on your system to follow the install directions.
|
||||
|
||||
### Installed Steps
|
||||
|
||||
1. Clone this repository to your local filesystem.
|
||||
2. Navigate to the directory created from the clone.
|
||||
3. Create a 'build' folder in the directory of this cloned repository
|
||||
4. Convert the project into deployable Metadata API format using the following command `sfdx force:source:convert -r ./force-app/main/default -d ./build/unpackaged/`
|
||||
5. Zip the 'unpackaged' directory located in the 'build' folder.
|
||||
6. Deploy the zip file into your instance using the following command `sfdx force:mdapi:deploy -u <yourinstancealias> -f ./build/unpackaged.zip -w 30 --verbose`
|
||||
1. Optionally, you can use the `-l RunLocalTests` option if installing into a production instance separately.
|
||||
7. Once the deployment completes successfully, the components will be installed in your instance.
|
||||
|
||||
### Setup Steps
|
||||
Reference in new issue
Block a user