ECALDIMA 2.0 SP1 Release Update – July 23, 2017

New

Service Catalog

  • The request view page has been redesigned to be easier to read.
  • Launch SQL scripts from an external task.
  • Generate PDF files from a request using an external task.
  • A new external task type permits the creation of TIMA Tickets within a SCOOP Process.
  • In the admin menu, a form is now available to force closing a request.
  • Attachments can now be sent with Notifications. Add an extended property “AttachmentFieldsId” to the service with the list of attachment fields separated by a comma.

 

Ticket Management

  • Fields associated to a service creating a TIMA ticket are displayed in the User view and the operator view.
  • Fields associated to a service creating a TIMA ticket can be used in conditions for actions.

Common

  • Drilldown report view allows to use reports that receive variables on the URL. This is useful for detail reports such as number of tickets by location that drilldown to list of ticket for the location.
  • The resources files are available to be translated and compiled if it’s necessary to include a new language.
  • A unique URL can be used to open a request or a ticket. If the user opening the ticket is member of the TIMAOperators groups then the ticket will open using the Operator view. This link can be used in reports.

Improvements

Common

  • A page displaying the status of the installed licenses and offering the possibility to load new key files is available in the Admin menu. A scheduled task sends an email when the number of used licenses reaches the 95% or 5 days before the end date.
  • In the right click menu of the Manage Menu form, it’s now possible to add a group to grant access permission.
  • In case of multiple installation of Ecaldima using the same database, the Scheduler must be activated in only one installation. An entry in the web.config allows that. (add key=”DisableScheduler” value=”true” in AppSettings)

Ticket Management

  • Internal comment check box can be checked by default. In configuration, set the Key “InternalCommentChecked” in the “TIMA” section to “TRUE” or “FALSE”.
  • Ticket can automatically be closed after a specified number of days in the “Resolved” status. Set the Key “NumberDayAutoClose” in the “TIMA” section of the configuration to the number of days to wait or set to 0 to deactivate the functionality.
  • In the Send Email action, the checkbox to select the validator is now available.
  • It’s now possible to add attachments in the resolve form allowing to do all in a single action.
  • To limit visibility of tickets to the requester or the end-user only, set the Key “RequireAffectedOrRequesterForUser” in the “TIMA” section to “TRUE”, and set it to “FALSE” to disable it.
  • The creation of tickets by mail can be disabled so that tickets are only updated. The checkbox is available when creating or updating an Inbox.
  • A ticket can be put on hold from the Classify action.
  • Changing the end-user of a ticket is accessible from the classify action.
  • The checkbox “Skip resolution” can be checked by default based on the configuration. “CloseDirectlyChecked” ” in the “TIMA” can take the values “TRUE” or “FALSE”.
  • The status of a ticket is now available close to the title.
  • The dropdown to search tickets in the operator dashboard searches also for requests.

 Service Catalog

  • Log4Net formatting of logs is available for the PowerShell Scripts launched by an automated task.
  • The request view can be adapted for each service, copying the original RequestView.vbhtml file, making the required changes and creating an extended property named “PROCESSVIEWPAGE” with the name of the copy as the value.
  • People can copy and paste images and rich text in the validations and tasks comment field.
  • The new “Add comment” link in the request view permits to add a comment to any request. It can be hidden using a service extended property named ”HIDEADDCOMMENT” set to “TRUE”.
  • 4 new assignment rules are now available:
    • End-user location manager.
    • Requester location manager.
    • Users based on an extended property query.
    • Groups based on an extended property query.
  • External tasks can be marked as finished from the request view page. This way a member of the SCPManagers group can close the task and the process goes on. It’s useful when an external task could not send the end status or is taking too much time.
  • Extended properties can be associated to external tasks.
  • TIMA tickets can be linked to requests. The selector in the classify action allows the selection of requests. A link appears in the request view page and in the incident page.
  • Groups available when reassigning a task or a validation are filtered on the Scope attribute so that Ticket Management group are not displayed.
  • In the automated task, it’s now possible to include tokens in the constant mapping. For example, in the Create PDF task, include the ´{USRFIELD_23}’ token in the file name constant.

User Management

  • A button is now available in the user index page to reset the password for users not coming from active directory.
  • In GroupAdImport and UserADImport the password is now encrypted.
  • Users are disabled during the AD Import if the account has been removed from AD.

 Designer

  • Categories can be sorted from the index page of the designer with a simple drag and drop.
  • The test query results table in the SQL fields configuration is better formatted.
  • The field description is displayed in the selector in the field tab in Service and Article.
  • The template ID is displayed in the notifications list.
  • The Service and the Article process are saved only if there is a change avoiding the renumbering of nodes.

FIXES

Asset, Contract and Stock Management

  • A validation message is displayed when entering amounts greater than 999.
  • In the Asset Dashboard, the chart Assets by location displays Assets by department.
  • In the Asset index, actions are only available when the checkbox All is checked.
  • In location details an error message prevents view the page: “<” is not valid at the start of a code block. Only identifiers, keywords, comments, and “(” are valid.
  • In the edition of a company an error message prevents saving the information: The property ‘CompanyId’ is part of the object’s key information and cannot be modified.

Common

  • In the menu configuration, adding an action results in a reportview action.
  • In the menu, the group applied when creating a new menu is always the first in the list instead of the selected group.
  • The LCID of the user viewing the login page is always 0.

Designer

  • When creating a field, the data type is not always available.
  • Multiple Level Selector not working. Query not saved, and in fixed mode, the Value is not saved.
  • A value greater than 999 cannot be entered in an integer field max value.

 

Ticket Management

  • The event “On Ticket to be validated” is not fired.
  • Ticket resume is not available for ticket on hold (400 status).
  • In ticket action events, disabled actions are visible.
  • The user selector in the assign action allows to assign to non-operator users.
  • In the conditions of ticket actions, HTML code cannot be used. For example, it not possible to use a condition like “Comment is <br>·.
  • The date format when parsing macros in TIMA is always en-US and it’s a problem for platforms using fr-FR for example.
  • Conditions on Boolean field do no work. For example, on Internal Comment.
  • In the Ticket Schedule action, dates are not saved in other language than en-US.

Service Catalog

  • When a service has more than one article and one of them without a process and no start process, nothing happens.
  • Groups in Notifications do not receive emails.
  • When an article process stops on a skipped task and it’s the only process on the request, the requests stays open.
  • In the tasks and the validations, the variables used are always in English. This happens when using a fixed values radio-button list for example.
  • The quantity does not appear in the request view.

OPERATIONS

Upgrade

Before upgrading your Ecaldima installation from Ecaldima 2.0 to Ecaldima 2.0 SP1 (2.0.1.0), take these actions:

  • Backup your database.
  • Backup the Ecaldima installation folder.
  • Copy the customization you made in a safe location.
  • For unsupported customization, contact your reseller before applying the update.

To upgrade, launch the SP1Update.exe file available in the Wiki.

Installation

Instructions for the installation are the same as for the Ecaldima 2.0 version.