Contents
Purpose
What is SedonaSync
Important Notes
Managing Projects for New Deployment
Managing Projects for Add on Databases Licensing
Managing Projects for V9 to V10 upgrades
Purpose
The purpose of this document is to outline the steps required for PMO resources to deploy SedonaSync standalone projects, as part of a new customer implementation, add-on module project, or license change for SedonaSync.
It does not include the steps required by the installation tech or consultant delivering training or event configuration services. Please refer to those departments for detailed information on those areas.
What is SedonaSync
SedonaSync is an OEM version of Knowledge Sync, an add-on module developed by Vineyardsoft, a subsidiary of ECI Software Solutions. In its simplest form, it uses events to trigger activities either within other software or sends automated emails or reports based upon an event trigger. The events will look for a condition in a database and then perform an action based on that event. Examples:
- When a sales order is received over x dollars, send an email to the President of the company
- At X time each day, send a report for all quotes closed to a specific person or group
- When x happens in a database, update database table x, field x, with x information
SedonaSync does come with an event pack with the most common events a Bold Group customer would use. Additional events can be configured at an additional service rate.
Top of Document
Important Notes
Below are some important items to remember when working with SedonaSync:
- Any net new SedonaOffice sale:
- Requires SedonaSync version 10 and will be Enterprise Webcaster
- Will include 1 database and within that database can have multiple companies
- A database connection is an application, not each application database
- Examples of database connections: SedonaOffice, Manitou, Stages, SFDC, etc.
- Example of companies for the SedonaOffice database:
- SedonaOffice Live1
- SedonaOffice Live2
- SedonaOffice Sandbox database
- Example of companies for Manitou
- Manitou Live1
- Manitou Sandbox Database
- Example of companies for the SedonaOffice database:
- Examples of database connections: SedonaOffice, Manitou, Stages, SFDC, etc.
- A database connection is an application, not each application database
- SedonaOffice database connection can include more than one company, but number of companies must be noted when requesting the license
- Example: 1 Database: SedonaOffice 2 companies: Company A Live and Company B Live
- Will include 1 client connection. Additional will be noted on the sales quote and number purchased included in the information when requesting the license
- Upgrading from V9 to V10 is free, as part of their support/maintenance agreement.
- Upgrades will take additional time and will be quoted with additional services time
- Upgrade issues for canned events will be covered as part of the upgrade unless the canned event is modified. Modified canned events and custom events are not covered under maintenance and support. Work on these events will require additional hours quoted
- Customer using OPT services must make OPT aware of any migration from V9 to V10 PRIOR to the upgrade occurring
- For test server setup (used to migrate to a new server), a temp license must be requested from ECI. The temp license will be turned off when the new server is live. Follow the same steps as for Managing Projects for Add on Databases Licensing
Managing Projects for New Deployment
Follow the steps below:
- Confirm customer is on the latest version of SedonaOffice
- Send customer Kick-off email
- Use template 'SedonaOffice Add On module - with Checklists Attachments'
- Remove all Preinstall checklist for non-SedonaSync products
- Use template 'SedonaOffice Add On module - with Checklists Attachments'
- Confirm Preinstall checklist has been received and review for any missing information
- Schedule an appointment with System Tech to request license from ECI
- Include name of customer's server
- Important Note: Server name can only be 15 characters long
- Include note for number of database connections (qty listed in sales quote for SedonaSync)
- If more than one listed, provide databases to be connected
- Example: SedonaOffice, Manitou, Stages, SFDC, etc
- If more than one listed, provide databases to be connected
- Include note for number of companies to be connected
- Include name of customer's server
- Schedule appointment with System Tech to install at least one week after license request task and after preinstall checklist has been received/reviewed.
- Duration will be 4 hours (both cloud and on prem installs)
- No SedonaOffice down time.
- Include the following information in the Chatter section of the task:
- Customer contact information
- Number of SedonaOffice databases
- If more than one list:
- Example: i.e. Manitou, Stages, SFDC, etc
- Number of Admin users (from checklist)
- If more than one list:
- Schedule Technical Consultant (if purchased) for training and configuration of events (note, quote may not include training, see No Training Purchased section for details to provide customer training info in this case).
- Include the following notes in the Chatter section of the task. This info is same info provided to tech for license/install. You may have to email the information to any resources delivering services that do not have access to Salesforce:
- Customer contact info
- Name
- Phone
- Location
- Licensing software
- Number of database connections
- For more than one connection list all connections:
- Example: i.e., Manitou, Stages, SFDC, etc
- Number of Admin users (from checklist)
- Installation of Software
- Cloud based - provide customers SedonaOffice URL
- On Premise – provide customer contact info with IT contact (internal contact or external IT firm should be noted)
- Name of main user or users being trained on SedonaSync
- Number of Hours approved for consulting/training
- Customer contact info
- No Training Purchased - if quote does not include training, provide the customer with the following information with Kick Off call/email. Customer should review the following prior to their first session with consultant:
- Training includes guides and on demand pre -recorded training videos as per the contract details. The following resources are available on BoldU for you to review. Please review this material PRIOR to your first session with our consultant. If you would like additional training, please reach out to your sales rep to purchase training time.
- Include the following notes in the Chatter section of the task. This info is same info provided to tech for license/install. You may have to email the information to any resources delivering services that do not have access to Salesforce:
- For cloud customers only, the day prior to the first session with the Technical Consultant, schedule the System Tech for 30 minutes to confirm access for the Technical Consultant and customer's user access
Managing Projects for Add on Databases Licensing
Follow the steps below for projects for Add on Database projects:
- Confirm customer is on the latest version of SedonaOffice
- Ask the customer for the following information if not provided in the project hand off information from sales:
- Current SedonaSync version they are on - 9 or 10
- Webcaster version or not
- Tech will have to have a call with the customer to validate if we cannot determine
- Are they using OPT? If so, they will need to contact OPT to confirm timing of the upgrade from V9 to 10 if upgrade is included in the project
- Current SedonaSync version they are on - 9 or 10
- Schedule appointment with Installation Technician to request a license from ECI
- Include name of customer's server
- Important Note: Server name can only be 15 characters long
- Include note if license is for webcaster or not
- Include note if licenses are v9 or v10
- Include note for number of Sedona office databases being added
- If additional application databases included list those as well
- Example: i.e., Manitou, Stages, SFDC, etc
- Include name of customer's server
- Schedule appointment with tech to install - one week later
- Include customer contact
- Include note if license is for webcaster or not
- Include note that Customer has SedonaSync - this is just license upgrade
- Duration: 2 hours
- If upgraded to v10 from V9 is included duration is 8 hours
- Schedule Consulting appointment and include following notes:
- Licensing software
- One database or multiple databases?
- One admin user or multiple users?
- Installation of Software
- Cloud based
- On Premise – requires contact with IT contact (internal contact or external IT firm should be noted
- Name of main user or users being trained on SedonaSync
- Number of Hours approved for consulting/training requested
- Licensing software
Managing Projects for V9 to V10 Upgrades
The following steps are required to upgrade a customer's SedonaSync application from V9 to V10:
- Discuss events -
- inform customer: Only canned events purchased and installed will be covered under maintenance/support if issues arise post upgrade
- Any custom events or canned events that have been modified are not covered under the scope of the project unless specifically outlined. Issues post upgrade will require additional services time to resolve
- OPT events should be upgraded by OPT
- Customer to coordinate timeline with OPT
- inform customer: Only canned events purchased and installed will be covered under maintenance/support if issues arise post upgrade
- Schedule appointment with Installation Technician to request license from ECI
- Include name of customer's server
- Important Note: Server name can only be 15 characters long
- Include note if license is for webcaster or not
- Include note if licenses are v9 or v10
- Include note for number of Sedona office databases being added
- If additional application databases included list those as well
- Example: i.e., Manitou, Stages, SFDC, etc
- Include name of customer's server
- Schedule appointment for Installation Technician - 4hours
- Technician to backup the existing SedonaSync database and install V10, then restore database
- Schedule Technical Consultant to upgrade SedonaSync Events
- Time will depend upon scoping done during sales process on number events that need to be updated
Revision History
Revision History
8/18/2023 - JMK updated resource name from Installation Tech to System Tech, added task for System Tech for 30 minutes before Technical consultant first session to verify access for Technical Consultant and customer users per request of System Tech
2/7/2023 - JMK - Updated install section to include new kick off template SedonaOffice Add On module - with Checklists Attachments. Updated Upgrade section to include discussion with customer on what events are covered by maintenance/support post upgrade if any issues arise
1/31/2023 - JMK Update all license request tasks to include note for server name - which can only be 15 characters long when requesting license