• The project will disappear from the list of current projects and will automatically be archived.
• The project status and end date will automatically be updated in the Project form.
• The task schedule can no longer be modified.
• Tasks will disappear from the time sheets of project participants. Only project managers can continue entering time sheets by selecting Time Sheet > My Projects in the menu.

• All equipment whose status is To be Transferred will be displayed.
• The recipient department can accept or refuse the transfer for each item of equipment.
• Accepted equipment:
  • Will appear in the equipment inventory of the new department.
  • Will be associated with a storage location of this department.
  • Its status will automatically change to In Stock.
  • It can be pre-assigned to an employee in this department.

• By default, the number of installations authorized for the new license is equal to the total number of installations for the licenses of earlier versions.
• Earlier licenses are archived. They are displayed in the Related Licenses tab but do not appear in the Gap Analysis by Version report.

• It can also run as a scheduled task.

• The trigger condition will be tested.

• The meta-object search results will automatically appear for predictive entry and the dedicated search results page displayed via Search in Grid mode. See the description.

• When you enable the TSA, all active mailboxes will be scanned by the agent (Enable Active Mailbox Scan box checked).
• When you disable the TSA, all the mailboxes associated will not be consulted any longer.

• When you run the wizard in List mode, you can associate several objects with the contract if their fixed monthly costs are identical. In this case:
  • Enter the unit price of the contract.
  • The total cost of the contract will automatically be calculated: Number of objects linked to the contract * Unit price.
• If the objects have different unit prices, you should run the wizard as many times as required.
• The cost of the contract will be updated in the contract inventory in the Financial Data tab.

• Only the manager of a project can perform this operation for non-completed projects.
• Projects already linked to the current object will automatically be displayed. Click to delete one of the links.
• In the form of the current object:
  • The Related Projects tab will be updated.
• In the form of the project:
  • Depending on the object from which the wizard is run, the Incident/Service Request/Investment Request/Change Request/Problem tab will be updated.

• Only the manager of a project can perform this operation for non-completed projects.
• In the form of the current asset:
  • The Related Projects tab will be updated.
• In the form of the project:
  • The dedicated tab to the type of assets, i.e. equipment, licenses, contracts, CIs, will be updated.

• Requests already linked to the current object will automatically be displayed. Click to delete one of the links.
• In the form of the current problem:
  • The Link to a Change Request action will automatically be generated.
  • The Related Changes tab will be updated.
• In the form of the change request:
  • The Related Problems tab will be updated.

• Requests already linked to the current object will automatically be displayed. Click to delete one of the links.
• In the form of the current service request:
  • The Link to a Change Request action will automatically be generated.
  • The Related Changes tab will be updated.
• In the form of the change request:
  • The Related Services tab will be updated.

• Drafts and input errors are not visible in the list of incidents.
• Incidents already linked to the current object will automatically be displayed. Click to delete one of the links.
• In the form of the current object:
  • The Related Incidents tab will be updated.
  • If it is a problem, the Link to an Incident action will automatically be generated. Click + to display the list of incidents.
• In the form of the incident:
  • Depending on the object from which the wizard is run, the Related Problems/Related Known Errors tab will be updated. The Known Errors tab can be seen in the actions of the incident.

• The user will become a project resource and can be assigned tasks.
• The Projects tab and the corresponding Project form and Gantt chart are automatically updated.

• Requests already linked to the current object will automatically be displayed. Click to delete one of the links.
• In the form of the current object:
  • The Related Services tab will be updated.
  • If it is a change request, the Link to a Service Request action will automatically be generated.
• In the form of the service request:
  • Depending on the object from which the wizard is run, the Related Problems/Related Known Errors/Related Changes tab will be updated. The Known Errors tab can be seen in the actions of the request.

• In the form of the incident:
  • The Linked to an Event action will automatically be generated.
  • The Related Events tab will be updated. In this tab, you can delete an existing link using .
• In the form of the event:
  • The Linked to an Incident action will automatically be generated.
  • The Related Incidents tab will be updated. In this tab, you can delete an existing link using .

• A parent incident cannot be linked to another parent incident. Only one parent-child level is authorized.
• If the child incident is already associated with a parent incident, a message will appear. If you select a new parent incident:
  • The link with the previous parent incident will be canceled.
  • The Related Incidents tab will automatically be updated in the forms of the previous and new incidents.

• In the form of the child incident:
  • The Related to a Parent Incident action will automatically be generated.
  • The Related Incidents tab will be updated.
• In the form of the parent incident:
  • The Related Incidents tab will be updated.
  • The status of the child incident will be Related Incident.

List of fields :

• Parent Incident: The list will only display open incidents.
• Filter on Incidents assigned as Parent: By default, only parent incidents will appear. To display all incidents, untick the box.

• If the continuity plan is already associated with the current object, a message will appear. If you select a new continuity plan:
  • The link with the previous plan will be canceled.
  • Depending on the object from which the wizard is run, the Incidents/Services/Changes tab will automatically be updated in the forms of the previous and new plans.

• In the form of the current object:
  • The Assign a Continuity Plan action will automatically be generated.
• In the form of the continuity plan:
  • Depending on the object from which the wizard is run, the Incidents/Services/Changes tab will be updated.

• Problems already linked to the current object will automatically be displayed. Click to delete one of the links.
• In the form of the current object:
  • The Link to a Problem action will automatically be generated.
  • The Related Problems tab will be updated.
• In the form of the problem:
  • Depending on the object from which the wizard is run, the Related Incidents/Related Services/Related Changes tab will be updated.

• In the form of the request:
  • The Related Incidents tab will be updated.
  • If you replace a previously linked request, the tab will also be updated in the form of the previous request.

• In the form of the current incident:
  • If you replace a previously linked request, the link with the previous request will automatically be canceled.
  • The Attached to a Change Request action will automatically be generated.
  • The Related Changes tab will be updated.
  • The status of the current incident will be Related Incident and will be managed by the standard workflow of the change request. It will automatically end when the request is closed.

• If requests are already linked to the current object, a message will be displayed.

• If this is the first link to a service request, the current object will automatically be closed.
  • It can be requalified when the category is modified.
  • All ongoing actions will be closed.

• In the form of the current object:
  • The Attached to a Service Request action will automatically be generated.
  • The Related Services tab will be updated.
  • If this is the first link to a service request, the status of the object will be associated with the Completed meta-status, indicating that the processing was closed early.
    • The Anticipated Closing action will automatically be generated.
    • The object will disappear from the list of open objects.
  • If ongoing actions are closed:
    • In the History of Actions, the text, Early termination will appear next to each of them.
    • In the Action form, the value of the Action to Complete field will be Anticipated Closing.

• In the form of the service request:
  • Depending on the object from which the wizard is run, the Related Incidents/Related Problems tab will be updated.

• In the form of the request linked to the action:
  • The status will be Attached to a Release.
  • The Assign a Continuity Plan action followed by the code of the release will automatically be generated.
  • The Release tab will be updated.

• In the form of the release project:
  • The Change - Open Requests and Change - All Requests tabs will be updated.

• One row is displayed for each asset in the selected service request, change request or investment request.
  • For each item, open orders with the same model, delivery location and analytical cost allocation will automatically be displayed.
  • The Take from available box is automatically updated and cannot be modified.
    • The box is selected if the open order already has one row for replenishing the same item and delivery location. The row will be related to the request.
    • The box is not selected if the open order already has one row for replenishing the same item and delivery location but is related to another request. A new row will be created in the open order.
• The open order will be refreshed. New rows will be added for items that do not exist in the order and the ordered quantity for existing items will be updated.

• In the form of the current object:
  • The status of the current object will be associated with the Completed meta-status, indicating an early closing or cancellation of the processing.
    • The Cancel / Close action will automatically be generated.
    • The object will disappear from the list of open objects.
  • All ongoing actions will be closed:
    • In the History of Actions, the text, Early termination will appear next to each of them.
    • In the Action form, the value of the Action to Complete field will be Anticipated Closing.

• You can create templates from forms (by checking the Is a Template box). Only objects whose meta-status is Processing in Progress can be selected.
• You can specify the fields whose content must not be duplicated when using a template via the {SM} Exclude SD_REQUEST fields when duplicating incidents other parameter.
• Date and System fields are never duplicated.
• You can modify the information preloaded from the template.

• The parent object will keep its status.
• If the child object is requalified:
  • The new workflow will start.
  • For the group or Support person involved in the initial step of the workflow:
    • The My Actions and counters are automatically updated in the Quick Dashboard.
    • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• The child incident will no longer be managed by the workflow of the parent incident.
  • Its own workflow will start.
  • Its status will be In Progress.
  • The current action will appear in the list of actions to complete.

• In the form of the current object:
  • The Cancellation of the Parent Relationship action will automatically be generated.
  • The Requalification action will automatically be generated if the category was changed.
  • The Related Incidents/Related Services tab will be updated.

• In the form of the parent object:
  • The Related Incidents/Related Services tab will be updated.

• Only order items with a quantity remaining to be delivered will appear.
• In the Order form:
  • The order closing date is automatically specified.
  • In the Detailed tab, the Cancelled / Supplier Stock Shortage box is selected for all canceled order items.
• If all order items pending delivery are canceled, the order will disappear from the Not Closed filter and will no longer appear in the list of pending deliveries.

• Equipment CIs are archived when they are discarded. Service CIs are archived when they are no longer available in the Service Catalog.
• The CI will no longer appear in the CMDB and cannot be associated with any incident/request.
• Items of equipment that depend on the equipment CI will automatically be archived.

• Only authorized groups where the action group belongs will be available for the transfer. Note: The domain of the logged-in user and the role defined in the workflow that manages the ticket will not be taken into account. See Group Directory > Manage authorized/unauthorized groups.

• The list of Support persons only includes members of the selected group.
• The Assignment action followed by the name of the Support person will automatically be generated.
• For the group or Support person involved in the current step of the workflow:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• The Service SLA changed action will automatically be generated.
• If the modification of the date generates a delay, the Late Actions counter will automatically be updated in the Quick Dashboard of the group or Support person involved in the current step of the workflow.

• Only passwords for users who are not managed in an LDAP directory or SSO tool can be changed.
• Passwords must comply with constraints in the Employee password policy. By default, there must be six characters minimum and any character is accepted.
• Users can click to change their own password in the user information zone provided that authentication is not performed via an LDAP directory or SSO tool.

• The Service SLA changed action will automatically be generated.
• The target resolution date will automatically be recalculated.
• If the modification of the date generates a delay, the Late Actions counter will automatically be updated in the Quick Dashboard of the group or Support person involved in the current step of the workflow.

• The current object will automatically be closed.
  • The workflow will be interrupted.
  • The Anticipated Closing action will automatically be generated.
  • The status of the current object will be associated with the Completed meta-status, indicating an early closing of the processing.
  • The object will disappear from the list of open objects.

• If current actions are completed:
  • In the History of Actions, the text, Anticipated Closing will appear next to each of them.
  • In the Action form, the value of the Action to Complete field will be Anticipated Closing.

• Linked objects will automatically be closed and their status will be identical to the parent object.

• When the main action is solved, a message will be displayed if there are related actions.
• When a related action is solved, a dialog box will ask what should be done with the related actions.

• The child request will be managed by its own workflow.
• For the group or Support person involved in the initial step of the workflow:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• In the form of the child request:
  • Depending on the object from which the wizard is run, the Related Services/Related Changes tab will be updated.
  • The request will have the initial status of the workflow associated with the category.
• In the form of the parent request:
  • Depending on the object from which the wizard is run, the Related Services/Related Changes tab will be updated.
  • The status of the request will not be modified.

• The Next Scheduled Intervention date will automatically be calculated using the Maintenance Duration frequency inherited from the model.
• If only one item of equipment is selected, you can check and update its attributes via Note Attributes.
• The intervention will not appear in the list of To Do actions in the Service Desk module.

• In the form of the new news article, the Related Major Incident field will be updated.
• The news article will automatically be displayed in the quick call for any new incident with the same category as the major incident. If it is selected:
  • The current incident will automatically be linked to the major incident and will be managed by the workflow of the major incident.
  • In the form of the new incident, the Related Incidents will automatically be updated.

• When the news article is closed, the link with the major incident will automatically be deleted and all linked incidents will be closed.

List of fields :

• Public News: Used to indicate if the new news article will only be visible in the Service Operation and Service Transition menus for Back Office users (box is not checked) or if it will also be visible to users in the Self Service portal (box is checked).

• Password definition rules only apply to users who are not managed in an LDAP directory or SSO tool.

• Define the employee's new role and equipment after a transfer to a new team within the company.
• Assign new equipment to the employee.

• You can specify what will happen to the equipment previously assigned by modifying its status, location or department.
• The Employee form will be archived.

• The trigger condition will no longer be tested.

• The meta-object will disappear from the list of active meta-objects.

• In the form of the current request:
  • The status before the release was linked will be retrieved.
  • The Detach from a Release Project action will automatically be generated.
  • The ongoing action before the release was linked will be retrieved.
  • The Release tab will be updated.

• In the form of the release project:
  • The Change tab will be updated.

• Notes :
  • When you duplicate a resource, it will automatically be associated with the same service and with the same connection as the template.
  • When you duplicate a questionnaire or a section of a questionnaire, all questions of the template will automatically be copied.
  • When you duplicate a profile, the menu of the profile will automatically be copied.

• Specify the leasing contract's global rental to be spread over the number of assets listed in the contract using the Global Amount for Rentals field.
• The share of the rental is automatically calculated as a percentage of the global purchase price. Global Amount for Rentals / Total Purchase Price

• In the form of the current object:
  • The Create Unavailability action will automatically be generated for each unavailable CI.

• In the form of the unavailable CI:
  • The Unavailability tab will be updated with the start of unavailability date.

• If the order has not yet been sent by the supplier, a non-blocking message will appear.
• Reception is performed at a single delivery location (storage location), except for orders linked to investment requests where reception at different locations is authorized.
• Only order items with a remaining quantity to be delivered will appear.
• Contracts can be associated with reception.
• You can inform the IT Asset Manager of the delivery reception by sending an email.
• New Equipment forms will automatically be created using references specified manually or automatically using bar code generation. The status will be In Stock.
• In the order, the quantity for each item received will be refreshed in the Detailed tab.
• Analytical cost allocations will be updated.
• If reception is:
  • Partial: The order will remain displayed in the list of pending deliveries and the remaining quantity to be delivered will be refreshed.
  • Total or canceled due to stock shortages: The order will disappear from the list of pending deliveries. Note: If you select the Balanced for Stock Shortage Supplier box for all order items, the order will automatically be canceled.

• Equipment forms will automatically be created with the In Stock status.

• The status of the equipment will be In Repair.

• If the recipient is different from the requestor, then the recipient will receive a copy of the email.
• The Notification to Requesting Person action will automatically be generated.

• An additional action that was not in the initial workflow will automatically be generated.

List of fields :

• Only authorized groups where the logged-in user belongs are available. See Group Directory > Manage authorized/unauthorized groups.
• The groups available are based on the domain of the user and the role defined in the workflow. In Other Parameters, the {SM} Filter list of groups by category when transferring actions parameter must be enabled.

• A file containing all linked CIs can be generated.
• You can run a capacity simulation.
• Associate the Selected CIs: Used to link the CIs in the impact analysis to the current object. The CI tab will be updated.

• Click Download. The name of the file will be based on the profile name followed by the file generation date and time.

• Note: Only for objects linked to the same supplier.

• The quantity invoiced is equal to the quantity received.
• Order forms will automatically be refreshed.
• Orders that have been completely invoiced will disappear from the list of pending invoices.
• Analytical cost allocations will be updated.

• All lower-level objects will automatically be archived.

• In the form of each unavailable CI:
  • The Unavailability tab will be updated with the end of unavailability date.

• All lower-level objects will automatically be archived.

• The project will disappear from the list of current projects and will automatically be archived.
• The project status and end date will automatically be updated in the Project form.
• The task schedule can no longer be modified.
• Tasks will disappear from the time sheets of project participants. Only project managers can continue entering time sheets by selecting Time Sheet > My Projects in the menu.

• You can display all or a selection of the software and attributes that differ for the two references. They can be added to the equipment that remains after merging.
• The equipment that remains after merging will keep its current status.
• Abandoned equipment will be removed from the IT infrastructure and its status will change to Archived.

• Note: The selected types must be linked to the same asset type.

• Abandoned types will be removed.
• Associated elements will be linked to the type that remains after merging.

• Abandoned manufacturers will be removed.

• Usage rights will not be kept when software models are merged.

• Payment includes rental for equipment and licenses included in the contract.

• You can specify an amount to be charged back for the use of the service.
• In the CI form, the Is a Service box will automatically be checked.

• The form will automatically open in the catalog and will no longer appear in the Service Pipeline.

• Authorized groups are integrated using three wizards: Transfer a Quick Call, Transfer an Action, Assign an Action.

  See Group Directory > Manage authorized/unauthorized groups

  .

• You can specify the groups managed by the employee.
• Field Default: If the employee belongs to several groups, this is used to specify the default group which will be used by certain wizards.
  example Use with the wizards Closing an incident, Reopen an incident

• Notes:
  • If a question is being used in another question via a constraint or condition, it cannot be deleted.
  • Its description, type and rank cannot be modified.

• If the Keep current Users of equipment related to selected equipment option is selected, related equipment will automatically be moved with the current equipment and will automatically inherit the new user and user location.
• If the Pre-Assignment wizard was previously run on equipment, the new user will be specified by default.
• By default, the location, department and cost center are those for the new user.
• If the status is not specified, the equipment will inherit the default status of the location.
• The equipment will store the history of previous assignments in the History of Changes tab, i.e. changes in location and user.

• You can configure the wizard using the Administration > Parameters > Scripts menu.

• Three options are available:
  • Update All: Update fields by replacing existing values with new ones.
  • Update if empty: Update fields only if they are empty.
  • Empty: Empty the fields.

• Contract periods are automatically updated in the Scheduled Periods tab in the Contract form.

• A new news article will be created:
  • It will be available for any object with the same category.
  • The Related Known Errors tab will be updated.
• In the form of the knowledge article:
  • The News Articles tab will be updated.

• The new status is selected from those specified in the Next Status tab in the Known Error Status reference table.
• The change of status of the current known error will not have an impact on the status of linked objects.
• If the status of the known error becomes Archived, the associated news articles will remain visible for objects with the same category.

• Users can assign their own profile and any lower-level profile belonging to their master profile.

• The Service CIs referenced in the Service Pipeline tab will automatically be released. They will disappear from this tab and will automatically appear in the Service Catalog tab.
• A Release Completed action will automatically be created for each change request related to the release project.
• The status and the version will automatically be updated in the form of each selected CI.

• The email is sent to users when they click Forgot your Password? in the Service Manager login window.

• The Urgency Change action will automatically be generated.
• A notification email will be sent to the Support person.

• For existing order items:
  • The reference and model cannot be modified.
  • The delivery location can be modified only if no request is linked to the order item.
• In the Order form:
  • The total order amount will be calculated again to take updated discount prices into consideration.
  • The Detailed Order Records tab will be refreshed.
  • Analytical cost allocations will be updated.

• Note: Only one order item can be selected.

• Depending on the current object, the Equipment/Software, Equipment/Software/Contracts, Equipment/Software/Consumable or Consumables tab will be updated.
  • A new row will be added for each new element.
  • If the quantity is zero, the row will be deleted.
• The estimated expense is automatically refreshed and analytical accounts are updated.

• You can enter a priority level manually for each business rule or you can define its order in the sequence based on a reference rule.

• The equipment CI will automatically become standard equipment again.

• The list of groups will depend on the selected roles.
• An email can be sent to notify those involved.

• The Notification for Action action will automatically be generated.
• For the selected group or Support person:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• The list of groups will depend on the selected roles.
• The Notification for Information action will automatically be generated.
• No To Do action will be generated for the Support person involved.

• In the User form, the Main Equipment tab will be updated.

• In the CI form, the Continuity Plan tab will be updated.

• The workflow of the new problem will automatically start.
• For the group or Support person involved in the initial step of the workflow:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• In the form of the current incident:
  • The status will be In Progress.
  • The Related Problems tab will be updated.
• In the form of the new problem:
  • The Related Incidents tab will be updated.

• In the form of the request linked to the action:
  • The Release tab will be updated.

• In the form of the release project:
  • The Change - Open Requests and Change - All Requests tabs will be updated.

• You are not required to select a CI.
• The new status will be available when you run the CI Status: Update wizard.

• The incident will inherit the default category indicated in the CI form.

• The workflow of the new incident will automatically start.
• For the group or Support person involved in the initial step of the workflow:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• In the form of the new incident:
  • The status will be In Progress.
  • The Related Events tab will be updated.
• In the form of the current event:
  • The Related Incidents tab will be updated.

• You can associate the attribute with a type.
• You should associate the new attribute in the Attributes tab in the form of the current object.

• The order is for a single supplier.
• Processed requests will disappear from the list.
• The new order will appear in the list of open orders.
• Analytical cost allocations will be updated.

• In the form of the new knowledge article:
  • The status will be Knowledge Base.
  • The Creation of Knowledge action, visible in the Actions tab, will automatically be generated.

List of fields :

• Creation Date: This is the current date.
• Status: Identical to Knowledge Base.
• Public: Used to indicate if the new knowledge article will only be visible in the Service Operation and Service Transition menus for Back Office users (box is not checked) or if it will also be visible to users in the Self Service portal (box is checked).
• Title: Title given to the knowledge article to be used as keywords for the full text search.
• Check Duplicates link: Used to check if there is an existing knowledge article on the same category. The full text search window will automatically open using keywords from the Title.
• Contents: Description of the knowledge article.
• Next Review: Frequency based on which the knowledge article should be reviewed.
• Version: Version number of the knowledge article, generally updated at each major review.
• Implementation Time: Time required to apply the solution described in the knowledge article.

• Publish This Element as News Article: Used to create a new news article automatically associated with the new knowledge article.
  • The News Articles tab will be updated.
  • List of fields:
    • Knowledge Number: Automatically incremented number.
    • Publication Date/End of News Article Publication: Publication period during which the news article is visible to users, provided it is public.
    • Restriction on Location: Application perimeter of the news article restricting its visibility to users at the selected location including those belonging to lower levels.
    • Restriction on Department: Application perimeter of the news article restricting its visibility to users in the selected department including those belonging to lower levels.
    • Language Publication: Select the languages in which the news article will be published. It will automatically be displayed in the user's connection language.
    • Publish Another News Article for This Element: Used to create a new news article automatically associated with the new known error.

• For configuration items, the request will inherit the default category indicated in the CI form.
• The workflow of the new request will automatically start.
• For the group or Support person involved in the initial step of the workflow:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• In the form of the new request:
  • Depending on the object from which the wizard is run, the Related Incidents/Related Services/Related Problems tab will be updated.

• In the form of the current object:
  • If it is an incident:
    • The change request will become the parent of the incident and the incident status will be Related Incident.
    • The Attached to a Change Request action will automatically be generated.
    • If ongoing actions are closed:
      • In the History of Actions, the text, Early termination will appear next to each of them.
      • In the Action form, the value of the Action to Complete field will be Anticipated Closing.
    • The Related Changes tab will be updated.
    • When the change request is closed, the closing workflow defined for the category of the request will then run for the incident.
  • If it is a service request or a problem:
    • The status of the object will not be modified.
    • The Related Changes tab will be updated.

• For configuration items, the request will inherit the default category indicated in the CI form.
• The workflow of the new request will automatically start.
• For the group or Support person involved in the initial step of the workflow:
  • The My Actions and counters are automatically updated in the Quick Dashboard.
  • The action is visible in the Service Operation > Actions > My Actions menu of the Support person and in the Service Operation > Actions > Actions for My Groups menu of group members.

• In the form of the new request:
  • For problems, the Related Problems tab will be updated.
• In the form of the current problem:
  • The Creation of Service Request action will automatically be generated.
  • The Related Services tab will be updated.

• Publish This Element as News Article: Used to create a new news article automatically associated with the known error. The news article will automatically be displayed in the quick call for any new incident with the same category as the known error.
  • List of fields: See the New Knowledge wizard.
• In the form of the new known error:
  • The status will be For Approval.
  • The Creation of Known Error action, visible in the Actions tab, will automatically be generated.
  • If you created a news article, the News Articles tab will be updated.

• In the form of the action associated with the current object:
  • The Known Errors tab will be updated.

• The amounts displayed are amounts scheduled in contract periods. You can modified them.
• The contract will automatically be updated.
  • The Invoices of Periods tab displays a new row with the total amount of items invoiced (contract periods and common expenses).
  • The Invoiced Periods tab displays one row for each new contract period invoiced. Common expenses will not be displayed.
  • Invoiced periods will no longer appear in the Scheduled Periods tab.

• A task is related to an action type.
• The task can be charged back.
  • Hourly and/or fixed costs are defined at the action type.
  • The duration of the intervention is specified at the task.

• In the form of the current object:
  • An action with the name of the task is automatically generated and completed.
  • It is visible in the Activity tab, provided the action type authorizes its display.
  • The end date is automatically specified.
  • Tou consult the charged back costs, click the task on the timeline. The Action form will be opened and costs will be displayed on the Details > Financial tab.

• You can configure a script, a URL or a stored procedure.

• The Deployment Phase tab will automatically be updated.

• Items that are taken from stock are assigned to the recipient of the request.
• One row is displayed for each asset taken from stock.
• The Asset Tag list displays all available items in stock that are not reserved. Items with the same manufacturer reference are displayed at the top of the list followed by equivalent items of the same type.
• Processed requests will disappear from the list.

• The status of the equipment will be Lent.
• The employee who is the loan recipient will be updated in the Main User field.