-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5 from jonsayer/master
Work up to June 10
- Loading branch information
Showing
10 changed files
with
258 additions
and
90 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,16 @@ | ||
Test readme | ||
How to Install | ||
|
||
1) In the target org, install the Twilio Helper Library: https://github.com/twilio/twilio-salesforce | ||
2) Ensure your target org has all of the fields associated with our fieldsets pre-installed. Those can be found in src/Objects, in the Account.object file and the Contact.object file. A TBG sandbox should work just fine. | ||
3) Install this package to your instance. | ||
4) After install, configure the Custom Settings for "TwilioConfig". | ||
a) For TBG sites, please see those relevant docs. | ||
b) The settings must have the name "default", no quotes, all lower case. | ||
5) Create a Force.com site with these permissions: | ||
a) Access to all of the Visualforce Pages in this package/ | ||
i) C501_ClassReg_CreateAcct | ||
ii) C501_ClassReg_Home | ||
iii) C501_ClassReg_Login | ||
b) Set the site template to C501_ClassRegSiteTemplate | ||
c) Configure the PubliC Access Settings to have access to all of the fields on the Contact, Account, and School Term objects that are needed (this will shift through the lifetime of this project) | ||
d) Also, make sure the Public Access Settings have full access to the Class Site Login Attempt object. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.