|
|
| (107 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | =General Information=
| + | The following features were implemented as part of the upgrade cycle commencing in February 2013: |
| | | | |
| − | The [[SmartSimple]] platform is upgraded with new features and enhancements approximately every 2 to 3 months.
| + | ===Universal Tracking Application=== |
| | + | * New [[caption]] setting introduced for the configuration of [[Template|type]]/[[status]] of objects, allowing you to change the default display name of a type/status. New [[Variable List|variables]] @statuscaption@ and @typecaption@ have been introduced to retrieve these captions. |
| | + | <!--17980 - Captions in English--> |
| | + | <!--Variable List page updated--> |
| | + | * New language translation setting introduced for the configuration of types and statuses for the UTA at Level 1, Level 2, and Level 3. New [[Variable List|variables]] @type_lang@ and @status_lang@ introduced to retrieve the relevant translation based on the current user. |
| | + | * New [[Field Permission Matrix|field visibility matrix]] introduced allowing you to configure a complex combination of view/edit permissions for custom fields based on user roles and UTA statuses in bulk. |
| | + | * Enhanced the UTA [[Batch Update|batch update]] feature to open directly off your current list view results instead of directing to a separate search page. |
| | + | * Enhanced the UTA [[Batch Update|batch update]] feature with the ability to update multiple contacts/group for UTA Level 1. |
| | | | |
| − | 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 [http://smart.smartsimple.com/s_signup.jsp?token=XVtQC1oGYF9bRxdFQhdQ subscribe] to the [[:Category:Newsletter Archives|Technical Journal]] that is sent out prior to each upgrade on the [http://smart.smartsimple.com/s_signup.jsp?token=XVtQC1oGYF9bRxdFQhdQ Newsletter Signup Page]. (Unsubscribe [http://smart.smartsimple.com/s_signup.jsp?token=XVtQC1oGYF9bQxNFQhdQ here]).
| + | ===Variable Processor=== |
| | + | * New [[Variable List|variable]] @sstimezone@ allows you to retrieve the user's timezone setting which can then be used to calculate their relative date/time. |
| | + | <!--17466 - Would like to have timezone variable that runs on the report builder--> |
| | + | <!--Variable List page updated--> |
| | | | |
| − | ==System Upgrade Process== | + | ===Standard and Custom Fields=== |
| | + | * Enhanced the account [[list view]] within a [[UTA]] with the ability to list the account [[owner]] as a column. |
| | + | * New ability to update the [[display order]] of only a selected group of [[custom fields]] within [[Batch Update|batch update]] (previously forced to update display order of all custom fields). |
| | | | |
| − | 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.
| + | ===Transactions=== |
| | + | * Enhanced [[:Category:Transactions|transactions]] with the ability to enable [[Record Lock|record locking]]. |
| | | | |
| − | ===Backup Server Update=== | + | ===Integration=== |
| | + | * Enhanced PubMed service with the additional ability to search on publication date. |
| | + | * Introduced [[integration]] with GuideStar service and ability to search their database. |
| | | | |
| − | * Each [[Backup Server and Testing Instances|backup server]] will be updated to the "release candidate" one week prior to the upgrade date.
| |
| − | * This update will provide for instance specific testing of release candidate, as you can log into your respective [[Backup Server and Testing Instances|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.
| |
| | | | |
| − | ===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 Wednesday at 12:00pm.
| |
| | | | |
| − | | + | [[Category:Upgrades| 2013-02]] |
| − | | |
| − | ----
| |
| − | ----
| |
| − | | |
| − | =Next Upgrade: May 2012=
| |
| − | | |
| − | The following server will be upgraded on Thursday 17 May, 2012 at 10pm EST:
| |
| − | :* smartsimple3.biz
| |
| − | The [[Backup Server and Testing Instances|backup server]] (*.smartsimple3bk.biz) will be upgraded on Thursday May 10th for testing.
| |
| − | | |
| − | | |
| − | | |
| − | The following servers will be upgraded on Thursday 24 May, 2012 at 10pm EST.
| |
| − | :* smartsimple.com
| |
| − | :* smartsimple2.biz
| |
| − | :* smartsimple4.biz
| |
| − | The associated [[Backup Server and Testing Instances|backup servers]] will be upgraded on Thursday May 17th for testing.
| |
| − | | |
| − | | |
| − | | |
| − | The following servers will be upgraded on Thursday 31 May 2012 at 10pm EST.
| |
| − | :* smartsimple.ca
| |
| − | :* smartsimple.us
| |
| − | :* smartsimple.biz
| |
| − | :* smartsimple.ie (after 10pm GMT)
| |
| − | :* factorial.ca
| |
| − | The associated [[Backup Server and Testing Instances|backup servers]] will be upgraded on Thursday May 24th for testing.
| |
| − | | |
| − | | |
| − | '''Important:''' The upgrade will be applied to your backup server 1 week prior to the scheduled upgrade date for your production server. You are encouraged to log into your backup server during this period to test the changes against your most recent data and configuration. [[Backup Server and Testing Instances]]
| |
| − | | |
| − | | |
| − | If your organization has a dedicated [[SmartSimple]] server or you host in-house SmartSimple will be in contact with your system administrator to schedule the upgrade of your server '''after''' June 1st.
| |
| − | | |
| − | | |
| − | We will be sending our Technical Journal in advance of the upgrade as well. If you would like to receive the Technical Journal you may [http://smart.smartsimple.com/s_signup.jsp?token=XVtQC1oGYF9bRxdFQhdQ subscribe here]
| |
| − | | |
| − | | |
| − | | |
| − | The following is a '''tentative''' list of the features included in the upgrade.
| |
| − | | |
| − | ==Security==
| |
| − | * Enforce from address in password e-mail: When a user clicks '''Send Password''' by default is uses their e-mail address as the from address in the system e-mail. With the from address used will always be the one defined on the [[User Email Templates]] page.
| |
| − | * '''Challenge questions''': rather than e-mailing a randomly generated password when new contacts register or when users click the '''Forgot Password''' the system can be configured to e-mail a time-limited authentication link. When clicking the link the user will be presented challenge question that must be answered correctly before they are logged into SmartSimple and asked to create a new password.
| |
| − | | |
| − | | |
| − | ==List Views==
| |
| − | * User defined List views: users can create their own personal list views for any entity (organizations, contacts, Level 1, Level 2, Level 3). They can select the fields they wish to use in each view, the display orders of the fields and sort order of the data and the colour of each column in the list view.
| |
| − | * Administrators can choose to make List Views public to be shared with other users.
| |
| − | * The List View can be marked as favourite and these list views are listed at the top of the list view selection.
| |
| − | * Any List View (system, public or private) can be copied, renamed and saved.
| |
| − | * The contents of a List View can be exported to MS Excel, MS Word or PDF though an Export feature
| |
| − | * The List view contents can also be used to create a set of MS Word letters though a Merge feature. When this feature is used an MS Word Merge Word custom field is assigned to the list view to allow bulk merging. (All selected records will be merged into a single document for printing)
| |
| − | * The System will remember the last list view used by a user and reapply that list view when the user next access that part of the system
| |
| − | * Multiple fields can be displayed within the same column in a "stacked" configuration.
| |
| − | * The [[List View]] for Associates/Associations can be customized via the [[Global Settings]] page.
| |
| − | | |
| − | ==Reports==
| |
| − | * Once a report is generated the user can select an MS Excel template used to create a MS Excel version of the report.
| |
| − | * Any Report can be set as a favourite to be displayed in the Favourite Reports tab.
| |
| − | * Support for exporting reports to a MS Word template
| |
| − | * The Report Builder will now support the MYSQL '''having''' clause. '''Having''' is used to accommodate criteria when aggregate functions are used.
| |
| − | | |
| − | ==Standard and Custom Fields==
| |
| − | * Settings for '''Standard Field'''s will be managed in a similar manner to Custom Fields. Including Role and Status Field Permissions lookups and the ability to '''translate''' Standard Field labels and validation messages
| |
| − | * You can now '''Track Changes''' on Contact and Company [[Standard Fields]]
| |
| − | * An improved [[Custom Field Type: Text – Rich Text|Rich Text]] editor will be introduced. As well as improved functionality and compatibility, the array of buttons displayed can be configured by an administrator as needed via [[Global Settings]]
| |
| − | * File Type Restrictions: '''Single File''' and '''Multiple Files''' custom fields can be configured to define which file extensions can be uploaded to each specific field (e.g. .pdf, .doc, .xls)
| |
| − | * '''Translation XML''': custom field language translations can now be done by exporting and importing using an XML template.
| |
| − | * Level 1 Track Changes: the field history of all fields with Track Changes enabled on Level 1 can be viewed at once with a new menu bar button.
| |
| − | * Option to make custom fields manifest as hidden for the following field types: Creation - Created By, Creation - Date, Special - Auto Number, Special - Calculated Value,
| |
| − | Store Value - System Variables. This will allow the value to be updated/saved without being visible on the page.
| |
| − | | |
| − | | |
| − | ==Transactions==
| |
| − | * Transaction Template Formula: server side formulas to be run whenever a transaction is saved.
| |
| − | * Transaction Template Page: Template page that can be used for internal or external entry/update of transactions.
| |
| − | | |
| − | ==Workflows==
| |
| − | * '''Update Custom Field''' task type will be available on Company and Contact workflows
| |
| − | * Company and Contact Workflow connectors can be delayed to trigger on a date stored in a [[Custom Field]] on the Company/Contact record
| |
| − | * The Recipient of workflows (Acknowledgement, Request for Comment, Request for Approval) can now be defined using variable syntax, rather than being limited to the list by role. This will allow you to send the same e-mail to multiple roles at the same time rather than creating 2 different tasks. It will also allow you to filter based on a custom field on the contact, or UTA Contact Role Based custom field(s). For [[Notes]] created against UTA records this will allow you to select recipients by UTA role (or owner/person) rather than system role.
| |
| − | | |
| − | ==Autoloader==
| |
| − | * Contact Autoloader: Match a field on the contact with a field on company records so the contacts will be created/moved under the relevant company. Similarly with company autoloader
| |
| − | * Company Autoloader: Match company field to find parent company, allowing new/updating companies to be managed within a hierarchy.
| |
| − | * Disable users with the autoloader (expose the Access Type)
| |
| − | * Setting to specify 'Append' role defined on autoloader rather than replace it if the user already exists in the system
| |
| − | * Allow addition of multiple roles (select many list box instead of combo box)
| |
| − | | |
| − | | |
| − | ==Miscellaneous==
| |
| − | * Advanced Date Searching: When using the advanced search to search a date field (standard or custom) you can search using: On, before, after, between or is empty.
| |
| − | * '''Level 1 Copy''': Specify which Custom Fields will be copied when a Level 1 is copies, including specifying which are mandatory. Can also define a Level 1 Status to be the default copy status.
| |
| − | * '''UTA Consumer/Provider'''. Full support for Level 2 to act as both consumers and providers. Can now define a '''Role''' for Consumer/Provider relationships, including the ability to have role base custom fields to track attributes of the association between specific consumer and provider records.
| |
| − | * Pandora '''utarole_add, utarole_remove''' and '''utarole_update''' functions extended to create, remove and update consumer/provider relationships.
| |
| − | * '''Batch Update''' Contacts can be added to Level 2 records using batch update when the Multiple Contact List is enabled at Level 2.
| |
| − | * Variable processor support for:
| |
| − | ::* Displaying the last time a user logged into the system: '''@me.lastlogin@'''
| |
| − | ::* Listing all the companies under another company: '''[#(object=company) ~name~ #]'''
| |
| − | ::* Displaying Contact/Company association role based custom fields: '''[#(?object=association;)$?afc_customfieldid$#]'''
| |
| − | * A new setting in email broadcast to choose a user custom field as email address instead of user standard field (e.g. alternate e-mail address)
| |
| − | *
| |
| − | | |
| − | ----
| |
| − | | |
| − | =Previous Upgrades=
| |
| − | Click on the links below to find detailed information on previous upgrades.
| |
| − | * The date listed indicates when the upgrade cycle commenced. Not all servers were upgraded on that date.
| |
| − | ==[[Previous Upgrade: November 2011]]==
| |
| − | ==[[Previous Upgrade: May 19th 2011]]==
| |
| − | ==[[Previous Upgrade: October 1st 2010]]==
| |
| − | ==[[Previous Upgrade: May 13th 2010]]==
| |
| − | ==[[Previous Upgrade: October 1st 2009]]==
| |
| − | ==[[Previous Upgrade: July 30th 2009]]==
| |
| − | ==[[Previous Upgrade: May 28th 2009]]==
| |
| − | | |
| − | | |
| − | [[Category:Upgrades| ]] | |
The following features were implemented as part of the upgrade cycle commencing in February 2013:
