Dovetail Agent Documentation

What's New

Version 7.0.0

Enhancements

• Part Request (Logistics) functionality
  • Create and Edit Part Request Headers and Part Request Details
  • Part Request Workflow operations: Accept,Assign,Dispatch,Forward,Reject,Yank,Close,Reopen
  • Part Request Actions: Create New Part Request, Replicate Part Request
  • Part Requests are available in My Work, Queries, Recent Items, and Search
• Remove the Number of Linked Cases from the Solution sidebar, as this information is now on the Linked Cases tab
• On the query results grid (such as My Work), allow for shift-clicking to select all checkboxes in-between the first one clicked and the second one that is shift-clicked.
• My Work - automatically remember the last selected tab
• Workflow Items (case, subcase, solution, part request) can be easily disabled with the Feature Enabled configuration settings. For example, if Part Requests are not used, this feature can be disabled, and they will not be shown in the application.
• Case History styling - reduce the amount of space between history item header and history item
• My Work and Tag queries now use a default condition filter of Condition Is In {{OpenOrRejectedFromQueue}}. The {{OpenOrRejectedFromQueue}} variable automatically expands to the appropriate conditions for each item type. For example, for cases, this variable expands to Open,Open-Reject. For part requests, this variable expands to Open,Open-Reject,RQST Reopened,RQST Reopened-Reject.
• The contact page now has a Create Case Action menu, making it easy to create a case for this contact.
• Notes are no longer required when closing a case or subcase
• Change Status and Log Note are now available as batch actions, making it easy to log a note or change the status of many cases or subcases at one time.

Bug Fixes

• Linked Cases for a Solution don't show the Update time.
• Reinstall site part navigates to bad page
• Copy button for the Public URL for a solution doesn't always work
• The change password action doesn't redirect properly when the application is setup as a virtual directory
• History Show Details option was not always being remembered

Changes of Interest to Developers

• New Architecture for Workflow Actions and Logs

  The workflow actions, logs, and other actions have been combined into one concept called "Entity Actions". These can be summed up as actions that can be taken on an entity, e.g. yanking a case, logging a note on a part request, re-installing a site part, etc. There is now an entityActions module that action handlers register with via a "topic" which is the combination of the action and the entity type the action occurs on.

  An action handler's responsibility is to present the user with the desired UI for the action, and then execute the action via entityActions with the information. This makes adding new actions trivial by simply creating a new action handler, registering a topic with entityActions and then executing the action once the user fills out the form (if any exists). It also allows for different UIs to be presented to the user depending on which entity the action is fired on, e.g. if "Close Case" and "Close Subcase" need to be different forms. When creating a new handler, be sure to include it as a dependency in actionRegistry.js so that it will be pulled into the app correctly.

  • editMenu.js, workflowMenu.js, and logMenu.js no longer exist and have been merged into contextMenu.js
  • workflowActions.js no longer exists
  • See assignAction.js and yankAction.js for examples of UI-driven and UI-less implementations of actions

• New Architecture for Bulk Actions

  A new "IEntityCommand" concept has been introduced to enable commands to be applied to entities. Errors and messages are aggregated during the processing of commands via the CommandNotification class (leveraging the Notification pattern). Commands are dispatched to their corresponding handlers (IEntityCommandHandler).

  Moving forward, all bulk actions will be wired up through the BulkEntityActionSource class which conventionally creates endpoints for every pair of matching commands requests that are found.

• Feature Detection

  Feature detection has been added to allow for runtime decisions. Features are classes (treating as plain old C# objects) that get built up as needed. When querying for features, the feature class is used to make the determination. By default detection is done from appSettings using a naming convention described below:

  • Class: CaseFeature
  • App Setting Key: Case.FeatureEnabled
  • App Setting Value: True/False (Default: True)

Upgrading to Version 7.0.0

1. Apply Schema Changes.

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Setup part request searching.

   If using part requests, edit Dovetail Seeker's documentSpecifications.xml file to allow for searching of part request headers and details. Within Seeker's documentSpecifications.xml file, include the part request specifications needed by Dovetail Agent, which are provided in the $dovetailAgent\source\config\seeker.config\part-request-domain-specification.xml file

3. Import data files.

   • logistics_user_defined_lists.dat
   • agent_logistics_data.dat
   • activity_codes.dat

4. If using Part Requests (Logistics), grant the Logistics privileges to the desired privilege class(es) using Dovetail Admin.

5. Merge in your customizations with the baseline source code.

6. Build / Test / Release / Deploy

Previous Versions

• 6.0.0
• 5.11.0
• 5.10.0
• 5.9.0
• 5.8.0
• 5.7
• 5.6
• 5.5
• 5.4
• 5.3
• 5.2
• 5.1
• 5.0

---

Version 6.0.0

---

Enhancements

• Improved performance throughout the application
• Agent is now a true SPA (Single Page Application), which means navigating across pages in the application is much faster
• The Navigation Menu is now accessible from every page in the app
• The Navigation Menu can be hidden on the console pages (My Work, Queues, Queries, Searches, Recent Items), and the page content will expand to fill the entire page
• Added a new Advanced Search page
• The activity spinner is now displayed when waiting for search results to appear
• The default avatar has been changed from a placeholder image to the user's initials
• Add Case Type filter for subcases, which filters on the case type of the related case for the subcase
• Queries are no longer executed on items without any relevant filters. For example, previously, a query for Case Type = Problem would query for all cases with that case type, all subcases whose related case has that case type, and all solutions. Now, solutions are not queried, as there aren't any filters that apply to solutions (as Case Type does not apply to solutions).
• Empty tabs for My Work now show a better message to the user

Bug Fixes

• Fixed an issue where sql filter parameters were incorrectly defined as nvarchar when they should be varchar for string columns using an Is In filter. This affected performance of the queries.
• Fix the styling of the date picker, which could cause it to render in an incorrect position on the page
• When using the MergeCaseHistoryChildSubcases=true app setting, and the Show Details option on the Case-History tab, duplicate entries for subcase create, close, and reopen would show. This has been resolved
• When using the MergeCaseHistoryChildSubcases=true app setting, the case history will now include subcase log entries (log email, log phone, log notes, log time & expenses)
• Rename the Sub Type filter to Subcase Type
• Fix an issue where recent cases would not show for a site with an alphanumeric site id
• Fix an inconsistency between Chrome and Internet Explorer with how items are sorted in a picker
• Added missing information about the recipients to case history for Email In action (Part of Dovetail SDK 3.3.5)
• Added missing information about the action type and the recipients to case history for Email Out action (Part of Dovetail SDK 3.3.5)
• Added missing information about the user performing an action to case history (Part of Dovetail SDK 3.3.5)

Changes of Interest to Developers

• The application is now a .NET 4.5 project (previously it was .NET 4)
• Upgraded to use FUBU MVC 2
• Upgraded to use StructureMap 3
• Upgraded to use Dovetail SDK 3.3.5
• app.root no longer exists
  • This is due to Agent 5 becoming a complete SPA instead of a SPA per bottle (core, console, support, etc.)
  • This means that links generated with app.root will need to be updated. There are a couple of options for this:
    1. You can simply replace app.root with app.base and add the SPA name in the url, for example app.root + 'sites/' + site.id can become app.base + 'support/sites/' + site.id
    2. You can change links to be calculated in the template, for example this.model.set('siteUrl', app.root + 'sites/' + site.id) in js can become <a href="support/sites/{{ site.id }}" data-link="spa">Site</a> in the template. Since Backbone's Router is aware of app.base, there's no need to put it in the link's href
  • If there were links that didn't use app.root, but also didn't include the bottle in the path, those too will need to be updated
• app.mainRegion no longer exists, use app.layout.main instead
  • Marionette deprecated the idea of having regions on an application object (http://marionettejs.com/docs/v2.4.2/marionette.application.html#application-regions) so that functionality has been replaced with a LayoutView. It is attached to the app object as 'app.layout'. The only region in that layout you'll probably need to use is app.layout.main. The other regions are header and toc.
  • This can also affect the use of ModalRegion, where you'll need to set the el to app.layout.main.el instead of app.mainRegion.el or another selector that might not exist anymore (such as #entity-content)
• Use BaseRouter object as parent for all routers
  • This contains two routers, ShownTocRouter and HiddenTocRouter. ShownTocRouter should be used when the page being routed to prefers the Toc to be shown (but if the user has hidden it, that will be persisted), while HiddenTocRouter should be used for pages where the Toc should always be hidden by default. For examples, ShownTocRouter is used on the console, while HiddenTocRouter is used for support pages like Case, Subcase, Solution, Contact, etc.
• _requireConfig.spark has been moved to requireConfig.js
  • If any plugins have been added for customizations, ensure those are added to the new requireConfig.js file
  • Paths to the plugins will also need to be updated as the location of the bower installation has changed. Use the other plugin paths as a reference to update the path of the custom plugin
• Grunt has been dropped in favor of Gulp
  • There were many reasons for this:
    1. Grunt as a project seems to be losing support
    2. Gulp as a project seems to be gaining support
    3. Gulp allows for concurrent tasks to be executed, meaning faster task completion
    4. Gulp syntax is more declarative, meaning easier understanding of what a task is doing
  • This means any custom grunt tasks will need to be converted to gulp tasks (contact us if you need assistance with this)
  • bower and grunt-cli no longer need to be installed (npm remove -g bower grunt-cli)
  • gulp needs to be installed globally to manually run gulp tasks (only required for development, npm install -g gulp)
  • A new config.json file exists that is used in gulp tasks to point to specific files. Ensure that custom filepaths are added to the correct entry of this file so that they are included
  • IMPORTANT: When developing, always run gulp watch
    • This will copy changed files to the correct location so that the browser gets the latest changes
    • This also starts up a LiveReload server that your browser can connect to, which will automatically reload the page when you change code. A Chrome extension for LiveReload is available.
• Acceptance test writing update
  • When writing tests, and checking for the current URL value, instead of checking for the full URL use the new currentUrlContains function to look for the route. This allows for older browsers like IE9 to be tested as they inject hash tags for routing.

Upgrading to Version 6.0.0

1. Install the .NET Framework 4.5

2. Merge in your customizations with the baseline 6.0 source code.

3. Build / Test / Release / Deploy

Version 5.11.0

---

Enhancements

• Add install, de-install, and re-install Site Part functionality.

• Use a treeview widget for displaying the Site Part hierarchy on the Site page.

• Enhanced the sorting capabilities for grids (My Work, Queries, etc.). Clicking a column header now has a tri-state: sort ascending, sort descending, no sorting. In addition, multiple column sorting is available using shift-click on a column header to sort by additional columns.

• The To and CC fields on the Log Email form now support searching for contacts, which makes it easier to send an email to a contact in the system. Users can search by contact first name, last name, site name, and email address.

• Add a Recent Cases tab on the Site page.

• Add an application timeout feature. After a period of inactivity, the application will be paused and the user's license will be released. A new configration setting control's the license timeout. Refer to the General application settings section for specific details.

• Add configuration setting to control the minimum number of characters in an entity search (used by many object pickers.) Refer to the Search application settings section for specific details.

• Improve the performance of paginated queries (such as My Work, Queue listings, user-defined queries, etc.)

• Fix issue where tab counts were not always correct.

• Fix issue where use of a caret (^) in searches would show an invalid search syntax error.

Changes of Interest to Developers

• Add DefaultOrderByClauseGenerator to allow for custom ordering policies in filters. The default sort order applies when an explicit sort order has not been set. For queries on workflow objects (case, subcase, solution), the default sort order will use id_number. For queries on all other objects, the default sort order will use objid.

Upgrading to Version 5.11.0

1. Apply Schema Changes.

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Update last modified timestamps for parts and part revisions

Update table_mod_level.x_modify_stmp and table_part_num.x_modify_stmp using the Update Timestamps SQL

1. Setup part searching.

   If using parts, edit Dovetail Seeker's documentSpecifications.xml file to allow for searching of parts. Within Seeker's documentSpecifications.xml file, include the parts specifications needed by Dovetail Agent, which are provided in the $dovetailAgent\source\config\seeker.config\seeker-part-domain-specification.xml file

2. Update contact searching.

   Edit Dovetail Seeker's documentSpecifications.xml file to allow for searching of contact email addresses. Refer to the $dovetailAgent\source\config\seeker.config\seeker-contact-domain-specification.xml file for reference Within Seeker's documentSpecifications.xml file:

   • include the email addresses into the contents:

     <contents>
      ...existing paths ...
      <path>e_mail</path>
      <path>contact2e_addr:e_num</path>
     </contents>
     

   • include the email custom field:

      <customField title="email" description="Email Addresses">
        <path>e_mail</path>
        <path>contact2e_addr:e_num</path>
      </customField>
     

1. Merge in your customizations with the baseline 5.11 source code.

2. Build / Test / Release / Deploy

Version 5.10.0

---

Enhancements

• Support for embedding YouTube and Vimeo videos on solutions.
• Support for Dovetail Seeker as an image file store when uploading images to solutions. Requires Dovetail Seeker version 2.3.0 or higher. Refer to the Resource Uploads application settings section for related configuration settings.
• Display a message when a resource URL (such as an image) isn't found or isn't able to load
• Assorted improvements when uploading images using the markdown editor
• Improve performance when loading the left sidebar of the home page, including loading counts for Queues and My Tags
• Improve the print formatting for cases, subcases and solutions
• Improved back button navigation after editing an item

Upgrading to Version 5.10.0

1. Apply Schema Changes.

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Install SQL functions

   Dovetail Agent uses user-defined SQL functions for certain operations. The functions are defined in the $dovetailAgent\source\config\sql{database}\toc-queues.sql file. Install these functions to your database.

   MSSQL: sqlcmd -UmyLoginName -PmyPassword -SmyServer -dmyDatabase -i toc-queues.sql

   Oracle: sqlplus myLoginName/myPassword@ora11 @toc-queues.sql

   These should complete without any errors.

3. Merge in your customizations with the baseline 5.9 source code.

4. Build / Test / Release / Deploy

Version 5.9.0

---

Enhancements

• Contract Functionality (Contract Manager, not ClearContracts)
  • Create, Edit
  • Relate to sites, contacts, site parts
  • Relate a contract to a Case
  • File attachments
  • Search
  • Show in Recent Items
  • On the site page, show contracts that cover this site
  • On the site part page, show contracts that cover this site part
• On the solution page, show the linked cases
• In-app Notifications (when user's notification preference is set to Notifier).
• Broadcasts - used to communicate a message to all users. It will appear in their notification drawer.
• On cases and subcases, show thumbnails of image attachments in the history and on the files tab
• On solutions, show thumbnails of image attachments
• Display images in a lightbox when clicking on an image thumbnail
• Support rich text (using Markdown) on solutions.
• Support for adding inline images to solutions. These images will be uploaded to an image file store. Currently, the only supported image store is Amazon S3. This must be your Amazon S3 account. Refer to the Resource Uploads application settings section for related configuration settings.

Bug Fixes

• Fixed a CSRF cookie bug that could cause users to experience a 403 - Forbidden error
• Better handling when Internet Explorer is in compatibility mode
• Edit employee page - sort privilege class list alphabetically
• Edit employee page - exclude inactive employees from the list of supervisors
• When relating/un-relating accounts and sites, properly handle the primary relation (primary2bus_org) and the OWNER bus_site_role.

Changes of Interest to Developers

• tabComponent changes. The onLoad callback now expects a value to be returned (usually the collection of the rendered view) to maintain tab counts.

Upgrading to Version 5.9

1. Apply General Schema Changes.

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Apply Database-specific Schema Changes.

   The database-specific (mssql/oracle) schema changes to be applied are defined in $dovetailAgent\config\schema\{database}\agent.{database}.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.{database}.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

3. Setup contract searching.

   If using contracts, edit Dovetail Seeker's documentSpecifications.xml file to allow for searching of contracts. Within Seeker's documentSpecifications.xml file, include the contract specifications needed by Dovetail Agent, which are provided in the $dovetailAgent\source\config\seeker.config\seeker-contract-domain-specification.xml file

4. Merge in your customizations with the baseline 5.9 source code.

5. Build / Test / Release / Deploy

Version 5.8.0

---

Enhancements

• My Tags page, for editing and deleting tags
• Parent/Child Sites
• Accounts functionality
  • Create, Edit
  • Relate to Sites
  • Relate to Employees (Team)
  • File attachments
  • Search
• Integration with Dovetail Agent Reporting module
• Notes field for a site
• Contact view includes the contact's avatar
• Ability to upload file attachments by drag-and-drop
• Add unlimited phone numbers, email addresses, and web URLs for sites and contacts
• Add an unsaved indicator on a query that has been modified but not yet saved.
• Added additional security when downloading file attachments to prevent mining of files.

Bug Fixes

• Fixed a CSRF cookie bug that could cause users to experience a 403 - Forbidden error
• Resolved an issue where subcase due dates could be set to an incorrect time

Changes of Interest to Developers

• baseContactMethod.js has been replaced by support/method/contactMethod.js
• contactPhone.js has been replaced by support/method/contactMethod.js
• contactEmail.js has been replaced by support/method/contactMethod.js
• AccountEndpoint.cs behavior has moved to SiteAccountEndpoint.cs
• queryService.js has been split into queryProxy.js and queryRepository.js
• Drag & Drop for uploading file attachments now allows for a visible dropzone. Pass a jQuery object as second parameter to upload#show to create a dropzone for that dom element.

Upgrading to Version 5.8

1. Apply Schema Changes.

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Import data files.

   • web_types.dat

3. Edit Dovetail Seeker's documentSpecifications.xml file.

   Specifically, edit the account specification, changing the idColumnName property from org_id to objid.

   The $agent\config\seeker.config\seeker-account-domain-specification.xml file shows the correct specification.

4. [Optional] Setup Agent Reporting

5. Merge in your customizations with the baseline 5.8 source code.

6. Build / Test / Release / Deploy

Version 5.7

---

Enhancements

• Added configurable password rules
• Add protection against CSRF (Cross-site request forgery) attacks
• Improved web application security within the web.config file:
  • Set the x-frame-origin to prevent click-jacking
  • Disable unused verbs
• Added an optional rewrite rule within the web.config file:
  • Remove the Server header which identifies this as an IIS server

Bug Fixes

• Recent Items - Better handling of unexpected data which could cause a blank page

Changes of Interest to Developers

• Provide a specific file for customer's custom CSS. Refer to the Dovetail Agent Developer Training Wiki for more details.
• Refactoring of CSS to reduce size and complexity
• Updated application dependencies (Javascript modules, etc.)
  • Marionette was upgraded to v2.2.0 (this might cause some incompatibilities with currently customized code, see the Upgrade Doc for details)
  • BaseHelper and BaseWorkflow's ItemView have been transitioned into Behaviors and no longer exist

Upgrading to Version 5.7

1. To take advantage of the web.config setting which removes the Server header which identifies that this is an IIS server, install the IIS URL Rewrite on your web server (if its not already installed).

   • Open IIS Manager
   • Click on the Dovetail Agent web application
   • In the middle pane, under IIS, look for URL Rewrite icon
   • If that icon is there, then URL Rewrite is already installed.

2. Merge in your customizations with the baseline 5.7 source code.

3. Build / Test / Release / Deploy

Version 5.6

---

Enhancements

• Impersonation - allows a user to impersonate another user.
• Notes are now required when performing a Reject or Forward workflow action
• When performing a Forward workflow action, the queue picker now excludes the current queue from the pick list
• A new CC tab on the site page. Contacts in this list will be automatically added to the CC list for log emails on cases and subcases.
• Search - better rendering of file results
• Improved the layout and iconography of the left sidebar of the console
• Support for Windows Authentication (Active Directory integration)
• When a web_user record is created for a contact (when a new login name has been specified), the initial password is set to a random string.
• Query enhancements
  • A new Queries page, allowing user to easily access My Queries, Subscriptions, and Shared Queries
  • Query results can be downloaded as a Comma-separated (.csv) or Microsoft Excel (.xlsx) file
  • Easily create a new query from the Queries page
  • Queries can now be shared to another user, to a workgroup, or to everyone
  • Shared queries can be subscribed to, which indicates that it's a query that you're interested in. These are queries that you may run occasionally, but aren't quite to the level of a favorite.
  • Queries can now be favorited. Favorite queries are queries that you run frequently, or want easily accessible. These show up in the left sidebar under the Queries heading.
  • Workgroup is now a system defined query, available on the Shared tab of the Queries page
  • Sort order is now remembered for each query for each user
  • The Item Type filter shows the list of valid values (Case, Subcase, Solution)
  • The Workgroup filter now allows a user to select {{MyWorkgroup}} which is dynamically resolved to the current user's workgroup name.
  • The Owner Login Name filter now allows a user to select {{MyLoginName}} which is dynamically resolved to the current user's login name.

Bug Fixes

• Resolved an issue where items could be duplicated (on the page, not in the database) on the case/subcase/solution history when the history automatically refreshes.
• Resolved a character encoding issue in the preview pane
• Prevent items from being forwarded to the same queue that they are already in
• Prevent items from being assigned to the current owner
• Resolved a pagination issue with queries on Oracle databases
• Resolved an issue where the password reset URL could be incorrect in a web farm environment. A new web.config setting of WebsiteSettings.PublicRootUrl was added to address this issue.
• Resolved an issue in the wipbin2tag.js script that would output "undefined" rather the correct username. This was only a problem with the output - the actual processing worked as expected.
• Resolved an issue when using mixed-case login names which could cause some parts of the application to not function properly, such as actions that compared the login name of the currently logged in user to a login name in the database.

Upgrading to Version 5.6

1. Apply Schema Changes.

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Run upgrade script

   • The upgrade script is located in $dovetailAgent\config\scripts\upgrade\5.6
   • Be sure that the Dovetail SDK is installed on the machine running the upgrade script
   • Edit the fc.env file, defining your database connection information
   • From a DOS prompt: cscript upgrade.js

3. Import data files.

   • user_impersonation_activity_codes.dat
   • agent_basic_data.dat (for the Impersonate Employee privilege)
   • WorkgroupQuery.dat

4. Add the canImpersonate custom field to the employee document specification in Dovetail Seeker's documentSpecification file. The custom field specification can be found within the $dovetailAgent\source\config\seeker\seeker-employee-domain-specification.xml file.

5. Grant the Impersonate Employee privilege to the desired privilege class(es) using Dovetail Admin.

6. Merge in your customizations with the baseline 5.6 source code.

7. Build / Test / Release / Deploy

Version 5.5

---

Enhancements

• Console (Home Page) enhancements
  • Additional data for cases, subcases, and solutions are now included in the grids
  • The currently row is highlighted
  • Selected rows are now highlighted
  • Users can now configure their console by:
    • Showing/hiding columns
    • Reordering columns
    • Resizing columns
    • The user's console configuration is automatically saved
  • Preview Pane enhancements
    • Removed summary information (as this information is now in the grid itself)
    • Show full history information (previously, each history item was truncated after so many characters)
    • Users can now resize the width of the preview pane
    • The user's preview pane width is automatically saved
  • Recent Items. The user's most recent items (items viewed in last 30 days) are now easily accessible.
  • The number of items shown in the grid will be dynamically adjusted based on the height of the browser window.
• Standardize the wording for Solution Public Availability throughout the application

Bug Fixes

• Gravatar links now use HTTPS when the Dovetail Agent site is configured for HTTPS

Upgrading to Version 5.5

1. Merge in your customizations with the baseline 5.5 source code

2. Build / Test / Release / Deploy

Version 5.4

---

Enhancements

• Ability to reverse the order of case/subcase/solution history
• Ability to view all activities within case/subcase/solution history (business rule actions, custom activities, etc.)
• The queue picker will show all queues by default (when dispatching an item)
• Users can now pick an existing tag without having to re-type it
• Tags can be added and removed from multiple items at one time using the batch actions menu
• Task Manager. Users can now pick a task set to be run for a case.
• Commitments
• My Calendar

Upgrading to Version 5.4

1. Apply Schema Changes

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Import Data Files

   Import these data files found in the $dovetailAgent\source\config\dat directory:

   • agent_support_data.dat
   • commitment-rule-properties.dat
   • commitment-templates.dat

3. [Optional] Setup Task Manager

4. Merge in your customizations with the baseline 5.4 source code

5. Build / Test / Release / Deploy

Version 5.3

---

Enhancements

• Wipbin to Tags conversion utility
• Improved the Developer Setup documentation

Developer Concerns

• Replaced the Spark view templating engine with Handlebars
• Improved the list helpers for both single-level (application) lists and hierarchical (multi-level, user-defined) lists.

Upgrading to Version 5.3

1. Apply Schema Changes

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Merge in your customizations with the baseline 5.3 source code

3. Build / Test / Release / Deploy

Version 5.2

---

Enhancements

• Auto-Destination functionality
• Log Research functionality for cases and subcases
• Close Case form (status, resolution, notes) when closing cases and subcases
• Select a site part for a case
• Site Part (Installed Part) view and edit pages
• View site part information on case page
• View site parts on site page
• Improve user experience when console sidebar parent items (Favorite Searches, Saved Queries, etc.) have no children
• Improve the print formatting for cases, subcases and solutions

Upgrading to Version 5.2

1. Apply Schema Changes

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Merge in your customizations with the baseline 5.2 source code

3. Build / Test / Release / Deploy

Version 5.1

---

Enhancements

• Improved the content and layout of History for Case/Subcase/Solution
• Improved the calendar control
• Styling improvements throughout the app
• Improved custom query experience on the console
• Improved filtering on the console
• Adding filtering functionality to the following lists

  • Subcases in the Case view
  • Sites in the Contact view
  • Recent Cases in the Contact view
  • Contacts in the Site view

• Added infrastructure for supporting multiple languages. Language Packs will be available in a future release.

Bug Fixes

• A favorite search could lose its favorite status when the same search was performed manually
• Renaming a Query on the console now works properly
• Sometimes navigation would behave strangely when going 'back' in the browser
• Other minor fixes

Upgrading to Version 5.1

1. Apply Schema Changes

   The schema changes to be applied are defined in $dovetailAgent\config\schema\agent.schemascript.xml The easiest way is to simply apply these changes using Dovetail SchemaEditor and the agent.schemascript.xml file - it will add the new schema and skip over any changes that already exist.

2. Import Data Files

   Import these data files found in the $dovetailAgent\source\config\dat directory:

   • localizations.dat
   • user_defined_lists.dat

3. Merge in your customizations with the baseline 5.1 source code

4. Build / Test / Release / Deploy

Version 5.0

---

Dovetail Agent 5.0 is a completely redesigned user interface and architecture.

On the back end, it uses the FUBU MVC Framework, which is a popular .NET framework for building web applications. It's built on top of the core ASP.NET libraries. The back end is all written in C#. On the front end, is HTML 5, CSS3, and JavaScript. It uses the Backbone JavaScript framework, along with a boatload of other common JavaScript libraries, including Require.js, jQuery, Marionette, Underscore.js, and Moment.js. In short, all leading-edge technologies.

Features

For specific features, view the High-level functional comparison between Clarify and Dovetail applications