How can we attach SLA for and incident using FLOW

Arun61
Tera Contributor

‎06-15-2023 01:10 AM

We have a requirement like when an incident is created and if no SLA attached with in 3 days i need to attach a new SLA (which i was create) and this should be done using FLOW designer can any one please help on this.

0 Helpfuls
  • 1,455 Views
1 REPLY 1

Community Alums
Not applicable

‎06-15-2023 01:23 AM

Hi @Arun61 ,

Configure your Service Level Agreement (SLA) definition to run a flow as the action plan.

Before you begin

About this task

An SLA Task trigger only runs when a task record matches the conditions of a Service Level Agreement (SLA) definition. For example, you can run a flow whenever an incident record matches the Priority 1 resolution (8 hour) SLA Definition.

Procedure

  1. Navigate to All > Process Automation > Flow Designer.
  2. Select + New > New Flow.
  3. On the form, fill in the fields.
    Flow Properties form
    Field Description
    Name Name to uniquely identify your flow. The system computes the internal name of the flow from the name.
    Application Application scope to create your flow in. Global is the default.
    Description Description of your flow.
    Protection Selection to specify if the flow is read-only. You can only select a value when you create the flow in an application scope that you own.
    Run As

    Option that you can select to specify that the flow runs as a system user or the user who initiates the session. Select the user who initiates the session option when updates should come from the user who triggered the flow. For example, use this option when you want the incident record comments to come from the current user, or if you want the approval emails to originate from the approver. Settings for the Run as option in a flow don't apply to child subflows.

    The system runs flow actions as the user who initiates the flow. Verify that all users who can trigger a flow have the necessary security access to run its actions. The initiating user also determines user-specific settings such as date/time formats.

    Note: Inbound email flows ignore this setting and always run as the user who initiates the session. To test access controls for an inbound email flow, impersonate a typical inbound email user and manually trigger the flow.
  4. Select Submit.
    The system displays the Flow Designer page.
  5. Select Select to add a Trigger > Application > SLA Task.
  6. Add actions, subflows, and flow logic to the flow.
    Add SLA Percentage Timer actions to specify what to do when a task record attached to an SLA reaches specific percentages of completion.
  7. Test the flow.
    For more information, see Test a flow and Activate a flow.
    Once behaving as desired, activate the flow.
  8. Create an SLA definition
    1. In the Flow field, select the SLA Task flow you previously created.
      Note: The Flow field only displays flows with an SLA Task trigger.
    2. Click Submit.

Result

When the SLA Definition conditions are true, the system runs the specified SLA task flow.