Then will show a brief description of the functionalities and properties of the applications that can use in the workflow.
This activity is necessary to give the sart the to flow in the same context will indicate that the flow and extension is performed.
This extension are detailed previously in Workflows Designer v5
Fields:
This application answerd the call.
Fields:
The language that it producing the call is stored.
Field:
It can create variables and assign values one that already exist, this variables can be used in all the flow and can store in the database.
Fields:
This application generate a unique identifier of the call and assign the value automatically to the variable ${guid}.
To let this value unique (the GUID) in the CDR.
To assign the CDR type,it can be record (to record the conversation), voicemail(if email mailbox ) or fax (if it incoming fax).
Assign the identifier to the recording, usually use ${guid}.
This application emits an audio and wait an answer which can store a variable, usually is used to generate menus.
Fields:
To assign the name of the campaign to CDR.
Fields:
Derives the call to a queue.
Fields:
The Hash function will take all the data from the rows in the data base and makes them more "accessible" for the user to make queries.
This last query will return a row, for example:
HASH(query) = (name, CallerID, Agent, Campaign) → HASH(Result) = (Sophie, 0800, Agent1, Campaign1)
If the user wants to get an specific data from the row, using the example above, the user must use the following:
HASH(Result, name) → "Sophie"
HASH(Result, CallerID) → 0800
HASH(Result, Agent) → Agent1
HASH(Result, Campaign) → Campaign1
Example:
In this example, we can see that the variable that takes as parameter the function Hash, is called Result. To the right, the user wrote the query that the variable Result represents.
The following will return a row containing the consulted data from the columns (did, name, dialstring).
The While function consists of a condition and a block of code called an expression. This function checks if the condition is true, if it is, executes the expression. The lasts steps repeat themselves till the condition is false.
Applied to a workflow, for example:
We have the While action, that contains the condition, then it continues with the block of code that gets to be executed if the condition is true, if it is, the block of code executed as long as the condition is true. When this one is false, the workflow will get to the EndWhile action and continue the flow.