Difference between revisions of "Previous Upgrade: February 2013"
Line 64: | Line 64: | ||
==Security== | ==Security== | ||
− | + | ===Hierarchical Password Policy=== | |
− | + | A different password policy can be defined for each company which will automatically apply to all sub-companies in the hierarchy, unless they have defined their own password policy. | |
− | + | ||
− | * | + | ===Persistent Login=== |
− | * | + | * Rather than having to log in to SmartSimple each time you open your web browser, a "cookie" can be installed on your computer that will automatically authenticate you, allowing you to bypass the login screen. (This setting can be enabled or disabled by your system administrator). |
− | * This | + | |
+ | ===Email Restriction=== | ||
+ | * The ability to send e-mails from within SmartSimple can be restricted by user role. | ||
+ | |||
+ | ===Backup Server Access=== | ||
+ | * Access to the backup server can be disabled for all non-Global User Administrator accounts. | ||
+ | |||
+ | ===SSencrypt Command=== | ||
+ | * A new command called ssencrypt allows object IDs to be encrypted manually. | ||
+ | |||
+ | ===URL Parameter Encryption=== | ||
+ | * A new setting will encrypt object IDs such as userid, companyid, activity. This enhances security by making it impossible to guess URLs. | ||
Line 82: | Line 93: | ||
==UTA Enhancements== | ==UTA Enhancements== | ||
− | + | ===Level 1 Status Indicator=== | |
− | * | + | *A graphical indicator can be enabled which will appear at the top of the Level 1 record to show the status pathway and indicate the position of the current record along the path. |
− | * ''' | + | |
− | * Level 1 | + | ===Default Contact Role=== |
− | * Quick | + | * '''--Select Role--''' can be set as the default role in the Level 1 contacts section to ensure a role is selected and not left at the first role listed. |
− | + | ||
− | * The column | + | ===Level 1 Template Branch Restriction=== |
− | + | * Level 1 templates can be restricted to any number of internal branches, rather than just one. | |
− | + | ||
− | + | ===Quick Entry=== | |
− | * Level 2 | + | * The Quick Entry method of creating multiple Level 2 items has been enhanced. Up to ten records can be created at once with any combination of Level 2 Types, and the custom fields that appear on the quick entry page can be selected. Additionally, an auto-number can be assigned to all records at the time of creation. |
− | * Recurring activities can be scheduled weekly on multiple days | + | |
− | * When displaying Level 2 records on the contact calendar, | + | ===List View Heading=== |
− | + | * The column headings in the list views can be defined on the list view settings page. This applies to Level 1, Level 2, Level 3, Invoices, Contacts and Companies. | |
− | * | + | |
− | * UTA Role Custom Fields at Level 1 and Level 2 as well as | + | ==="Is Empty" Search=== |
− | * | + | * Standard and custom fields and Level 1, Level 2 and Level 3 records can be searched to find empty values using the "Is Empty" search option. |
− | * | + | |
− | * UTA | + | ===Lock on Type=== |
− | + | * Level 2 and Level 3 records can have their type locked after creation to prevent it from being changed. | |
− | + | ||
− | * | + | ===Creation Roles=== |
+ | * The user roles that are permitted to create each Level 2 and Level 3 record type can be configured separately. | ||
+ | |||
+ | ===Available Statuses=== | ||
+ | * The statuses that are available to each type of Level 2 or Level 3 record can be defined. | ||
+ | * Similarly, you can define which other statuses are available from each status. This is for Level 2 and Level 3. | ||
+ | |||
+ | ===Recurring Activities=== | ||
+ | * Recurring activities can be scheduled weekly on multiple days of the week. | ||
+ | |||
+ | ===Level 2 Contact Calendar Status=== | ||
+ | * When displaying Level 2 records on the contact calendar, the records that are shown for each Level 2 type can be controlled by status. | ||
+ | |||
+ | ===Invoice Status Batch Update=== | ||
+ | * Invoice status can now be change using batch update. | ||
+ | |||
+ | ===Void Invoice=== | ||
+ | * A button to automatically void invoices has been introduced. Visibility of the button is controlled by Advanced Logic. | ||
+ | |||
+ | ===UTA Role Custom Fields=== | ||
+ | * UTA Role Custom Fields at Level 1 and Level 2 as well as Associations can be defined to appear for all user roles. | ||
+ | |||
+ | ===Group Contact Assignment=== | ||
+ | * When the multiple contact list is enabled, groups of contacts can now be assigned at Level 2 and Level 3 in the same manner as they are at Level 1. Advanced Logic has been introduced to allow this feature to be suppressed at Levels 1, 2 and 3. | ||
+ | |||
+ | ===Multiple Contact/Company List=== | ||
+ | * When the Level 2 multiple contact or company lists are enabled they can now be re-positioned below the custom fields, in the same relative location as they appear at Level 1. | ||
+ | |||
+ | ===Aggregation UTA=== | ||
+ | * Creating an aggregation UTA will facilitate creating reports that span multiple related UTAs by defining the association between equivalent fields in each UTA. | ||
+ | |||
+ | ===Data Exchange=== | ||
+ | * Settings have been added to specify "preserve template", "preserve type", "reject new template" and "reject new type" (Level 2 and Level 3). Additionally there is a new setting to prevent the exchange of new Level 2 records. | ||
+ | |||
+ | ===UTA Connection List View=== | ||
+ | * The fields to be shown in the UTA connection list view can be selected when the consumer/provider relationship is enabled. | ||
+ | |||
+ | ===Template Pages=== | ||
+ | * Level 1, Level 2 and Level 3 Template pages now go through the variable processor. This means you can include variables directly on the template page. | ||
+ | |||
==Workflows== | ==Workflows== |
Revision as of 20:21, 9 May 2011
Contents
- 1 General Information
- 2 Next Upgrade: 12 May and 26 May 2011
- 2.1 Security
- 2.2 Standard and Custom Fields
- 2.3 UTA Enhancements
- 2.3.1 Level 1 Status Indicator
- 2.3.2 Default Contact Role
- 2.3.3 Level 1 Template Branch Restriction
- 2.3.4 Quick Entry
- 2.3.5 List View Heading
- 2.3.6 "Is Empty" Search
- 2.3.7 Lock on Type
- 2.3.8 Creation Roles
- 2.3.9 Available Statuses
- 2.3.10 Recurring Activities
- 2.3.11 Level 2 Contact Calendar Status
- 2.3.12 Invoice Status Batch Update
- 2.3.13 Void Invoice
- 2.3.14 UTA Role Custom Fields
- 2.3.15 Group Contact Assignment
- 2.3.16 Multiple Contact/Company List
- 2.3.17 Aggregation UTA
- 2.3.18 Data Exchange
- 2.3.19 UTA Connection List View
- 2.3.20 Template Pages
- 2.4 Workflows
- 2.5 Reports
- 2.6 Variables
- 2.7 Misc
- 3 Previous Upgrades
General Information
The SmartSimple platform is upgraded with new features and enhancements approximately every 2 to 3 months.
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" 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 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.
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.
- Topic: SmartSimple May 2011 Upgrade
- Date: Tuesday, May 10, 2011
- Time: 11:00 am, EST
- Meeting Number: 576 959 334
- Meeting Password: Tech39
- 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
- Webex Link: https://smartsimple.webex.com
Next Upgrade: 12 May and 26 May 2011
The next upgrade cycle will commence on the 12th of May, 2011.
The following server will be upgraded on Thursday 12 May, 2011 at 10pm EST:
- smartsimple.biz
The backup server (*.smartsimplebk.biz) will be upgraded on Thursday May 5th for testing.
The following servers will be upgraded on Thursday 26 May, 2011 at 10pm EST.
- smartsimple.com
- smartsimple.ca
- smartsimple.ie
- smartsimple2.biz
- smartsimple3.biz
The associated backup servers will be upgraded on Thursday 19th May 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 the support team will be in contact with your system administrator to schedule the upgrade of your server after May 31st.
The following is a partial list of the features that are scheduled to be included.
- Note: this list is subject to revision.
Security
Hierarchical Password Policy
A different password policy can be defined for each company which will automatically apply to all sub-companies in the hierarchy, unless they have defined their own password policy.
Persistent Login
- Rather than having to log in to SmartSimple each time you open your web browser, a "cookie" can be installed on your computer that will automatically authenticate you, allowing you to bypass the login screen. (This setting can be enabled or disabled by your system administrator).
Email Restriction
- The ability to send e-mails from within SmartSimple can be restricted by user role.
Backup Server Access
- Access to the backup server can be disabled for all non-Global User Administrator accounts.
SSencrypt Command
- A new command called ssencrypt allows object IDs to be encrypted manually.
URL Parameter Encryption
- A new setting will encrypt object IDs such as userid, companyid, activity. This enhances security by making it impossible to guess URLs.
Standard and Custom Fields
- Standard Fields - Edit condition to control which user roles are permitted to edit each standard field.
- Language translation integration within the custom fields settings.
- Proxy friendly multiple file upload applet
- New Custom Field Type: Special - Hand Drawing (Pain Diagram)
- Display Only Image field: Enable "Camera Snapshot" and "Auto Capture" settings
- Multiple Files field: Document console to allow preview of files without opening them and facilitate printing.
UTA Enhancements
Level 1 Status Indicator
- A graphical indicator can be enabled which will appear at the top of the Level 1 record to show the status pathway and indicate the position of the current record along the path.
Default Contact Role
- --Select Role-- can be set as the default role in the Level 1 contacts section to ensure a role is selected and not left at the first role listed.
Level 1 Template Branch Restriction
- Level 1 templates can be restricted to any number of internal branches, rather than just one.
Quick Entry
- The Quick Entry method of creating multiple Level 2 items has been enhanced. Up to ten records can be created at once with any combination of Level 2 Types, and the custom fields that appear on the quick entry page can be selected. Additionally, an auto-number can be assigned to all records at the time of creation.
List View Heading
- The column headings in the list views can be defined on the list view settings page. This applies to Level 1, Level 2, Level 3, Invoices, Contacts and Companies.
"Is Empty" Search
- Standard and custom fields and Level 1, Level 2 and Level 3 records can be searched to find empty values using the "Is Empty" search option.
Lock on Type
- Level 2 and Level 3 records can have their type locked after creation to prevent it from being changed.
Creation Roles
- The user roles that are permitted to create each Level 2 and Level 3 record type can be configured separately.
Available Statuses
- The statuses that are available to each type of Level 2 or Level 3 record can be defined.
- Similarly, you can define which other statuses are available from each status. This is for Level 2 and Level 3.
Recurring Activities
- Recurring activities can be scheduled weekly on multiple days of the week.
Level 2 Contact Calendar Status
- When displaying Level 2 records on the contact calendar, the records that are shown for each Level 2 type can be controlled by status.
Invoice Status Batch Update
- Invoice status can now be change using batch update.
Void Invoice
- A button to automatically void invoices has been introduced. Visibility of the button is controlled by Advanced Logic.
UTA Role Custom Fields
- UTA Role Custom Fields at Level 1 and Level 2 as well as Associations can be defined to appear for all user roles.
Group Contact Assignment
- When the multiple contact list is enabled, groups of contacts can now be assigned at Level 2 and Level 3 in the same manner as they are at Level 1. Advanced Logic has been introduced to allow this feature to be suppressed at Levels 1, 2 and 3.
Multiple Contact/Company List
- When the Level 2 multiple contact or company lists are enabled they can now be re-positioned below the custom fields, in the same relative location as they appear at Level 1.
Aggregation UTA
- Creating an aggregation UTA will facilitate creating reports that span multiple related UTAs by defining the association between equivalent fields in each UTA.
Data Exchange
- Settings have been added to specify "preserve template", "preserve type", "reject new template" and "reject new type" (Level 2 and Level 3). Additionally there is a new setting to prevent the exchange of new Level 2 records.
UTA Connection List View
- The fields to be shown in the UTA connection list view can be selected when the consumer/provider relationship is enabled.
Template Pages
- Level 1, Level 2 and Level 3 Template pages now go through the variable processor. This means you can include variables directly on the template page.
Workflows
- Create Activity Workflow Task available at Level 2 to create Level 3 records.
- Workflow request for comment/approval at Level 2 and Level 3: can define whether the record appears in view or edit mode.
Reports
- Reports: Display Charts using Flash animation
- Reports: New dashboard layouts: 1x7, 1x8, 1x9 and 1x10
Variables
- Variable processor currency formatting (@format(FIELD NAME,currency,CURRENCYCODE)@)
- System Library to provide central access to commonly used option lists, script functions and other components.
- System variable pre-processing (@system2.@variable name@@) as well as support for system variables appearing within system variables
- A global autonumber field can be specified as a System Variable. This will allow sequential numbers to be provided across different objects in different UTAs
Misc
- Global Advanced Logic to control who is permitted to edit contact records.
- Fields searched and displayed when using the Ajax Lookup can be customized for Contacts and Accounts. The column headings can also be customised.
- Manager Permission to provide read-only access to the Message Queue, controlled by user role.
- Manager Permission to restrict use of the Multiple File Upload Applet
- The List View column headings can be customised for Contacts and Accounts.
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.