Feature Suggestion

Currently, the Locations, Departments, Extension Properties API are not public. Need these APIs to be available in swagger with the product support as the Locations, Departments and Extension Properties API Data output can be utilised in the subsequent APIs of Contract, Users etc. To start with GET and maybe POST can be added later

As a user, I would like to be able to figure out if and when the changes were made on Custom Card. What are the changes done? Who made the changes? When was it done? Last 2 are mostly available

In case of recurring monthly/weekly tasks, we need the previous email thread to keep a record of client’s feedback and iterations reflected in the current output. Generated automatically, it starts as a new work item without any previous communication every time. This is not feasible because the client can come at any time to ask a question and we cannot go back to a particular email and emphasize our points.

As business user, i want tickets to be triggered on daily basis based on definition like monthly/ weekly/ daily time. Can we get a feature similar to case triggering for tickets.

Current design requires information required for decision to have been made available in previous step(s) this potentially leads many artifical steps and therefore nothing modelling the actual steps (as required by client).

When trigger external api flavoured action is triggered, there is no parameter in the received JSON body to identify if the action is from Test mode or Live mode. Due to this clients are not able to use the test mode feature.

As an end user, if I am sending email to create workitem on Enate, I don’t want the acknowledgment to be received by the CC’ed members. As a configurator, if I want an option to select whether the acknowledgment should go to only To address or CC both.

There are business scenarios where the work item due date is next year of the work item creation date for example, a case has a due date of 31st January but has to be triggered on enate on 1st of November previous year. Currently we have no feature to tackle this kind of situations directly via the due date methods present and have to use different workarounds.

In the Schedule section within the builder, when manually adding schedules, the dates should follow consecutively. For example, if the first activity is selected as August 5th while configuring the schedule in the current month (July), selecting the next activity within the same row should automatically display the August calendar instead of defaulting back to the July calendar. This enhancement will reduce the number of clicks required and improve user efficiency.

As a user on Builder, when deleting objects I would like to restore back what was immediately deleted and to be notified when it is successfully deleted. Similar feature for the undo send email functionality released in 2021.1