SLA not working on collection cases
When creating a case category of the type Collections, a default Service Level agreement is selected. When a user creates a case of this category, the default SLA is not filled. The user is also not able to fill in the SLA on this case.
Odata element needed for the creation of cases and associations
Hi, We are working with external sources in which customer do enter remarks on invoices, products and services. One source is a portal the other source is scan software. For any of the remarks we do need to react within a number of days by law. Therefor all these complaints \ questions \ remar...
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Today there is a DMF entity that is explicitly not enabled for odata, as it contains many fields and isn’t tailored for a specific role. You can absolutely extend or copy that entity if you believe you can use as-is or take our entity as a basis for a role-tailored entity.
Sincerely,
Ryan Sandness
Public data entities to create cases and activities in FinOps from third party app
To be able to create cases and activities in FinOps from third party app it would be useful to have the following data entities to be public and available as OData API for the creation of Cases and Activities in FinOps: * CaseDetailBaseEntity * CaseAssociationEntity * CaseDependencyEntity * smmA...
Workflow for Tasks vs Approvals
Split out the workflow functionality for approval vs tasks. Currently if the global workflow setting of "disallow approval by submitter" is set to "yes", a task within a workflow does not get assigned back to the submitter. The functionality to have that global setting turned to yes, and allo...
Thank you for your suggestion. To help us in our review process, we’re requesting votes from the community to help us understand the importance of this functionality. This posting is provided “as is” with no warranties, and confers no rights.
Create a new entity for a case's log
Although D365 has an out of the box entity for migrating cases (Case Detail), no entitiy is available to also migrate the related logs linked to the case. As a result, an essential part of the case's history can 't be migrated and is lost. Therefor, a new entity (caseLogEntity) should be creat...
Issue 370589 - Parent case is not correctly transferred into New case form when filter is applied to All cases list page
Thank you for reporting this product issue. We agree that this is an issue for you and understand how this can be impacting your business. Unfortunately, the issue doesn’t meet the standards we require to be adjusted at this time. Our previous fix implemented had severe side-effects so had ...
Data entity for Hierarchy
There is no data entity for Case process or in general the Hierarchies. If there is no specific reason why there is no data entity, could a new entity be created for Hierarchy table as this is useful in data migrations and at time of production configurations.
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Ryan Sandness, PM
Assigning inquiry reason codes and security administration to selected or range of records
Future assigning inquiry reason codes and security administration to selected or range of records at inquiry and/or potential reports, may potentially efficientize record display or disclosure security or potential encryptions.
Case management integration with Amelia
Wish there is a future option to integrate with Amelia https://www.ipsoft.com/amelia/ for purpose to easy close support tickets and potentially ledger post certain cases to internal consulting projects or general ledger (e.g. accounting for potential feedback, IT support tickets, other.) Not fea...
Thank you for your suggestion. After careful consideration, we’ve decided not to proceed with this functionality at this time.This posting is provided “as is” with no warranties, and confers no rights.
Case management aging in periods of days and hours by status
Future having the option to automatically track aging by number days and by hours by case status including accumualed aging from record creation might be potentially valuable for purpose of efficiency on inquiries, reports and dashboards.
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Ryan Sandness
Administrator
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it. This was an original design decision to treat collection cases differently and we have significant implications involved in changing the data model and functionality that currently treats collection cases differently.
Sincerely,
Ryan Sandness