☰
Navigation :

Expression

N2FE Flow Operation - Expression

The Expression Operation is used to set/adjust the values of various objects within NCC.

The nodes supported by this expression flow operation are:

These nodes correspond to various rules that the expression node can express in its ruleset. The rules are backed by similarly named OCNCC nodes.

The Expression operation has exactly one exit.

Config Parameters

The Expression operation config attributes are as follows.

Parameter Type Description
rules Array of Object [Required] The `rules` Array must contain at least one or more Objects.

Config Rules

An Expression operation rules Object takes one of the following forms.

Parameter Type Used By Description
type String (all operations) [Required] Describes the operation that is being altered by the Expression operation. Valid values are: set set_event_counter adjust_event_counter set_loop_counter adjust_loop_counter
event_counter String set_event_counter adjust_event_counter Used when setting or adjusting an event counter. The event_counter parameter names the event counter owned by the customer that is to be used within the corresponding operation.
loop_counter String set_loop_counter adjust_loop_counter Used when setting or adjusting a loop counter. The loop_counter parameter names the loop counter configured within N2FE that is to be used within the corresponding operation.
profile_block String set Used when creating a generic Set operation. This will map directly to the OCNCC profile block selector of the Set operation.
tag_code String set Used when creating a generic Set operation. This will map directly to the OCNCC profile tag selector of the Set operation.
value String (all operations) Used by all operations when adjusting/setting operations. This will be used as the value for either incrementing/decrementing or resetting of field values.

Example Operation

Here is an example Expression operation in JSON representation.

    {
        "base_node": "1",
        "type": "Expression",
        "id": "1",
        "config": {
            "rules": [
                {
                    "type": "set",
                    "profile_block": "18",
                    "tag_code": "327688",
                    "value": "1234"
                },
                {
                    "type": "set_event_counter",
                    "event_counter": "Event Counter 1",
                    "value": "0"
                },
                {
                    "type": "adjust_event_counter",
                    "event_counter": "Event Counter 1",
                    "value": "1"
                },
                {
                    "type": "set_loop_counter",
                    "loop_counter": "Loop Counter 1",
                    "value": "0"
                },
                {
                    "type": "adjust_loop_counter",
                    "loop_counter": "Loop Counter 1",
                    "value": "-1"
                }
            ],
        },
        "exits": [
            2
        ],
        "exitNames": [
            {
                "name": "Continue"
            }
        ]
    }

Each of the rules specified will generate a single node within the generated ACS control plan.

  1. A Set operation that sets the value of Call Context.CC Account Code to 1234.

  2. An EventSetting operation that sets the value of Event Counter 1 to 0.

  3. An EventCounting operation that increments the value of Event Counter 1 by 1.

  4. A Set operation that sets the value of Loop Counter 1 to 0.

  5. A ProfileCounting operation that sets decrements the value of Loop Counter 1 by 1.

The final operation in the list of rules will then exit out exit 1 to node 2.

Exits

There is exactly one exit for every Expression Node.

Exit Index Name Description
0 Continue [Required] This exit is used once the last of the configured rules has completed its processing.