regarding (1), the easiest way to do it would be actually defining an alarm in SCI. Go to SCI, click on new alarm, and then press Help. It will show you all the possible codes you can use to base your reaction on. Chances are most of the alarms you want to create are already in SCS Then, you can use Reaction in SCI to send an email or SNMP
regarding (2), I would suggest to use sub-routines, because you can pass variables from one strategy to another.
Genesys does have global variables, but their scope is only within the strategy itself, so it would not do you any good. If you have to call one strategy from another, I strongly urge you to consider having one global strategy with subroutines that can be called along with parameters you want to pass both to subroutine and from them.
One thing you do not want to do is use attach-data to pass data from one strategy to another, because in almost all of the instances attach-data would not arrive in time for your second strategy to read it.
Would your answer to 2 still be relevent if they were to use the KV string and set a new KVP in the string before passing the call onto the next strategy?
I agree that it would be best to just have a global strategy incorporating everything that you would need for each scenario (as you have said), however there may be a specific reason for nabnikulin to route between strategies.
The problem will be as to generate event including his ID. What object in strategy can be used and as? I tried “sendevent error”, but each time appears event in a log URS without event ID (i.e. it is not possible to set ID). In result SCI cannot identify this event.
if you will use KV string, you will see that it will be possible for a call to arrive to the next routing point before user-data is updated.
I strongly discourage people from using user-data to pass information between strategies using user-data.
If ANI the subscriber that corresponds to the specified values in the List Objects, then strategy should play announcement and send the message to E-mail.
Alarm
Parameters: Alarm Number: INTEGER or variable
Alarm Message: STRING or variable (representing a string)
Return value type: VOID
This function sends an alarm message through the URS management API. This message can be used, for example, by the Genesys SNMP Master Agent as a client of the URS management API to generate a polling trap. For more information on setting alarms, see Framework 7.2 Getting Started Guide, Management Layer Functionality chapter. Also see Framework 7.2 Management Layer User’s Guide, SNMP Interface chapter. The alarm is sent along with the following information: the supplied Alarm Number, the Alarm Message, and the current interaction’s ANI, CED, DN, and Tenant.