Meldungen/en: Unterschied zwischen den Versionen
Weitere Optionen
Faha (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
Isan (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
Zeile 1: | Zeile 1: | ||
Experts and professionals can see all reported incidents of the active management system under "Case Management → | Experts and professionals can see all reported incidents of the active management system under "Case Management → Tickets". | ||
By double-clicking on a | By double-clicking on a ticket, it can be edited. Here, you can either communicate with the creator of the ticket, change the status of the ticket, or set a period for the ticket. | ||
Tickets that have not yet been assigned to anyone are marked accordingly in the overview. | |||
[[Datei:CM Meldungen.png|left|thumb| | [[Datei:CM Meldungen.png|left|thumb|900px|Tickets]] | ||
<br clear=all> | <br clear=all> | ||
__TOC__ | __TOC__ | ||
== Edit | <span id="Meldung_bearbeiten"></span> | ||
== Edit ticket== | |||
=== Header data === | === Header data === | ||
---- | ---- | ||
In the header data of the | In the header data of the ticket, you can configure who has to process the ticket. | ||
[[Datei:CM Meldung Kopfdaten.png|left|thumb|900px|Header data]] | [[Datei:CM Meldung Kopfdaten.png|left|thumb|900px|Header data]] | ||
Zeile 22: | Zeile 23: | ||
<u>Title:</u> | <u>Title:</u> | ||
:Above the status, the title of the | :Above the status, the title of the ticket can be customized. Initially, the subject of the first message is set as the title. The title is displayed in the ticket overview list and in the period overview. | ||
<u>Reporter and date of submission:</u> | <u>Reporter and date of submission:</u> | ||
:Below the title is the information, by whom and when the | :Below the title is the information, by whom and when the ticket was submitted. | ||
<u>Periods:</u> | <u>Periods:</u> | ||
:Clicking on "x periods" under the title opens a window in which the periods assigned to this | :Clicking on "x periods" under the title opens a window in which the periods assigned to this ticket are listed. In the displayed list, new periods can be assigned to the ticket or existing periods can be implemented. At this level, periods should only be assigned if they apply to the entire ticket. Otherwise, the individual messages can also be assigned with periods. | ||
<u>Comment:</u> | <u>Comment:</u> | ||
:A comment for the | :A comment for the ticket can be given here. | ||
<u> | <div class="mw-translate-fuzzy"> | ||
<u>Advisor:</u> | |||
</div> | |||
:A | <div class="mw-translate-fuzzy"> | ||
:A ticket should always be processed by one person. This person can be assigned here. By clicking on the blue button next to it, the current user takes over the processing of the ticket. The advisor of the ticket is reminded of the processing of the ticket by the periods. | |||
</div> | |||
<u>Support team:</u> | <u>Support team:</u> | ||
:If no | <div class="mw-translate-fuzzy"> | ||
:If no advisor is entered for the ticket, then the reminders of the periods are sent to the support team. Under the <b>[[Special:MyLanguage/Fallmanagement-Einstellungen| settings]]</b> for the case management system, a default support team can be stored. This team will automatically be entered as the support team for all new incoming ticket. | |||
</div> | |||
<u>Dossier:</u> | <u>Dossier:</u> | ||
:Here the | :Here the ticket can be assigned to a dossier. You can also create a new dossier for the ticket or open the assigned dossier. | ||
:For more on dossiers, see [[Special:MyLanguage/Akten|"Case Management → Dossiers"]]. | :For more on dossiers, see [[Special:MyLanguage/Akten|"Case Management → Dossiers"]]. | ||
<u>Close | <u>Close ticket:</u> | ||
If the | If the ticket is finished or if there is another reason why the ticket should be closed, it can be done using this button. | ||
To close the | To close the ticket, one of the following reasons must be specified | ||
* Processing completed | * Processing completed | ||
::: The | ::: The ticket has been successfully processed. | ||
:* Missing information | :* Missing information | ||
::: The | ::: The ticket cannot be processed further because not enough information is available. | ||
:* Not plausible | :* Not plausible | ||
::: The | ::: The ticket is not plausible and therefore cannot be handled. | ||
:* Inactivity | :* Inactivity | ||
::: The notifier is no longer responding to messages and has left too little information. | ::: The notifier is no longer responding to messages and has left too little information. | ||
Zeile 65: | Zeile 72: | ||
---- | ---- | ||
Below the header data of the | Below the header data of the ticket is the message history for a ticket. | ||
"Compose answer" can be used to communicate with the creator of a | "Compose answer" can be used to communicate with the creator of a ticket. This makes it possible to get further information from the creator of the ticket if the initial information is not sufficient. | ||
<b>Caution:</b> | <b>Caution:</b> | ||
* Communication is only possible with creators who have created an anonymous mailbox when creating the | * Communication is only possible with creators who have created an anonymous mailbox when creating the ticket. If the creator has not created a mailbox, then this information is displayed with the first message. | ||
For each message, a dialog can be opened via "x periods", which can be used to assign periods to the message. | For each message, a dialog can be opened via "x periods", which can be used to assign periods to the message. | ||
[[Datei:CM Meldung Nachrichtenverlauf.png|left|thumb| | [[Datei:CM Meldung Nachrichtenverlauf.png|left|thumb|901px|Message history]] | ||
<br clear=all> | <br clear=all> | ||
Zeile 80: | Zeile 87: | ||
---- | ---- | ||
Periods are meant to help answer | Periods are meant to help answer tickets and messages within a certain period of time. | ||
For this purpose, the processor of the | <div class="mw-translate-fuzzy"> | ||
When the reminders are to be sent out, can be configured in the <b>[[Special:MyLanguage/Fallmanagement-Einstellungen#cm_fristdef| | For this purpose, the processor of the ticket or the support team, if no processor is entered, will be reminded via e-mail to comply with the period. | ||
When the reminders are to be sent out, can be configured in the <b>[[Special:MyLanguage/Fallmanagement-Einstellungen#cm_fristdef| period definition]]</b>. | |||
</div> | |||
Using the blue text "x periods" next to the messages or the | Using the blue text "x periods" next to the messages or the ticket, periods can be added to them or existing periods can be edited and implemented. | ||
A period is always assigned either to a message or directly to the | A period is always assigned either to a message or directly to the ticket. | ||
A new period can be assigned using the " | A new period can be assigned using the "Plus" button. | ||
By clicking the red button next to a period, a period can be deleted. | By clicking the red button next to a period, a period can be deleted. | ||
[[Datei:CM Meldung Fristen.png|left|thumb| | [[Datei:CM Meldung Fristen.png|left|thumb|901px|Periods for a ticket]] | ||
<br clear=all> | <br clear=all> | ||
<u>Message:</u> | <u>Message:</u> | ||
The subject of the message to which this period was assigned is displayed here. If it is not assigned to any message, then the period was assigned at | The subject of the message to which this period was assigned is displayed here. If it is not assigned to any message, then the period was assigned at ticket level. | ||
: Only visible at the | : Only visible at the period grid of the ticket (topmost). | ||
<u>Period definition:</u> | <u>Period definition:</u> | ||
Zeile 107: | Zeile 116: | ||
<u>Start:</u> | <u>Start:</u> | ||
: Here, you can enter from when the period should apply. Thus, periods that are to apply from receipt of the | : Here, you can enter from when the period should apply. Thus, periods that are to apply from receipt of the ticket can also be entered in retrospect. | ||
<u>Expiration:</u> | <u>Expiration:</u> | ||
Zeile 122: | Zeile 131: | ||
::: The period has not yet been implemented and the expiration is in the past. | ::: The period has not yet been implemented and the expiration is in the past. | ||
:*Obsolete | :*Obsolete | ||
::: The period has not yet been implemented but the | ::: The period has not yet been implemented but the ticket has been completed. | ||
<u>Implemented on:</u> | <u>Implemented on:</u> | ||
: The date on which the period was implemented. | : The date on which the period was implemented. |
Version vom 28. Februar 2023, 12:19 Uhr
Experts and professionals can see all reported incidents of the active management system under "Case Management → Tickets".
By double-clicking on a ticket, it can be edited. Here, you can either communicate with the creator of the ticket, change the status of the ticket, or set a period for the ticket.
Tickets that have not yet been assigned to anyone are marked accordingly in the overview.

Edit ticket
Header data
In the header data of the ticket, you can configure who has to process the ticket.

Title:
- Above the status, the title of the ticket can be customized. Initially, the subject of the first message is set as the title. The title is displayed in the ticket overview list and in the period overview.
Reporter and date of submission:
- Below the title is the information, by whom and when the ticket was submitted.
Periods:
- Clicking on "x periods" under the title opens a window in which the periods assigned to this ticket are listed. In the displayed list, new periods can be assigned to the ticket or existing periods can be implemented. At this level, periods should only be assigned if they apply to the entire ticket. Otherwise, the individual messages can also be assigned with periods.
Comment:
- A comment for the ticket can be given here.
Advisor:
- A ticket should always be processed by one person. This person can be assigned here. By clicking on the blue button next to it, the current user takes over the processing of the ticket. The advisor of the ticket is reminded of the processing of the ticket by the periods.
Support team:
- If no advisor is entered for the ticket, then the reminders of the periods are sent to the support team. Under the settings for the case management system, a default support team can be stored. This team will automatically be entered as the support team for all new incoming ticket.
Dossier:
- Here the ticket can be assigned to a dossier. You can also create a new dossier for the ticket or open the assigned dossier.
- For more on dossiers, see "Case Management → Dossiers".
Close ticket:
If the ticket is finished or if there is another reason why the ticket should be closed, it can be done using this button. To close the ticket, one of the following reasons must be specified
- Processing completed
- The ticket has been successfully processed.
- Missing information
- The ticket cannot be processed further because not enough information is available.
- Not plausible
- The ticket is not plausible and therefore cannot be handled.
- Inactivity
- The notifier is no longer responding to messages and has left too little information.
In addition to the conclusion, a reason for it should be given.
Message history
Below the header data of the ticket is the message history for a ticket.
"Compose answer" can be used to communicate with the creator of a ticket. This makes it possible to get further information from the creator of the ticket if the initial information is not sufficient.
Caution:
- Communication is only possible with creators who have created an anonymous mailbox when creating the ticket. If the creator has not created a mailbox, then this information is displayed with the first message.
For each message, a dialog can be opened via "x periods", which can be used to assign periods to the message.

Periods
Periods are meant to help answer tickets and messages within a certain period of time.
For this purpose, the processor of the ticket or the support team, if no processor is entered, will be reminded via e-mail to comply with the period. When the reminders are to be sent out, can be configured in the period definition.
Using the blue text "x periods" next to the messages or the ticket, periods can be added to them or existing periods can be edited and implemented.
A period is always assigned either to a message or directly to the ticket.
A new period can be assigned using the "Plus" button.
By clicking the red button next to a period, a period can be deleted.

Message: The subject of the message to which this period was assigned is displayed here. If it is not assigned to any message, then the period was assigned at ticket level.
- Only visible at the period grid of the ticket (topmost).
Period definition:
- The underlying period definition must be stored here. Period definitions specify the length of time of the period. Period definitions can also be provided with reminders for the processor to meet the period. Period definitions can be created and configured by experts under "Case management → Settings".
Name:
- Each period can have its own name. Through this, periods created with the same period definition can be distinguished from each other.
Start:
- Here, you can enter from when the period should apply. Thus, periods that are to apply from receipt of the ticket can also be entered in retrospect.
Expiration:
- Results from start date and time span of the selected period definition.
Implementation:
- A period can be implemented using this dropdown.
Adherence:
- Indicates the status of a period. The following statuses are available:
- Implementation pending
- Implemented
- Period exceeded
- The period has not yet been implemented and the expiration is in the past.
- Obsolete
- The period has not yet been implemented but the ticket has been completed.
Implemented on:
- The date on which the period was implemented.