SedonaWeb Implementation Process

12/28/2023 3:46 pm EST

Contents

Purpose
Process Overview
Locating the Website URL
API vs SedonaWeb Sites
 

Purpose

SedonaWeb provides a web portal for Bold Product users' customers to conveniently manage their accounts. It provides visibility to view and pay open invoices, submit service tickets, and manage service calls.

If the customer already has the SedonaCloud API, there is technically no installation, just an extension to the URL.

This document walks through the process for Project Managers (PM) to implement SedonaWeb.

Top of Document

Process Overview

The following steps are required to implement SedonaWeb:

  1. Verify SedonaOffice version is compatible
    1. Yes – move to step 2
    2. No – see SedonaOffice Upgrade Implementation Process
      1. 5.7 or lower – Upgrade completion is required prior to installation Step 4
      2. 6.x or higher, add install time to step 4
  2. Confirm API status
    1. Included in the project quote?
      1. Yes
        1. Provide the customer with the appropriate preinstall checklists for installation based on where their data resides in step 3 Kick Off email

          1. Preinstall Checklist - SedonaWeb (Limited API) - On Prem

          2. Preinstall Checklist - SedonaWeb (Limited API) - Cloud

          3. Backup copies are available in Implementation and Installation Forms
      2. No
        1. Confirm customer has API API Information and Installation Process
          1. No – inform sales API needs to be sold
          2. Yes – move to step 5
  3. Send Kick Off email
    1. Template: ‘SedonaOffice Add On module - with Checklists Attachments’
    2. Update fields in red
    3. Remove checklist items that do not apply
  4. Schedule Installation
    1. Combine the necessary estimated time for each of the install tasks required:
      1. SedonaOffice Upgrade from 6.x only: 30 minutes
        1. The customer will be down during this time
      2. API
        1. Install
          1. Hosted – 2 hours
          2. On Prem – 6 hours
        2. Upgrade – 30 min
    2. Update the task Chatter to include all elements to be installed/upgraded
    3. Upload any preinstall checklists
    4. For On Prem customers, schedule an Outlook appointment for the technician and the customer
    5. The technician will install and provide the URL, username/password
  5. Test the URL
    1. See Locating the Website URL section for more information
  6. Provide website URL and user login information to the customer
    1. The website URL will be the same URL as the API with the database Prefix added to the end. See Locating the Website URL section for more information
    2. Ask the customer to test the URL
  7. Training
    1. Schedule training if sold
    2. Estimated time: 1 hour
      1. Schedule for time sold in quote
  8. Provide the customer with the SedonaWeb Customer Login Documentation document (included in files attached to this article). The customer can update this document with their portal information and contact information and share it with their customers for registering for portal use
    1. Note - at this time the SedonaOffice invoice does NOT include the registration number at the bottom of the email. It can be found in the customer's account information under the Registration Code field.
  9. Send Project Completion Request
  10. Close Project

Top of Document

Locating the Website URL

SedonaWeb is ‘installed’ with the API. Customers who purchase SedonaWeb are given both the API URL and the SedonaWeb URL. To locate the URLs, follow the steps below:

  1. Open the customer's API
    1. See API Information and Installation Process for assistance locating and opening the customer's API
    2. For this example, the API URL is: Https://linderapi.sedonaasp.com
  2. Click on Companies
  3. Under Company Name, find the database name the website will access
    1. In this example, Linder C2

  1. In the Url Prefix column, copy the prefix
    1. In this example LinderC2
  2. Combine the URL and prefix for the SedonaWeb URL
    1. In this example:
      1. API URL = Https://linderapi.sedonaasp.com
      2. SedonaWeb URL = https://linderapi.sedonaasp.com/LinderC2
  3. Logg out of the API
  4. Launch the URL
    1. Confirm you are logged out of the API
    2. Launch the SedonaWeb URL
    3. Internal login information:
      1. Username: automatedjob
      2. Password: Perennial$0ftware
      3. DO NOT CHANGE OR SHARE THIS LOGIN INFORMATION WITH CUSTOMERS

Top of Document

API vs SedonaWeb Sites

The API and SedonaWeb sites when launched will look very similar when launched unless the customer has made modifications to the sites. To tell the difference:

  1. Does the URL have the database prefix?
    1. No – API
    2. Yes - SedonaWeb
  2. Does the site menu have ‘Register’ as a menu option?
    1. No – API
    2. Yes - SedonaWeb

API - No database prefix in URL and no Register menu item


SedonaWeb – database prefix at end of URL and Register menu item is available

Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.

Copyright © 2024-26 Bold Group All rights reserved.