Previous Upgrade: February 2013

From SmartWiki
Revision as of 15:56, 22 July 2009 by Cameron (talk | contribs) (Field ID Variable)

Jump to: navigation, search

General Information

The SmartSimple platform is upgraded with new features and enhancements approximately every 6 to 8 weeks.

This page will provide a general overview of each upgrade, with links to the Wiki articles describing the new or updated features and how to use them. You can also subscribe to the Technical Journal that is sent out prior to each upgrade on the Newsletter Signup Page. (Unsubscribe here).

System Upgrade Process

The objective of the System Upgrade Process is to ensure that customers have a chance to review, without compromising the integrity of their production system, how their applications and information will work following the upgrade. In order to take advantage of this you will need to know how to access your backup instance of SmartSimple. If you need assistance with this either refer to the Backup Server and Testing Instances Wiki article, or contact the SmartSimple support desk.

Backup Server Update

  • Each backup server will be updated to the "release candidate" on the Tuesday of the update week.
  • This update will provide for instance specific testing of release candidate, as you can log into your respective backup server and test the the changes against your most current data and configuration.
  • Internal staff will also be using these servers to perform instance specific testing.
  • The update will stay in place on the backup server for the Tuesday, Wednesday and Thursday of the update week.

Update Go/No-Go

  • Subject to satisfactory testing on both the pre-production server and the production backup servers, the go/no go decision will be made on Thursday at 12:00pm.

WebEx

  • There will be a Pre-Release WebEx session the week prior to each upgrade that will provide technical details on how to implement and use the new features and enhancements.
  • Details of each WebEx session will be posted on this page once it is scheduled.




Next Upgrade: July 30th, 2009:

The next upgrade is scheduled to start on Thursday July 30th at 10pm. The following servers will be upgraded that day:

  • smartsimple.com
  • smartsimple.biz
  • smartsimple.ca

The following servers will be upgraded on {date TBC}

  • smartsimple.ie
  • smartsimple2.biz

Any clients with installed servers will be contacted to arrange an upgrade date.


WebEx Demonstration Session

Topic: July Upgrade Date: Monday, July 27, 2009 Time: 2:00 pm, Eastern Daylight Time Meeting Number: 579 163 842 Meeting Password: Upgrade727

Please click on the following link to join the meeting: https://smartsimple.webex.com

We have arranged a toll-free teleconference using the following numbers:

  • 416-343-4997 (Local dial-in)
  • 1-866-440-4486 (Toll free dial-in)
  • 800 2355-0000 (Global dial-in)

Teleconference ID: 8914632


Click on any heading below to go to the associated Wiki article.

UTA Enhancements

Level 1 Submit Button Script

  • Allows you to define a script that is run when the Submit button is pressed. The normal Submit button functions are not executed (validation and status change).
  • This will allow you to create a Browser Script that will perform custom validation of the data on the page, and can then optionally change the status or execute the submit function as part of the script.

Level 2 and Level 3 Submitted URL

  • When the Submit button is pressed for a given Status, instead of remaining on the view of the current record the user will be redirected to the URL defined in this section. If no URL is entered the current record will stay in view.
  • This was introduced for Level 1 in the last upgrade, and now has expanded to include Level 2 and Level 3.

Level 2 Type Tab Label

  • Currently you can configure Level 2 Types to be shown on their own tab in the list view at the bottom of Level 1 records, with each tab labelled with the name of the Level 2 Type it contains.
  • Following this upgrade you will be able to define the tab name for any Types that you wish to have on tabs. If you use the same tab name for multiple Types they will appear on the same tab, allowing you to group related Level 2 Types.

Skills Matching Template

  • There are now 2 different types of Level 1 Templates available. In addition the Standard Template there is now a Skills Matching template.
  • The Skills Matching Template allows you to define a set of skills that are related to a particular Level 1 record. In the Contact section of that record a Skills Match button will appear which will allow you to find contacts that have the relevant skills defined for that entity.
  • For example, if the Level 1 record is a funding application for a project researching Whale Migration Patterns you may want to assign reviewers with skills in Oceanography, Marine Biology and Meteorology.

Advanced Logic to Suppress Contact Hyperlinks

  • Using Advanced Logic you are now able to suppress the Contacts hyperlink at Level 1.
  • This allows you to define criteria to prevent UTA users from clicking into and viewing the contact record for contacts associated with a Level 1 record.

Contact/Account

Contact and Company Standard Field Terminology

  • You will be able to define your own names for the standard Company and Account fields via the Global Settings page.
  • Visibility Conditions will also be implemented on the Company and Account Standard Fields to allow control of these using logic, and any fields you don't wish to use can be removed.

Integration

MS Outlook Contact Synchronization

  • Previously only contact owners were able to synchronize contacts using MS Outlook. We are introducing a new manager permission that will allow users to synchronize contacts for which they are not the owner.
  • If this manager permission is enabled a new section will appear on the users System Settings page which will allow them to select the contact roles they wish to include in the synchronization.

Miscellaneous

Field ID Variable

  • It is now possible to reference the field ID of Custom Fields using a variable rather than the actual field ID. The syntax is @fieldname.ID@
  • This will allow you to write Browser Scripts without looking up field numbers, as well as making it easy to identify which field is being referenced. When exporting Custom Fields this will also allow you to avoid having to change the field IDs in exported Browser Scripts.
  • If you have fields with the same name (on different Templates or Types) you will still have to use the fieldid, since that is the only way to differentiate fields with identical names.

Server Time

  • The current server time can be found on the Global Settings Page.








Previous Upgrades

Click on the links below to find detailed information on previous upgrades: