Advanced case management is used to record, update, track, follow up on and close issues raised by Workers and/or Customers.
Cases can be used within multiple modules of D365 Finance and Operations such as Customer service, Purchasing and receiving, Human resources and payroll, Auditing and Collections. Via GRC it also extends to Medicals (occupational health) as well as Treasury (creation of loans & investments).
These are required and will be covered below:
Axnosis has increased case management functionality as part of its Governance, Risk and Compliance suite. As an extension to quality management, Advanced case management has been added.
Go to: GRC > Setup > Governance, risk and compliance parameters
A Document pack is used to group multiple documents together. These documents normally support tender and contracting activities. Thus when a set of templates is needed for a tender, they can be referenced on the RFQ by using a Document pack. Additionally, a list of recipients can also be added to the pack. This is useful when needing to send a set of documents to a bid committee.
Go to: Organization administration > Setup > Organization email templates
Go to: GRC > Setup > Governance, risk and compliance parameters
Teams are a collection of workers (and system users) who are getting together for a temporary assignment, for example a bid adjudication committee.
Enter a code or name for the priority of a lead record. For example, you can define High, Medium and Lowpriorities for a case, or Critical, Emergency, High impact, Medium Impact or Low impact.
Go to: GRC > Governance > Setup for governance > Priority
When designing a case hierarchy for your business, the first step is determining how each business process will fall into Case Categories. Think of Case categories as a tiered structure in which your ad hoc business processes can be centralized. For example, categories can be broken down at the highest level into 3 categories: Assets, Audit and Contracts. This is a simple example, but cases can be used across a variety of functional business departments. (for instance General, Service, Collections)
Go to: GRC > Governance > Setup for governance > Case categories
The Category type has to be Service
Cases are grouped according to the Category type, and can be found under specific menu items. E.g. All audit cases
Grouping of Symptoms, Fault area, Fault types, Causes and remedies set up under the Asset management module.
Go to: Asset management > Setup > Fault > Fault symptoms
Go to: Asset management>Setup>Fault>Fault areas
Go to: Asset management > Setup > Fault > Fault types
Go to: Asset management > Setup > Fault > Fault causes
Go to: Asset management > Setup > Fault > Fault remedies
Go to: Asset management > Setup > Fault > Fault designer
Fault symptoms, areas and types are added to the Fault designer form
Go to: Asset management > Setup > Asset types > Asset types
Go to: Asset management > Assets > All assets
In order to create the right urgency and provide proper expectations of when a task (or stage) should be completed, service level agreements are used. They are used on case categories and can be created as a default or manually entered on an individual case basis.
Go to: Service management > Setup > Service agreements > Service level agreements
This is the preliminary setup. The next step is to set up a case process on how you want a process to be handled
Processes help guarantee consistency in cases, and also help employees resolve cases faster and more efficiently. You can set up a process for each case category that cases are assigned to. Although planning a separate process for each case type takes time, case resolution will go much more smoothly if the processes are planned out.
Go to: Organization administration > Setup > Cases > Case processes
Case processes: There should be a one-to-one relationship between a Case category and a Case process. The same Case process can be used across multiple categories; it may make sense to do so if you would like to segregate similar cases by department for reporting purposes.
Case levels: The various stages in a case process are defined as levels. Within these levels, multiple default activities can be assigned. Depending on the importance and flow of the case, these activities can be set as required, which forces the user to complete that activity before moving on in the case. Notes can also be added about what must be done.
- Click on the Process tab and select details
Case activities: Within a case level, default activities can be assigned that are commonly completed during a case. The choices for activities include appointments, tasks, action items, and events. Once again, these activities can be assigned to specific members of an organization, which can then be placed into a work queue. Once the case is opened, activities can always be added on the fly to any case level.
After case setups are completed, employees with the appropriate permissions can create cases as issues are raised.
Go to: Common > Cases > All Cases
On the New case dialog, under the General Index tab, enter the following information:
Open the Other Index tab and enter the following information:
The Case log Index tab:
To access all cases
Go to: Common > Cases > All cases
- The dropdown values are limited based on the case category setup. This reduces random data being entered
- Correct setup will ensure context correct data
Note, the ability to record Geo tags is useful for PowerBI reporting
By using the Create work order button in the Action pane, users can create a Maintenance work order from the case
Users can capture the following per case under the Treasury Fast tab:
For Treasury to work, the G2T model is required and from a setup point of view, users must work with cases of Category type = “Treasury”
Service Level Agreement - If the case is upgraded to a higher priority we can recall the SLA and assign a shorter time frame. Each time we recall an SLA, D365 prompts the user for a reason code, and all SLA related changes are tracked in a transaction log. Similarly, if the case is taking longer than expected for reasons outside our control (pending customer response), we can stop the SLA so that the case does not appear as overdue. A reason code is also required for any stoppages and can be tracked downstream to better evaluate your customer service professionals
Go to: Common > Advanced case manager