What is hit policy in SAP LOD-BPM-WFS - Workflow Service Runtime / Editor?

SAP Term: hit policy

• Component: LOD-BPM-WFS

• Component Name: Workflow Service Runtime / Editor

• Description: Specifies the output of the determination process in decision tables in cases where more than one rule in the table is matched for a given set of batch-based inputs. There are two types of hit policies: First Match: The first occurrence that matches the input condition is fetched and returned as result. All Match: All the occurrences that match the input condition are fetched and returned as result.

Smart SAP Assistant

• Key Concepts: 
  Hit policy is a feature of the SAP LOD-BPM-WFS Workflow Service Runtime / Editor. It is used to define the order in which tasks are executed in a workflow. It allows users to specify the order in which tasks should be executed, as well as the conditions that must be met for a task to be executed. 
  
  How to use it: 
  Hit policy can be used to define the order in which tasks are executed in a workflow. To do this, users must first create a workflow and add tasks to it. Then, they can select the hit policy from the drop-down menu and specify the conditions that must be met for a task to be executed. 
  
  Tips & Tricks: 
  When creating a workflow, it is important to consider the order in which tasks should be executed. This will help ensure that tasks are completed in an efficient manner and that all necessary conditions are met for each task. 
  
  Related Information: 
  Hit policy is just one of many features available in the SAP LOD-BPM-WFS Workflow Service Runtime / Editor. Other features include task assignment, task routing, and task execution.