Skip to main content

Note: All the features/enhancements below will be available on Starter and Growth plans on August 19th, 2024 & on Pro and Enterprise plans on August 28th, 2024.

Product version: 2024.R08L.01

 

New Features and Enhancements

 

Multi-language support for custom fields in Problem, Release, and Change modules 

Category: IT Service Management

Users can now translate custom fields in the Problem, Release, and Change modules to any Freshservice-supported language. This functionality was already available for the Tickets and Timesheet modules. The translation process is managed via a YAML file upload, which allows you to define translations for all fields and their respective choices for all the Freshservice-supported languages.

 

Revamped admin experience for ServiceBot

Category: IT Service Management
ServiceBot is a channel with essential functions like ticket collaboration, ticket updates, virtual agent support, and on-call management. The new unified admin experience allows users to set up, manage, and customize all these features seamlessly in a single, streamlined flow. To get started, navigate to Admin > Channels > ServiceBot for MS Teams.
Note: This is currently available only on MS Teams

More details here.

AD_4nXfsBn38hnWPrSKB7SdA5XldfMbnsEZiCL5fiZIIwfYYeeWxEiFw5cpbwoqrtLWvYl_j3mO2J_9cZGQNHSbYyb_ZkyQQdszbGPrfqQDq9kVj-Ym7bIKKYJFSEWh8-mxxn2-bT4AjQzQmRX2Y6GuYsDKOgona?key=1oUNl0Sp7HI3nbkFsHnEEA

 

.NET security upgrade for Orchestration Server

Category: IT Service Management

We've upgraded the .Net Core version used in the Orchestration App Server from 3.5 to 4.8.1 to enhance security and to comply with the latest standards. This update is essential for those who use on-premise orchestration apps.

What Needs to Be Done?

  • Existing Customers: Uninstall the current Windows Installer version and install the latest one.
  • New Sign-Ups: The latest version will be automatically available for download.
     

MS Teams Orchestration app enhancement 

Category: IT Service Management

A new version of the MS Teams Orchestration app will be released, featuring all existing functionalities and essential updates to maintain seamless operations of the "Post Message" action, which is impacted by the MS Teams connector deprecation.

Action Required for existing customers: Configure the new "Post Message via Power Automate" action before Microsoft's deadline on 1st October, 2024. 

More details here

 

Private Notes edit access enhancements  

Category: IT Service Management

Users who have ‘View’ access to the Problem, Change, and Release modules will now be able to add private notes in these modules.

 

Clone nodes and workflows in Alert Workflow Automator

Category: IT Operations Management

Users of Alert Workflow Automator can now clone individual nodes within a workflow or duplicate entire workflows, saving time and effort in setting up similar processes.

AD_4nXeTO-nyVHRNaQb4lMMr5QF9Q4Uw0pogZO6i0uPS0lfIeRjRtQ067PhGmyzoGqP9jhukpsPtNT51T901iVQjdoUt6N7ol1DmK2BYanK9I3LAZrgp1SaJBbsvlWGOwyUKDuCKL2nlQT9hQ3DW6B1FnZiOuzPx?key=1oUNl0Sp7HI3nbkFsHnEEAAD_4nXdZhlb6gdKqcibv8RibnCSF0izAkQ5-4k8H_72otjUJWgQSIMWHhclMaGEkd_Mc3u4s4MEZNhll1ciZbeBxgwihkQ0p5I5AmrKMHPSNQfdAM1Ja34X0Ovs7OfIk3r-xXIVyUxMXohiAK46SKMuQiSKZvg5H?key=1oUNl0Sp7HI3nbkFsHnEEA 

 

Trigger workflows on alert acknowledgment

Category: IT Operations Management

Users can now trigger workflows when an alert is acknowledged. This enhancement gives them greater control over alert workflows by automating responses, specifically when an alert is marked as acknowledged, improving workflow precision and efficiency.

AD_4nXcgm6Fr9okod7nHlwJFZcx97wtNvS6fzZB-m2jA4hJ9z-K9K7wRb9zJ_OpZc4wq0sNw7xZZQ16eGQizZyZS7dYyVtq0NEz74XWcr-15zK306jecw6RrT-dVIrWRNMJrgePC2K3T6KAqfdPJmB5nvdPcMI2k?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Increased character limit for metric values

Category: IT Operations Management

The character limit for the metric value parameter in alert fields has been increased from 100 to 255. This enhancement allows for more detailed and descriptive metric values.

 

Embeddable status page widget & badges

Category: IT Operations Management

Users can now embed Status Page badges and widgets on any webpage. This will help them update end-users about outages or maintenance directly via customer-facing websites and internal portals without making them visit the status page. This enhancement will improve the end-user experience and further reduce the number of support tickets.

More details here.

AD_4nXcmzE1Spe6hIytWc6YNgbpfTpzTKKRzz6_oR9likWjp9PE_DWEJschkERXmVsmJ28uRDKLfNWRH4do8-Px6oKiF8Wht4-ZRbspWIvpYdDUwfrBNFjbYmT6PzL9IthikFILJJzBougmUAo-3Z15hJHYzRpc_?key=1oUNl0Sp7HI3nbkFsHnEEAAD_4nXcj9RDmh8DwSecS1DIEn8mRfLJbn-aLQfdp51REPhn5SUnoSG91BJNp_7VGb122uq3NbIL0_InARKGPTBLwAUlb9w1q3qVydWNwvhSCrhTWbbYfkfB6DDLRBfnY4f-XlztRPmc2SoQZAEf_wNOdh_Ya0NUS?key=1oUNl0Sp7HI3nbkFsHnEEA

AD_4nXf7N5nE2PfCHC72eovS5tgcArvp6IxAnqoG4So2e4gRMKR9bfNWOiAy4sjbQ0jdqmVJouU3z6Byncr0Ua7-E1VLNQ7gxnbqcAd-iLH-B6OjH030PqeyvUck37vrso4scmrFXAKDCB4mjl5Zj6yytiP-O3HQ?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Post-incident report list page

Category: IT Operations Management

Users can now access all post-incident reports in one place via the reporting menu. They will no longer have to access each major incident separately to get the associated post-incident report. This capability will help users save time and make better deductions about the efficacy of their infrastructure & operations.

AD_4nXdIkYaWq5MxdQEaI9k-NRUaae-PjaQeMCEmtAa0Dx0Fv8kSkAPG_WxHleG8gqocFYHUNpU9QglKwSXUCyBYU5-qss5Ri6kbc3PSuC8cH_5sOxy9KBRtPLFftYpeIVyJBYaMIl2C8bEeJFVJIIwJ7uWri9l7?key=1oUNl0Sp7HI3nbkFsHnEEA

AD_4nXdlX-6_nqFlzGDZ7rYBmmY_VSYfglhvc3k21eSgbIeBV8tUkLmHRoaMN7P0G5xH2O_mnMg2ZcHmJJeA7UAd0sw7mgLgwxz8XZ_sOdbuB_bUMcd3NzfoMrozJFjjFW0oKpIEGgLQeL0AumY1sNVREu_ERmyJ?key=1oUNl0Sp7HI3nbkFsHnEEA


Enhanced setup and security for Windows Agent and Probe

Category: IT Asset Management

This enhancement introduces an additional layer of security for new installations of the Discovery Probe and Windows Agent. It will not affect any agents or probes that are currently installed.

For new installations, users will need to complete an extra step. During setup, a user will be required to copy a registration token from the application and paste it into the installer when configuring the Discovery Agent or Probe.
More details here.

AD_4nXejOjr_jGUzL7cGvxIg4VjdE7xrwF6yfqZLzFtqwW6491fTaPPSbbZjpYMOIRpMgn9bnuMdkT7fnjjItL1wUJm3bnEPgfM2eGEdDw0nQr_GosoZfHKsIwYgNVmchxCBZ9Sbzde57s-zVPVujAI0nmVDzUd9?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Discovery Probe Enhancements 

Category: IT Asset Management

The following enhancements are designed to improve troubleshooting and streamline error management in the Discovery Probe.

  • Improved Device List Accuracy

The devices tab now displays only devices that have been successfully scanned at least once and will thus also indicate how many assets have been synced to the CMDB.

AD_4nXd52QVIxtg6XoC8UTetnVdeb7gNwKItgm7aqw53wwI1M3BwCY0CVuty-J-Skp1hFdwQq2gCKPBynQ0ShZqKAFjSeLViV0tWtfIm35jXj1GTNzHbwk7x_VPsM2h14LppaI9vMm_7x8xSh0CdQKurqJubSlLo?key=1oUNl0Sp7HI3nbkFsHnEEA

  • Streamline Error Management with Advanced Sorting and Filtering  

Sort and filter devices by type, model, and scan time to better manage and analyze assets across both devices and error tabs.
AD_4nXc-QMEl08tMLfnORlZIbQsXCoE-_DhSzPh8ai8AEA_ARdSahDHlbuPJnt0o05EhKzwq0AFeIPpTPwrp4Cbh7uvVYVFwwVqGwzaJqhLQg5qba44CPs9xxoxqgn2oHpQy2rm9_qdj4os2zc5HQ-7zTaHfkJ3x?key=1oUNl0Sp7HI3nbkFsHnEEA

AD_4nXdsKVn-GS9s4kNKCQTrd-H8V_L1HIyXHFZgeM_kEt7orWeQbjKwT2H_ZiGCx69Im_TwM5hcla7kyO-wlFDIG5ieKLCu8reggxyqfleiahhBS9ONTY4uZpdcLQ4P760nZDcOD8cFOIP_HvWtsMIou3LTRyo?key=1oUNl0Sp7HI3nbkFsHnEEA

  • Ability to clear out stale error entries

Review and remove errors from the Errors tab, with the ability to select and clear irrelevant errors in bulk, keeping  error list up-to-date.

AD_4nXdK7jCFzKbaFHjx4PV9MUmMMBzEkDWKwcmdG8qqc2APT1l2fjrsnjQDmP0mueHhpLJtFj-WqvOo7jqenAuIGePcNEME3rjBMbIYOL5ItsJKnGKjJdKc5EJ3118mKixL6Usx5Lv-0waFyj0NqYTliC9Vcs_V?key=1oUNl0Sp7HI3nbkFsHnEEA

  • Resolve Issues Quickly with Troubleshooting Guide Links

Access a hyperlink to the Troubleshooting Guide directly from the error message column for faster issue resolution.

  • Get Detailed Insights with the new Scan Message column

This column summarizes the steps taken before failing to scan a device within the probe console, thus providing rich insights for troubleshooting.

  • Improve Scan Accuracy with NMap Version Upgrade

Benefit from enhanced OS detection capabilities with the upgraded NMap version, resulting in fewer generic error messages.

 

Intune integration enhancements 

Category: IT Asset Management

  • Daily Device Sync

Configuration Items (CIs) will now be synced daily to ensure they are always up-to-date, providing more accurate and timely updates to asset data.

  • Enabling Software Sync

Software sync is now enabled, allowing for comprehensive tracking of software installed on devices, ensuring thorough asset management.

  • Sync Ownership Info Based on Primary User

Ownership information will now be synced based on the Primary User in Intune, rather than the Enrolled User, providing a more accurate representation of device ownership.

  • Flexible Device Sync Options

The integration now supports syncing just computers, mobile devices, or both, offering flexibility to tailor the sync process for specific needs.
More details here

AD_4nXfiSrpe0wIXGx8ZuGBAl4SAK_8nShYG2ckRJnHaxROSE9LS5i9TaNjg1pyxOC_ABXb0Qo0Ghik2f_EXNKA1wlmcL5oLkRmr_tpCRg9IoctKYyua60jKvvF5OM5o53fJTgR02mgiHmo_OwWXxSrVujP30d9h?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Asset activity reporting

Category: IT Asset Management

Activities serve as a repository of all historical changes to an asset over time, providing significant value for auditing purposes. Asset activities are now available in analytics, unlocking use cases such as:

  • Export activities across all assets for the last X months.
  • Track specific attribute changes for an asset, such as Location, Department, and Used-By.
  • Understand how many assets were deployed or retired over the past months.

More details here

Note: Analytics can report only on the last 12 months of asset activities, so ensure this data is leveraged periodically.

AD_4nXdTY7gPOxtCS1xVZdXWKSmJI8lex6ir-wERRWgnpePYsgtESqyKyXTFo99bTSu2hPTwFUlPnw33a08HMrGSwyzgIxJhhg6_LJRAGUgQ_JfJLFBc4jilyRziT8k1DhVrc6b4wEMQUyTt96fNME2bXGRBTEn9?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Automate SaaS actions with Scheduled Workflows

Category: IT Asset Management

We've introduced SaaS-based actions in Scheduled Workflows, allowing IT admins to automate processes across SaaS-based applications and users. This streamlines operations, reduces manual effort, and ensures consistent execution without the need for constant monitoring.
Sample use cases:

  1. Admins can harvest licenses (de-provision users) based on SaaS app usage percentage
  2. Send email notifications to Software Users using specific apps (restricted/blacklisted apps, nearing the end-of-life apps, etc.)

AD_4nXcSwKS5ZuG5w7tMo-zLtHkh8udn50jy8y-IVrpOv0bSmsr9pY6MfT6ZJ1D0xIB2XWMW8Nf07kT4-9GHNKzT-XBR46ch0arL3dtWbgoHgX_dSCBdpPaeyXEpYV3J8ohKECmdPtZH4-uQl7spA2iscdpYV6Pw?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Reorder service categories on the support portal

Category: Freshservice for Business Teams

Admins will now be able to configure the order in which service categories appear to requesters on the support portal. This allows admins to optimize the user experience and make employee services easily discoverable.

More details here

AD_4nXe5d0uo66qagBLio-P8quXzJFpjtbhBGut0k_hh8e7cd-u6SpO4Rlr2hipcKjNOqyGaU5pMmJ_P3mYvW57_hmVvGb3BNfDKO4QXi5FtwHwpFFGukV9_kDtmUAA4HX3xQAhjliMUZul_wXhz-iFm7PDoZCM?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Reorder workspaces in the ticket form dropdown

Category: Freshservice for Business Teams

Admins will now be able to change the order in which workspaces are listed on the ticket form. 

More details here

AD_4nXe2gMWpYLjrxJb61E7ZXVGI4s03Mq5iHlRaWr81UFdnvMS2Z6RTqMk4OSlufRo8zn4VF6txDolXWczAjzwp55lCUwNMP1naDqTx4zXRL0BzlQl1g2L3IUvYyXzxZu6qiA_xF8xY4-kkumtpLi2xPjGT9EdF?key=1oUNl0Sp7HI3nbkFsHnEEA

AD_4nXf9dR5XvGzMlsSdCiLxXNEQFIsfQG4pUYdcmAZoRdqJJZfWam1IZJ3WDtj8sHhBfKEQ8VxSNYPpEVg-nKAiu-Dcyd76WhDVhoxZagjjgedx0iy7FOpR9XiJIjlDzvH0iT5P_4UtQPVNBS0iWJt5ru1hEWSe?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Move business teams from primary to new workspaces

Category: Freshservice for Business Teams

With the Workspace Organizer tool, admins can now easily copy over the configurations and move the tickets of their business teams from the primary workspace to new workspaces. Starting August 30th, 2024, this tool will be released only to accounts that had onboarded their business teams (non-IT teams) before the release of workspaces and have these teams currently functioning out of their primary workspace. 

More details here.

AD_4nXe2aE4q8Ttv-EStfH4NOzTh0VJ8Znp9UrGLnjwTbZ-ye_nZ6OkigJGII8WKEPmqAXlKHzsGJiN5Q6oaxQedNQl_0e_aMgJdcAR2KCnLj4vQwKYP_kNKAlpptm6fHJV9UaIAvevnSKXrig4mUwonntZh4BUx?key=1oUNl0Sp7HI3nbkFsHnEEA

AD_4nXca2K2xHMwF-Ld01q4CYbx1C2EYWCf6VqLHnFrWBO2yYNWiNuilPt68o5mOqcky7XQT8gN_IumfllwkmduOG7wOk9CQWtyy7kOpyAxnLbzCIpz0mIH9S7NfaiyIEpTrNEJ1tJO6_PQkw_-AWvEW_LHimhWI?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Track and manage eSignature usage

Category: Freshservice for Business Teams

Admins can now monitor eSignature usage with a dedicated report in Analytics and track usage per workspace within the Document Template setup. Each eSignature Pack includes 30 signatures for $90, with recurring billing to maintain the signature quota. All accounts receive a one-time bonus of 30 free signatures to get started.

More details here

Note: This feature is available only for Pro and Enterprise customers.

AD_4nXdfBWswSFhuKN7FY5VZGbJ3qplc-cG-n7W-Vwf7KIwhRRDCwykL9w3qUEkffhJlOQcI1c5BSFx6X3gZ1Tk1ZJRKEVbFv-z9GN5j2AAxtTO4Pl_NkZ3_XoKhx5DFbBen_Etij3xOhFjTEN9m07-CXSMQ5jcC?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Curated report on Project Time Entries

Category: Project Management

With an out-of-the-box curated report on project time entries, users can now keep track of the time that agents spend on a project or the total time they spend across projects. Billable and non-billable time entries can also be tracked across projects. This gives managers complete visibility of the hours logged by agents via the captured time and date details.

More details here
AD_4nXf2NmBWq6vB1yIP8gsePonSKUOBdVVo5ynoppDwvfDMClFprL3AtNoHLKmamCduNB7Oboh6D1AdNZ73nl2lldvfccr3YerDdDdgpeFLcUK3YfeDphqtSW1LFLmn2nk-z8lAc5_ZLpHGSe8hIDP-uzcB7ou_?key=1oUNl0Sp7HI3nbkFsHnEEA

 

Important Updates

Notices for new changes/upgrades/deprecation activities

The following changes will be made effective by Nov 5th, 2024. Ensure that you’re prepared for it.

  • Fair Usage Policy (FUP) for Freshservice Analytics

To ensure that all our customers have an uninterrupted, performant, and smooth reporting experience, we are implementing safeguards in some of our analytics capabilities starting Nov 5th, 2024. Please note that there is no immediate impact to your existing reports. You can continue to create and edit reports without any restrictions.

Who will be impacted?

If you have created reports, data exports, or schedules in Freshservice Analytics that violate the Fair Usage Policy, you will be impacted by this change.
What do you need to do?
Ensure all your reports adhere to the FUP before Nov 5th, 2024. Follow in-product instructions displayed starting May 16th, 2024, and resolve FUP violations.
More details here.

  • Discontinuation of Legacy Versions of Marketplace Apps

We will discontinue legacy versions of a few Marketplace apps to ensure that you get enhanced and consistent app experiences. To ensure that these apps work as expected without disruptions, you will need to upgrade them by Nov 5th, 2024.

Who will be impacted?
You will be impacted if you are using any of the older versions of these apps.
What do you need to do?
Upgrade to the latest versions of these apps.

More details here.

  • Discontinuation of AWS Orchestration App

To ensure that you get both Cloud Discovery and Orchestration capabilities in a single Cloud Management app, the AWS EC2 - Orchestration app will be discontinued on Nov 5th, 2024.

Who will be impacted?

If you use the AWS EC2 - Orchestration app (for cloud asset actions and custom workflows), you will be impacted by this discontinuation.
What do you need to do?

You can install the new AWS Cloud Management app and uninstall the AWS EC2 - Orchestration app.
If you have workflows that use nodes from the Orchestration app, replace them with new nodes from the AWS Cloud Management app.

More details here.

  • Deprecation of the current Sandbox version

To ensure you experience the enhanced capabilities of the revamped Sandbox in Freshservice, we will be deprecating the current version of Sandbox by Nov 5th, 2024.

Who will be impacted?

You will be impacted if you have an active Sandbox created using the current version on or before Nov 5th, 2024.

What do you need to do?
If you have an active Sandbox that belongs to the current version, you can destroy or sync it to enable the revamped Sandbox version in your account.
For example, If your account has Sandboxes across three workspaces (Global, IT, and HR), destroy or sync all of them to access the revamped version.

More details here.

 

Bug Fixes

These were the product defects detected, and they have now been fixed.

  • The newly introduced field ‘Approval status updated at’ in the Analytics module will now capture accurate (real-time) timestamps of a change request whenever the approval status is updated. The existing field ‘Approved Date’ which captures the timestamp of the Change when the approval is moved to 'Awaiting Approval' status,’ will be renamed to 'Moved to Awaiting Approval On' under Analytics.
  • In a multi-workspace account, if agents updated assets in bulk, they received an invalid workspace error. Now, agents can update assets in bulk without facing any issues.
  • Due to a bug, ‘Ticket Forms.Service Item’ & ‘Ticket Forms.Service Category’ were introduced in Business Rules. These two fields have now been removed to avoid any confusion. 
  • When two requesters being merged are present in multiple Freshservice accounts but not in non-Freshservice accounts in the same Freshworks organization, merging was not supported. Now, the requester merging will be allowed in such scenarios.

So the following issues are still outstanding…

1.) Tickets should not be closed by agents, they should be resolved. You can hide the close button when viewing a single ticket from the agents via business rules, but they still have the ability to change the status to closed in ticket list view. Also applies if you have any particular statuses you might not necessarily want agents to be able to use (we have a couple we use within workflows that are hidden via business rules).

2.) No resolution to prevent users bypassing SSO if their email domain is a specific domain such as your organisation email domain. We don’t want to allow users to bypass our SSO, as it means they can log in with email and password, which is easier to breach. Security risks don’t seem to be that critical in Freshservice…?

3.) Unable to download all attachments on a ticket if say >10 are attached. So long-winded.

4.) Servicebot for Slack is clunky - Does the MS Teams variant have more importance?

5.) Sorting useful columns in ticket list view such as State and Assigned to STILL not possible.

6.) Certain placeholder text defaults to Times New Roman which is a horrible font to read. Why can’t it use the default Segoe UI font that is available elsewhere?


So the following issues are still outstanding…

1.) Tickets should not be closed by agents, they should be resolved. You can hide the close button when viewing a single ticket from the agents via business rules, but they still have the ability to change the status to closed in ticket list view. Also applies if you have any particular statuses you might not necessarily want agents to be able to use (we have a couple we use within workflows that are hidden via business rules).

 

We work around this with a Global Workflow:
Event: Status is changed from Any Status to Closed
Condition: Ticket Fields.Type is not Major Incident 
Action: Set Status to Resolved.

 

Agents can still Close a ticket, but the automation immediately changes it to Resolved. 

The Supervisor Rules then change it to Closed without any issues.

Major Incidents are excluded from this Workflow due to needing to be manually moved to Closed once the PIR is published.

 

 


Please review my idea for the ability to decommission services and software.  Status for deprecated items (assets and services) | Freshworks Community

Unless I am missing something, there is no way to disable a service other than to delete it.


What about being able to sort by start date or possibly others in the onboarding module!!


So the following issues are still outstanding…

1.) Tickets should not be closed by agents, they should be resolved. You can hide the close button when viewing a single ticket from the agents via business rules, but they still have the ability to change the status to closed in ticket list view. Also applies if you have any particular statuses you might not necessarily want agents to be able to use (we have a couple we use within workflows that are hidden via business rules).

 

We work around this with a Global Workflow:
Event: Status is changed from Any Status to Closed
Condition: Ticket Fields.Type is not Major Incident 
Action: Set Status to Resolved.

 

Agents can still Close a ticket, but the automation immediately changes it to Resolved. 

The Supervisor Rules then change it to Closed without any issues.

Major Incidents are excluded from this Workflow due to needing to be manually moved to Closed once the PIR is published.

 

 

 

We found if the ticket was already closed, and agents went into it, it would show as open. We found this to be a suitable resolution to hiding the closed status.

 


5.) Sorting useful columns in ticket list view such as State and Assigned to STILL not possible.

attempting to be helpful here, you could filter on these columns and then save it as a view.  I’ve done this with lots of those categories and it’s been easier for me because you can even save how the other columns are sorted so that they’re in the order you want.  I just switch back and forth between views now instead of trying to sort everything from the main ticket list.

 


Another round of updates and no XML/Code in reply boxes - it seems like such a simple change - low hanging fruit. The community wants it based on numerous posts - here’s a link to my community post which shows other threads that are about the same thing. I’d love to see this incorporated ASAP

 


So the following issues are still outstanding…

1.) Tickets should not be closed by agents, they should be resolved. You can hide the close button when viewing a single ticket from the agents via business rules, but they still have the ability to change the status to closed in ticket list view. Also applies if you have any particular statuses you might not necessarily want agents to be able to use (we have a couple we use within workflows that are hidden via business rules).

 

We work around this with a Global Workflow:
Event: Status is changed from Any Status to Closed
Condition: Ticket Fields.Type is not Major Incident 
Action: Set Status to Resolved.

 

Agents can still Close a ticket, but the automation immediately changes it to Resolved. 

The Supervisor Rules then change it to Closed without any issues.

Major Incidents are excluded from this Workflow due to needing to be manually moved to Closed once the PIR is published.

 

 

 

We found if the ticket was already closed, and agents went into it, it would show as open. We found this to be a suitable resolution to hiding the closed status.

 

 

We had to jump through major hoops to make this work so an agent couldn’t re-open a closed ticket.  We had to create a check box Ticket Closed field, and then automate when a ticket went from Resolved to Closed after 3 business days, to check that box.   

Then created a global rule that if ticket closed was selected, to set status to only closed.  So when an agent opens the closed ticket, the status doesn’t show Open.  It only shows Closed.

Then another global rule that if ticket closed is checked, if they try to update the ticket, they get a validation error and can’t save any changes.

...and another to disable the ticket closed so it can’t be edited.

 


The “Reorder service categories on the support portal” is a good move. However, the biggest hinder to improve end-user experience is the “All Service Item” being the default in the Service Catalogue.

This flooded end-user default page with all service catalogues in the portal from A-Z. Make away with default “All Service Item” - let us determine what is the right landing page.

 


So the following issues are still outstanding…

2.) No resolution to prevent users bypassing SSO if their email domain is a specific domain such as your organisation email domain. We don’t want to allow users to bypass our SSO, as it means they can log in with email and password, which is easier to breach. Security risks don’t seem to be that critical in Freshservice…?

3.) Unable to download all attachments on a ticket if say >10 are attached. So long-winded.

 

  1. Even if you turn off Freshworks login ?
  2. If there are no Idea on that get more the 15 votes it will never happens. There are apps out there that can do it. 

What about silent installation after introduction “security” update to agent deployment - “Enhanced setup and security for Windows Agent and Probe”? Is there any command line parameter like for proxy information to provide this code automatically?
I’m deploying software in fully unattended way and it will be a nightmare for mass or remote deployments.

Did anyone consult it with clients, IT administrators, not only developers internally?

For new installations, users will need to complete an extra step. During setup, a user will be required to copy a registration token from the application and paste it into the installer when configuring the Discovery Agent or Probe.


oclews10 wrote:

So the following issues are still outstanding…

1.) Tickets should not be closed by agents, they should be resolved. You can hide the close button when viewing a single ticket from the agents via business rules, but they still have the ability to change the status to closed in ticket list view. Also applies if you have any particular statuses you might not necessarily want agents to be able to use (we have a couple we use within workflows that are hidden via business rules).

 

I was also very surprised by some of the default configuration options when I came to this organization that was already using Freshservice. I accomplished issue 1 with a business rule, but the key is to enforce it system-wide so they also can’t set a ticket to closed at the ticket list view.

 

 


What about silent installation after introduction “security” update to agent deployment - “Enhanced setup and security for Windows Agent and Probe”? Is there any command line parameter like for proxy information to provide this code automatically?
I’m deploying software in fully unattended way and it will be a nightmare for mass or remote deployments.

Did anyone consult it with clients, IT administrators, not only developers internally?

For new installations, users will need to complete an extra step. During setup, a user will be required to copy a registration token from the application and paste it into the installer when configuring the Discovery Agent or Probe.

 

I agree, there has to be a way to deploy the agent unattended, this is a very basic requirement and the documentation shows no command line parameter to suppress the token input. Please note that the installation files & scripts are usually stored in a public fileshare, so the agents token will be exposed to every client. This is more of a security nightmare than before!

 

To add to this, every client installation will be bound to an Agent’s API Key. This is already bad practice with the ORCH Server and the Freshservice Apps, but now all of our clients are also depending on that specific agent? What if this agent has an accident or leaves the company? We would have to redo all of our client installations with a new API key. 


What about silent installation after introduction “security” update to agent deployment - “Enhanced setup and security for Windows Agent and Probe”? Is there any command line parameter like for proxy information to provide this code automatically?
I’m deploying software in fully unattended way and it will be a nightmare for mass or remote deployments.

Did anyone consult it with clients, IT administrators, not only developers internally?

For new installations, users will need to complete an extra step. During setup, a user will be required to copy a registration token from the application and paste it into the installer when configuring the Discovery Agent or Probe.

 

I agree, there has to be a way to deploy the agent unattended, this is a very basic requirement and the documentation shows no command line parameter to suppress the token input. Please note that the installation files & scripts are usually stored in a public fileshare, so the agents token will be exposed to every client. This is more of a security nightmare than before!

 

To add to this, every client installation will be bound to an Agent’s API Key. This is already bad practice with the ORCH Server and the Freshservice Apps, but now all of our clients are also depending on that specific agent? What if this agent has an accident or leaves the company? We would have to redo all of our client installations with a new API key. 

 

No way the FS developers were this stupid… right?  Without an unattended deployment option, FS won’t be usable for us any longer.


The “Reorder service categories on the support portal” is a good move. However, the biggest hinder to improve end-user experience is the “All Service Item” being the default in the Service Catalogue.

This flooded end-user default page with all service catalogues in the portal from A-Z. Make away with default “All Service Item” - let us determine what is the right landing page.

 

We actually handled this by updating our main landing page to have a “button” for each category that we wanted users to go to.  It was time consuming but got rid of the “all” page as the default.  Our users have commented that the link the bigger “buttons” for categories rather than the list anyway.

Just an option that might be better than nothing for you.


Bundling for service requests with multiple sub-items needs addressing so that it is a better experience for customers and not a pain to administrate.  Currently, both the All Service Items and Last Category must be hidden with CSScript on the Service Desk Rebranding - Customize Support Portal in a janky way.  People will take the path of least resistance if they are not given options in a digestable way, and this causes re-work on tickets.

 

Maybe a filter could suffice as a solution if it is tied to a toggle option for service requests that places them in a special always hidden category reserved for 1-1 asset fulfillment.


Please push out an update where business rules are also applied to ticket view as currently you are able to see options that are available to specific workspaces. You are able to see all Status’s that are allocated to specific workspaces in ticket view as business rules are not applied.

 

Due to this issue our reports can tend to break occasionally as an agent will accidentally select the wrong option in their workspace as the option isn't available


Since service catalogue changes were to be a part of the audit log, is there any plans to include custom objects aswell?


The “Reorder service categories on the support portal” is a good move. However, the biggest hinder to improve end-user experience is the “All Service Item” being the default in the Service Catalogue.

This flooded end-user default page with all service catalogues in the portal from A-Z. Make away with default “All Service Item” - let us determine what is the right landing page.

 

Would it help your teams if you were able to add sub-categories to workspaces? If so, I have some code which can help make it a bit more of a plesant experience for your end users. (Below)

 


Any movement on project exports being not-bugged? Would love to be able to export all data out of projects (especially via API export), AND for the export to be a full export and not incremental. This has been bugged since release, and we’re relying on widget exports, which is less than ideal.


Are the FUP comments here being deleted?

I still can´t understand how we should be able to use Freshservice for historical-trending usage with this new policy with the limit of 2 years of data in a report!?!


The “Reorder service categories on the support portal” is a good move. However, the biggest hinder to improve end-user experience is the “All Service Item” being the default in the Service Catalogue.

This flooded end-user default page with all service catalogues in the portal from A-Z. Make away with default “All Service Item” - let us determine what is the right landing page.

 

Would it help your teams if you were able to add sub-categories to workspaces? If so, I have some code which can help make it a bit more of a plesant experience for your end users. (Below)

 

What is this beautiful magic?


Project Time Entries:  You state “This gives managers complete visibility of the hours logged by agents via the captured time and date details.” NO IT DOES NOT! There is no way to generate a report that includes time spent on Project and on Tickets, so this only gives partial visibility into time an agent is logging. You make a ridiculous assumption that Agents only work on Projects or only work on Tickets, and never both.  

Add to this the fact that Project tasks can’t be reordered and it’s a huge amount of functionality that is 100% useless to us. 

Oh, and again with the broken record. Where are the updates/improvements for MSPs that use Freshservice? 


@phodgkinson  I agree completely with you. There seems to be an underdevelopment in the project module and purchasing module and it is essentially useless for running projects. As a new customer I’m finding more and more that doesn’t make any sense in this product and is just really poor design. I can’t even link a purchase order to a project. I have to just manually capture what project the order is for and what wbs items the lines are for. These modules need some investment. 

Being able to reorganize project tasks should be a bare minimum function and it feels like a developer spec’ed up the system. when planning a project, I don’t put tasks in task order and I now need to buy another system to do this as freshservice is far below the standard for running IT projects. 

I’m also concerned around the number of people in these forums that are saying that freshservice is not listening to them. I’ll raise this with my account manager for discussion as I'm about to buy more licenses.


Im really struggling with the ms teams setup, especialy the collaboration part.

i can only link the chatbot to ONE team, but then all the agents are in that team, so everyone gets notifications i think.

And you need to make it a public channel, so you can not limit the views for that one team, so how do i make this work?