Changes

* Persistent Login===Hierarchical Password Policy===* ssencrypt command A different password policy can be defined for each company which will automatically apply to manually encrypt object ids* Hierarchical all sub-companies in the hierarchy, unless they have defined their own password policy . ===Persistent Login===* A new setting available Rather than having to restrict access log in to backup server 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===* Ability to restrict which user roles are permitted The ability to send e-mails through [[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 upgrade will provide a number of additional enhances security enhancements which will be announced when the Technical Journal is sent outby making it impossible to guess URLs.

* ===Level 1 graphical Status life cycle indicatorIndicator===* Template pages now go through 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 variable processorpath. ===Default Contact Role===* '''—Select Role—--Select Role--''' can be set as the default role in the Level 1 Contacts contacts section to ensure a role is selected deliberately and not left at the first role listed inadvertently. ===Level 1 Template Branch Restriction===* Level 1 template templates can be restricted to a set any number of internal branches, rather than just one. ===Quick Entry===* The Quick entry feature to create 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 same time: * Includes custom fields that appear on the ability to assign a '''Group Identifier''' quick entry page can be selected. Additionally, an auto-number can be assigned to allrecords at the time of creation. ===List View Heading===* The column heading used headings in the [[List View]]s list views can be specifieddefined on the list view settings page. This applies to Level 1, Level 2, Level 3, Invoices, Contacts and Companies.* Search panel can search for empty fields using ==="Is Empty" at Search===* Standard and custom fields and Level 1, Level 2 and Level 3records can be searched to find empty values using the "Is Empty" search option.* '''===Lock on Type''' at ===* Level 2 and Level 3 records can have their type locked after creation to prevent changing the type once the record has been createdit from being changed.  * Level 2 and Level 3 '''===Creation Roles''' to define which ===* The user roles that are permitted to create each Level 2 and Level 3 record typecan be configured separately. ===Available Statuses===* The statuses that are available to each type of Level 2 and or Level 3 '''Available Statuses''' to record can be defined.* Similarly, you can define which other statuses are available to from each typestatus. This is for Level 2 and Level 3. ===Recurring Activities===* Recurring activities can be scheduled weekly on multiple daysof the week.  ===Level 2 Contact Calendar Status===* When displaying Level 2 records on the contact calendar, which the records that are shown for each Level 2 type can be controlled by Statusstatus.* ===Invoice Status Batch Update for invoice statuses===* '''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 role using Advanced Logic) .  ===UTA Role Custom Fields===* UTA Role Custom Fields at Level 1 and Level 2 as well as Association Associations can be defined to appear for all user roles. ===Group Contact Assignment===* Contacts When the multiple contact list is enabled, groups of contacts can now be assigned by Group at Level 2 and Level 3, in the same manner as they are at Level 1. Additionally an Advanced Logic setting has been introduced to allow this feature to hide the Group assign option be suppressed at each level if it's not requiredLevels 1, 2 and 3.  ===Multiple Contact/Company List===* If When the Level 2 multiple contact or account 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 Connection [[List View]] (Consumer/Provider) can be customizedwill facilitate creating reports that span multiple related UTAs by defining the association between equivalent fields in each UTA.  * ===Data Exchange: Preserve Template===* Settings have been added to specify "preserve template", Preserve Type"preserve type", "reject new Template, template" and "reject new Type type" (Level 2 and Level 3)* Data Exchange: Setting . Additionally there is a new setting to prevent the exchange of new Level 2 records. ===UTA Connection List View===* Aggregation UTA: Creating an aggregation UTA will facilitate creating reports that span multiple related UTAs by defining the association between equivalent The fields to be shown in each the UTAconnection 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.