Provide automations for calculating values and implementing logic so that your application can flexibly respond to unique conditions at run time. For example, you can create a process of transforming data, and, as a result, present users with relevant information when they perform work.

• Creating an activity

  Automate a system task for which a more appropriate rule type is not available by creating an activity. With activities, you define a sequential set of instructions, or steps, that the activity completes automatically. Each step calls a method or supported rule type to perform the required processing.

• Constraints rules

  Create constraints rules to define and enforce comparison relationships among property values. Constraints rules can provide an automatic form of property validation every time the property's value is "touched", in addition to the validation provided by the property or other means.

• Data transforms

  A data transform defines how to convert data that is in one format and class (the source) into data of another format and class (the target). The supported formats are clipboard and JSON. Using a data transform instead of an activity to set property values speeds up development and makes application maintenance easier.

• Decision tables

  Decision tables derive values that have one of a few possible outcomes, where each outcome can result from a test of a condition that includes multiple variables. A decision table lists two or more rows, and each row contains test conditions, optional actions, and a result.

• Decision trees

  Use a decision tree to record if .. then logic that calculates a value from a set of test conditions organized as a tree structure on the Decision tab, with the 'base' of the tree at the left.

• Declare Expression rules

  Declare Expression rules automatically calculate values based on other values that are available in your application. When you include Declare Expression rules in calculations, you increase automation and efficiently reuse resources.

• Declare OnChange rules

  Create Declare OnChange rules to run an activity automatically at activity step boundaries when the value of a specified property changes. This capability provides a form of automatic forward chaining.

• Declare Trigger rules

  To define correlations between events in your case types, create Declare Trigger rules to cause an activity to run when a specified event takes place in a case. By creating Declare Trigger rules, you automate your business processes and flexibly respond to dynamic business needs.

• Map Values

  Use a map value to create a table of number, text, or date ranges that converts one or two input values, such as latitude and longitude numbers, into a calculated result value, such as a city name. Map value rules greatly simplify decisions based on ranges of one or two inputs. Use a map value to record decisions based on one or two ranges of an input value. A map value uses a one- or two-dimensional table to derive a result.

• When condition rules

  A When condition rule evaluates a Boolean logic statement that involves comparisons among field values, to return true or false. As a result, you deliver flexible software that adjusts to changing business circumstances.

• Defining conditions in the condition builder

  Use the condition builder to create conditions that define the behavior of your application, or to use for propositions evaluated by a proposition filter. You can save custom conditions to the condition library for future use.

• Expression Builder

  The Expression Builder is a tool that guides you in authoring arithmetic and logical expressions in a natural language format. For example, you can compute an employee's salary by defining a calculation that uses properties, such as the number of years employed, employee review rating, and job grade level.

• Defining URL patterns for work items

  Share your work items with users of the same application by defining URL patterns for the work items in your application, for example, cases, reports, landing pages, or other work items, such as sitemap.xml. Simple, meaningful URLs make collaboration more efficient for users. For example, they can bookmark a case for quick access, and then send a direct link to the case to other users.