Home

Brand Mobiliser Development Manual

Contents

1. Attribute 1 Attribute 2 Attribute 3 v Follow up States Showing 1 2 oK Send SMS Q2 iA Fail Send SMS ERROR Select a follow up state M Add Follow up ve 72 Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Registration Descriptions Register a new mobile consumer using the basic registration information The registration includes the creation of the following basic account features for the consumer e Stored Value Account SVA e Setting the PIN This state can also be used to update the basic information of an existing consumer but all the required input variables must to be provided Input Variables Identification type Not used To be removed Identification of the consumer Not used To be removed NOTE the consumer identification value is forced to the consumer MSISDN obtained from the incoming message Currency for new consumer Currency value Country of new consumer Country value Organizational unit of new consumer Organization unit value Credit limit to assign to new consumer Credit limit value Name of new customer Customer name Language of new customer Language code value Passport no of new customer Passport number or other unique id for customer e g social security no PIN for new customer PIN value Follow up State OK Registration completed s
2. Brand Mobiliser provides a number of basic stand alone states including states for composing workflow that are referred to as Base State and states for performing operations on the Subscriber storage known as the Subscriber State In addition service states for integrating with the Money Mobiliser platform are also included by default Additional custom states can be easily developed using the provided State SDK to meet any customer specific requirements These custom states can be added dynamically using the plug in mechanism enabled by the OSGi Services Registry Please consult the reference Brand Mobiliser State Developers Guide on how to develop and deploy plug in states for use within the Brand Mobiliser There are two types of application Interactive and Event differ by how they are used and invoked Interactive application is used for providing a rich user interactive mobile service This type of application is typically invoke by mobile customers sending a keyword to a pre assigned short code The Event application is designed for workflow or batch processing The workflow or batch type of application is typically invoked by event such as scheduled time s system trigger or external trigger events So unlike the interactive application the event application is not associated with keyword s Applications are composed using the Application Composer Most of the states in Application Composer are accomp
3. VAR2 Right Variable v Follow up States Showing 1 2 OK Send Variable Values Equal A Fail Send Variable Values Not Equal Select a follow up state v Add Follow up Save Usage Scenario 1 a simple and commonly used scenario of the Compared Typed Variables will be in prompting PIN with limited retry This scenario is supported using a combined Counter and this Compared Typed Variables states as shown below ci RETRY lt 3 PIN CREDENTIAL PIN Variable Variable Send SMS Send SMS Vioney Mobiliser GOTO APPLICATION ABORT Delete LJ Name m v Input Variables Showing 1 5 INTEGER o H Variable Type UU C Select an entry z Text Case Sensitive Default No None po e lt RETRY_COUNT Left Variable v Input Variables Showing 1 1 SSS E RETRY_COUNT Variable name E operator v Follow up States Showing 1 2 3 e Right Variable Fail Select a follow up state i me v Follow up States Showing 1 2 Target Check PIN Retry lt 3 x ox Prompt for PIN o El Expression Assign To Fail Goto Application Abort 5 Seeaatowup site IES Eao U For reusability this scenario is usually encapsulated into the Sub Application as shown in the Application Call state Usage Scenario 1 58 m Brand Mobiliser Development Manual Fy Version 1 2 September 2011 Base State creates a variable that is increased by o
4. g OK Select a follow up state See the Get Customer Information for other customers information See the Get Customer Attributes for a specific customer attribute See the Get Customer Product state for the customer product ID Brand Mobiliser Development Manual Version 1 2 September 2011 101 Money Mobiliser State Customer Management Name Get Customer Attributes Loads a customer and returns an attribute value for a specified attribute id Input Variables Output Variables Follow up State OK Follow up State Fail Follow up State DYN 102 m Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification
5. Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory The New name of the customer customer new name Follow up State OK Save successfully Follow up State Fail Set customer name failed for unknown reason Follow up State DYN Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found v Name New Mobiliser Set Customer Name state 30 E Notes v Input Variables Showing 1 3 O Selectanentry Identification type Identification of the customer overrides session NAME The new name ofthe customer Y Follow up States Showing 1 2 A OK Select a follow up state i A Fail Select a follow up state Select a follow up state v Add Follow up C PSS 108 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 Money Mobiliser State Customer Management Name Set Customer Attribute Add or modify a specific customers attribute value Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when
6. MAX length of display name This parameter limits the length of the name that is displayed Output Variables a Customer ID The customer identification Blacklist Reason ID If the customer is blacklisted a blacklist reason is set based on an ID defined in Appendix B1 Language The customers preferred language code for example en for English Country The country code the customer comes from For example US for United States DE for Germany etc Display Name The customer displayed name Orgunit The organizational unit This is a grouping of customer For example a grouping of regions that includes the region the customer comes from Security Answer The answer to the security question selected by the customer Security Question The security question Is Active true false Indicates whether the customer is active or not Is Test true false Defines whether the customer is a test user or a real user Is blocked until milliseconds f the customer is blocked contains the remaining blocking time in milliseconds Currently this field could return null so when used directly with the Send SMS could be a problem For now need to check the null in the application flow This limitation will be enhanced in the future to prevent null MSISDN The customers telephone number Product ID The product defines the customer type This ID is used to differentiate between a Street Agent Mini Agent Sup
7. 93 94 Also see the Get Languages state Languages are setup in Brand Mobiliser M_LANGUAGES table Currently setup is performed using DB script only Brand Mobiliser needs to be restarted to the changes to be available Scenario 1 a typical and minimal required implementation of the menu list state like this one requires to implement the follow up states for both DYN 0 and 1 i e empty list and single item list respectively because the menu list will be skipped in these two cases and immediately transition to the follow up state Otherwise the application will just terminate See Get Wallet Menu state Scenario 1 Brand Mobiliser Development Manual Version 1 2 September 2011 Set Language Session Money Mobiliser State Account Management Set the selected language of the current customer in the Brand Mobiliser session context so that it is used for the rest of the session Input Variables The selected Language The language to be set e g en de etc Follow up State OK Follow up State Fail Successfully setting the language into session context Possible reasons e Unsuccessfully setting the language into the session context e Selected language does not exist in the system Follow up State DYN e Other unexpected error LJ v Name New Mobiliser Set Language Session onl BO Notes v Input Variables Showing 1 1 LANGUAGE The selected Language Expects a loca
8. ATTRIB1 ATTRIB2 ATTRIBS ATTRIB4 ATTRIBS Attribute 1 Attribute 2 Attribute 3 Attribute 4 Attribute 5 v Follow up States Showing 1 2 OK Fail Select a follow up state v Select a follow up state Select a follow up state v Add Follow up Scenario 1 see the Process Subscriber state Usage Scenarios 1 and 2 for how the Get Subscriber state is used Scenario 2 the Get Subscriber state can be used to handle blacklist or whitelist The following example shows it is used for blacklist The Check Subscriber For Blacklist is a Get Subscriber state It checks whether the MSISDN exists in the Blacklist set The OK means the MSISDN exists so the message should not be sent The Fail means otherwise so Brand Mobiliser Development Manual Version 1 2 September 2011 67 68 the message can be sent To use as for whitelist just reverse the OK and Fail transitions HANDLE PROCESS CHECK OK SEND SMS BLACKLIST SUBSCRIBER SUBSCRIBER FOR STATE STATE BLACKLIST GOTO END U v Name Check Subscriber for Blacklist D v Input Variables Showing 1 2 ll Blacklist Iz Subscriber Set MSISDN Subscriber MSISDN j wv Output Variables Showing 1 5 6 10 11 15 16 20 All ATTRIB1 Attribute 1 ATTRIB2 Attribute 2 ATTRIB3 Attribute 3 ATTRIB4 Attribute 4 ATTRIBS Attribute 5 v Follow up S
9. An MSISDN The payers selected PI ID if a pre selection has been made A PI ID Typically this is obtained from the Get Wallet Menu menu list followed by the customer select an PI See Get Wallet Menu state Show Exit menu item This defines whether the Exit menu item 0 Back should be displayed O no 1 yes Output Variables j Currency of the selected PI A currency code Variable of the selected KEY This is the number assigned to the menu item Variable of the selected VALUE This is the text of the menu Follow up State OK Customer selected a currency from the menu list The selected currency and all its attributes are stored in the output variables Follow up State Fail Possible reasons are e Web service internal error Follow up State DYN 0 zero item in the menu list 1 only one item in the list and it is automatically selected and stored in the output variables EXIT customer select the 0 Back 106 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 LJ v Name New Mobiliser Get Currency Menu state Tl Notes Message 0 760 characters v Input Variables Showing 1 5 Select an entry Identification type Identification of the customer overrides session The payees MSISDN The payers selected PI ID if a preselection has Show Exit menu item 1 yes O no Default 1 v Output Variables Showing 1 3
10. DASHBOARD PROGRAMS SUBSCRIBERLIST ASSETS PERFORMANCE AND ANALYTICS WORKSPACE ADMINISTRATION Actions 7 assets Interactive Applications Cash Out Process Application Actions SAVE LAYOUT LOAD APP Gridlines All v Zoom 70 v Aj ENTER TX CONFIRM TX CASH OUT SUCCESSFUL AMOUNT ACCOUNT PIN TX INVALID AGENT UMKNOUVN AGENT NOT INVALID AMOUNT 4 INSUFFICIENT CONFIRM TX INSUFFICIENT AGENT SVA LMT VURONG TOO MANY CODE FORMAT AGENT CODE APPLICABLE FUNDS PREAUTH SVA FUNDS HIT ACCOUNT PIN WRONG PINS AGENT SVA LIMIT HIT PREAUTH ERROR BACK TO MENU APPLEATDN MAIN MENU APPLICATION DETAILS APPLICATION COMPOSER W t4 Ei le a a CASHOUT ENTER AGENT PROCESS ccoE WEED PIN FORMAT AMOUNT NEAN MO BILIGER THN PRE AUTHORISE SEND MONEY VALIDATE AGENT CODE FORMAT GET AGENT INFORMATION I APPLICABLE AGENT All immm E Jj i gt gt Recent Activity Log gt Related Items Copyright 2010 Sybase Inc An SAP Company Contact Support About Brand Mobiliser SYBASE ma TY company Figure 30 Application Composer View of Cash Out Process 33 Brand Mobiliser Development Manual Version 1 2 September 2011 4 4 State Editor The figure below shows the first portion of the Application Composer view of the Cash Out application EJ Cash Out Process APPLICATION DETAILS APPLICATION COMPOSER MA Application Actions z
11. VOUCHER_AMOUNT Amountto transfer Identification of the customer overrides session B By mobile no Payer Identification Type 7 PICKUPCODE The pickup code for the remittance Payer Identification Output Variables Showing 1 3 Output Variables Showing 1 3 VOUCHER_PI ID The pild ofthe Voucher PAYER_FEE The fee forthe payer VOUCHER_CURRENCY The vouchers currency PAYEE_FEE The fee for the payee VOUCHER_AMOUNT The vouchers amount PAYEE_NAME The name of the payee v Follow up States Showing 1 2 v Follow up States Showing 1 2 OK Pre Authorise Voucher Pickup gt ok Confirm Fail Select a follow up state ji Fail Select a follow up state Ie Select a follow up state M Add Follow up Save v Input Variables Showing 1 5 6 6 All I PICKUPCODE The pickup code of the voucher 7 VOUCHER_CURRENCY Currency of transaction 175 Use Case ID VOUCHER_AMOUNT Amount 7 VOUCHER_PI_ID Payer PI ID Output Variables Showing 1 2 TXN ID Transaction ID AUTHCODE Authorisation code v Follow up States Showing 1 2 OK Success Ly Fail Select a follow up state Tz Select a follow up state 7 Add Follow up Save Brand Mobiliser Development Manual Version 1 2 September 2011 145 Money Mobiliser State
12. 16 20 All MESSAGE Attribute 1 ATTRIB2 Attribute 2 7 ATTRIB3 Attribute 3 F ATTRIB4 Attribute 4 ATTRIBS Attribute 5 v Follow up States Showing 1 2 Q OK Send SMS F Fail Goto END z Select a follow up state 7 Add Follow up Save GET SUBSCRIBER INFO Delete Message MESSAGE Social Networking Inc 34 160 characters v Input Variables Showing 1 1 No lal Request SMPP Acknowledgement Select a follow up state BA eee Save Scenario 3 Dynamic message push campaign The uploaded subscriber set contains attributes that are used to construct the customized message dynamically Brand Mobiliser Development Manual Version 1 2 September 2011 65 v Name Get Subscriber Info Bo EE Notes v Input Variables Showing 1 2 Subscribers Subscriber Set 7 MSISDN Subscriber MSISDN v Output Variables Showing 1 5 6 10 11 15 16 20 All GENDER Attribute 4 fw AGE Attribute 2 Attribute 3 7 ATTRIBS Attribute 4 r z Message Hi MSISDN your balance is BALANCE Thanks BANK Send Re J Sosa ted more for discount coupon v Follow up States 87 160 characters OK Send SMS Showing 1 1 Fail Goto END Request SMPP Acknowledgement Add Follow up Save Scenario 4 more complex campaign with filtering can be
13. 21 22 All testList v Subscriber Set MSISDN Subscriber MSISDN Attribute 1 Attribute 2 Attribute 3 v Follow up States Showing 1 2 A OK Select a follow up state v A Fail Select a follow up state Notes Usage Scenario 1 the Update Subscriber state can be used for example voting application Initially the voting participant is added to the Voting Result list Subsequently the Update Subscriber state is used to insert the answer into other fields as shown below The following example also implements winner for the 100 voting participant The Add Subscriber returns the total number of subscriber in the list that can be used to identify the 100 participant The Set Variable state is used to store the participant s response to a question before Brand Mobiliser Development Manual Version 1 2 September 2011 71 updating the Voting Result list ADD SUBSCRIBER CHECK WINNER CALLER SEND SMS BYE STATE SUBSCRIBER NO 100 Delete r t ce r aS Message Are you 17 years old Yes or No 31 160 characters Follow up States Showing 1 2 Target Set Q1 Yes bd Expression Yes lt lt q Assign To Target SetQ1 No v Follow up States Showing 1 1 Expression K Update Q1 v Input Variables Showing 1 5 6 10 11 15 16 20 21 22 All C Movie Vote Subscriber Set MSISDN Subscriber MSISDN
14. Get Customer Product state for the customer product ID Brand Mobiliser Development Manual Version 1 2 September 2011 103 Money Mobiliser State Customer Management Input Variables Output Variables Follow up State OK Follow up State Fail Follow up State DYN 104 m Loads a customer and returns the customer product in the response and as an output variable Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Product ID product ID Product ID needs to be obtained from configurations or customization specification documents N A This is a limitation now In the future the O
15. INVALID AGENT Expression 2 Assign To MENU SE F seictatolowpsite n Brand Mobiliser Development Manual Version 1 2 September 2011 61 Agent Code Check Sub Flow RETRY COUNTER CHECK RETRY PROMPT AGENT CHECK CODE CHECK AGENT VALID AGENT lt 3 6 DIGIT CODE HASS 6 DIGITS CODE STATUS 0 INVALID AGENT APPLICATION STATUS 2 CALL RETURN WITH STATUS INVALID FORMAT STATUS 1 3 JU v Name Invalid Format STATUS 1 J Notes Variable STATUS Value 4 UUW y Name Application Call Return with STATUS JE v Follow up States Showing 1 1 v Input Variables Showing 1 4 OK Application Call Return with STATUS I5 7 STATUS An optional Return Value Select a follow up state M Add Follow up Save 62 Brand Mobiliser Development Manual Version 1 2 September 2011 Base State nome Aon Cae If you define an application that is to be called by another application the application can return a value This state assures that a value is returned This is an end state N A LJ v Name Return to caller 3o Notes v Input Variables Showing 1 1 C SUCCESS An optional Return Value Select a follow up state v Add Follow up e This state can be used for Interactive Application only Scenario 1 please refer to the Application Call state Usage Scenario 1 for example Brand Mobiliser Development Manual 63 Version 1 2 September
16. The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Info Mode The chosen mode The dropdown list choices are None SMS Email SMS and Email Follow up State OK The opted choice have been updated Follow up State Fail Possible reasons are e Update failure e Web service internal error e Web service connection error U Name New Mobiliser Set Info Mode state ol W Notes v Input Variables Showing 1 3 O Selectanentry Identification type Identification of the customer overrides session O Selectanentry v Info Mode v Follow up States Showing 1 2 Z OK Select a follow up state k Fail Select a follow up state Selec
17. The watermark allows for quick recognition of different state types in the layout view and the popup window 22 m Brand Mobiliser Development Manual E Version 1 2 September 2011 3 Popup Drag Area The state window can be moved anywhere inside the application composer page To move the state click on the dotted header area and drag the state to the desired position 2 State Type Watermark and Icon 3 Popup Drag Area 4 Encryption 5 lie Clase 1 Entry Nodes g Ww aria E aac 8 Inputs Section Input Variables Showing 1 3 6 State Type Notes 9 Variable Pagin C By user name v Identification type Sing AGENT_CODE Identification of the customer overrides session MAX length of display name v Output Variables Showing 1 5 6 10 11 15 16 18 All 11 Variables Paging 10 Outputs Section CONSUMER_RECEIPT_I Consumer Receipt Mode ID CONSUMER_CANCELLA Consumer Cancellation Reason ID IS_CONSUMER_ACTIVE Is Consumer Active true false 12 Follow ups Section e 7 Follow up States Showing 1 3 13 Follow up Paging OK Is applicable agent A Fail Error back to menu 14 Exit Nodes Target Unknown agent code Expression 1010 Assign To 15 Follow up Selector 9 Select a follow up state v Add Follow up Save 16 State Actions Figure 17 State Editor Popup 4 Encryption The state encryption option allows a state to never show the messages it sends out or inputs it
18. Utility Descriptions Formats the entered amount of a given currency It checks the validity of the entered amount and returns it in formatted form The amount is reformatted to comply with the number of decimal places specified for the respective currency and rounded off if necessary Input Variables Amount to be formatted The value of the amount to be formatted The currency of the amount The currency of the amount to be formatted Minimum valid amount The minimum valid value of the amount Maximum valid amount The maximum valid value of the amount Output Variables The formatted amount The reformatted amount is returned here Follow up State OK The amount to be formatted has been formatted and stored in the output variable Follow up State DYN MIN the value of amount to be formatted is less than the minimum valid amount MAX the value of amount to be formatted is larger than the maximum valid amount v Input Variables Showing 1 4 AMOUNT Amount to be formatted CURRENCY The currency of the amount C 10000 Minimum valid amount C 6000000 Maximum valid amount v Output Variables Showing 1 1 AMOUNT_FORMATTED The formatted amount v Follow up States Showing 1 3 A OK New Mobiliser Txn Pre Authorise Send Money state v A Fail Invalid amount Target Amount too low shigh Expression MINIMAX Assign To 146 m Brand Mobiliser Development Manual E Versi
19. Y N internal only Setting to allow the capture to be different amount than the authorized amount Y N Setting to allow payer and payee to be identical Y N Passive participant can be created on the fly if unknown in the system with BLR set Y N 12 m Brand Mobiliser Development Manual E Version 1 2 September 2011 The sample of pre defined use cases are listed on the following tables with the attribute settings 100 siemens ele fe wd mf a cc omea e fet y w lo wm fa t fe feed fo eww EEEE mememe EEEE 2 4 7 Money Mobiliser Web Services The services on the Mobiliser Money platform can be grouped into the following functional categories Mobile Consumer Registration Security Authentication Authorization amp Blacklist Mobile Accounts Management Mobile Consumers Management Money Transaction Services Mobile Consumer Registration Mobile Security AA amp Blacklist Registration Login Check Identification Check Credential PIN Brand Mobiliser Development Manual 13 Version 1 2 September 2011 Set Identity Change Credential Set Blacklist Reason Block Until Delete Network Entry Mobile System Management Mobile Consumers Management Get Language Check Customer Get Language Menu Customer Has PIN Get Currency Menu Get Customer Information Set Language Session Get Customer Address Get Customer Attributes Get Customer Product Set Customer Name Set Info Mode Set Receipt Mode Set
20. Zoom 100 bad SAVE LAYOUT REVERT LAYOUT Gridlines All v E CASH OUT GET WALLET ENTER AGENT Kna Get Wallet Menu JE Hotes PROCESS MENU Message Please selectthe source account Ul 33 760 characters Input Variables Showing 1 5 6 6 All O Select an entry 4 v Identification type Identification of the customer overrides session 0 41 42 List of Pl types Example 12 123 45 List of PI classes Example 1 2 3 Max count of Pls gt Output Variables ERROR BACK TO MENU v Follow up States Showing 1 3 4 4 All g OK Enter agent code Fail Error back to menu v Target Enter agent code Expression Assign To vi amp i u Select a follow up state v Add Follow up Save gt Recent Activity Log gt Related Items Figure 31 Application Composer View of Cash Out Process 34 Brand Mobiliser Development Manual E Version 1 2 September 2011 5 How to Test Applications It is possible to test applications you have constructed in Brand Mobiliser in a number of different ways e Using the built in application simulator that is part of the Brand Mobiliser Web UI e Using an SMPP test harness or a JMS test harness These methods are more suited for state plugin developers or advanced system administrato
21. 0 End smapp Mobiliser Tester Login 123456 1234 smapp Mobiliser Tester Login 123456 4 gt Mobiliser Tester Login Enter your credentials smapp Mobiliser Tester Login 123456 mobiliser menupage Startpage 123456 4 Startpage Welcome to Mobiliser Tester send mobiliser to continue menupage Startpage 123456 hello Figure 38 Mobiliser Counter Simulation 2 In this case the keyword match was confirmed as successful and the counter is incremented and re displayed to customer From this point any other input will return to the menu from which the customer can continue with other functions or choose to end their session The figure below shows the remainder of this simulation session returning the menu and then ending the session Refresh message log Client Timestamp Message Receiver MSISDN Dir Msg 21 12 2010 11 52 50 21 12 2010 11 52 50 21 12 2010 Mobiliser Menu Misc 11 52 42 smapp Functions 21 12 2010 Mobiliser Menu Misc 11 52 42 Smanp Functions 21 12 2010 11 52 35 21 12 2010 11 52 35 21 12 2010 11 49 22 21 12 2010 11 49 21 21 12 2010 Mobiliser Menu Misc 11 44 21 smaPP Functions 21 12 2010 Mobiliser Menu Misc 11 44 20 smaPP Functions 21 12 2010 ii Test Ident 447977257100 1 Check Identification 2 Check Credential 3 Change Credential 4 Counter 11 44 17 amapp Mokihsar Manu Top 123456 t 5 Copy Var 6 Get Languages 0 Back 21 12 2010 11 44 17 21 12 2010 11 44 12 21 12 2010 11 44 10 12 20
22. 2011 Subscriber State Descriptions This state is used in Event Applications to retrieve the next subscriber from a subscriber list and assigns that subscriber as the effective MSISDN for the application The application will then continue for example send a message to the MSISDN and then will most likely return to this state in order to get the next subscriber or to end the Event Application Input Variables Subscriber Set the subscriber set to use The drop down list presents the subscribers in the workspace Follow up State OK A subscriber is available to be processed for this event Follow up State Fail This event window processing has finished with error with the following possible Follow up State DYN END The end date for the window has been reached FINISH Event window processing has completed due to window finish COMPLETE There are no more subscribers returned from the subscription finder service NOTE If the END FINISH COMPLETE dynamic transitions are not handled they behave the same as the OK transition ie y Name New Process Subscriber state 30 W Notes Y Input Variables Showing 1 1 testList v Subscriber Set v Follow up States Showing 1 2 A OK Send Event Message b A Fail Select a follow up state Select a follow up state v Add Follow up Applicable to event application only When the Send SMS state is used in Event Application the Request SMPP Ackno
23. 3 Attribute 4 3 Output Variables Showing 1 1 NINDS Es SUBSCRIBER_COUNT Total subcriber countin the list v Follow up States Showing 1 2 v Follow up States Showing 1 2 ok Add Subscriber state oK Send SMS Coupon E Fail Select a follow up state 2 Fail Select a follow up state T Select a follow up state M Add Follow up Save Select a follow up state Add Follow up Save 70 Brand Mobiliser Development Manual Version 1 2 September 2011 Subscriber State Descriptions This state updates the subscribers attribute from the selected subscriber list The subscriber MSISDN is retrieved from the session variable MSISDN by default Up to 20 subscribers attribute can be updated Input Variables Subscriber Set the subscriber set to use The drop down list presents the subscribers in the workspace Subscriber MSISDN the MSISDN unique key of the subscriber to add Attribute 1 20 The attribute values from the session variables are inserted into the subscriber set Follow up State OK Successfully update the subscriber to the set Follow up State Fail Error while adding the subscriber and its attribute due to one of the following possible reasons e MSISDN does not exist e Non recoverable system error such as database connection etc U Name J wees v Input Variables Showing 1 5 6 10 11 15 16 20
24. 5 6 6 All PICKUP CODE The pickup code of the voucher a CURRENCY Currency of transaction a USE CASE Use Case lD x VAR_MAME_AMOUPT Amount a K Payer FI ID lt Optional Transaction Text Y Output Variables Showing 1 2 TAR ID Transaction ID ALITHOODE Authorisation code Y Follow up States Showing 1 2 ca OK Select a follow up state A Fail Select a follow up state 144 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Usage Scenario 1 the send voucher remittance is typically complemented by the pickup voucher remittance flow After a successful send voucher remittance see scenario 1 above a pickup code is generated The pickup code can be shown to the sender but behind the scene money mobiliser will send a notification message with the pickup code to the voucher receiver The receiver can redeem the voucher using the pickup voucher flow shown below Error handlings have been omitted for clarity ENTER FIND PRE AUTHORISE CONFIRM PICKUPCODE REMITTANCE VOUCHER VOUCHER PICKUP SUBFLOW CHECK PICKUP PIN VOUCHER STATE WU v Name Pre Authorise Voucher Pickup bw mF Notes input Variables Showing 1 5 6 10 11 11 All W e z a F VOUCHER_CURRENCY Currency of transaction v Name Find Remittance Voucher 3 tes L Ss 4 input Variables Showing 1 3 175 Use Case ID By mobile no x Identification type
25. CUSTOMER Indicates that the or a customer specified in the request cannot be used considered because he is inactive see database CUSTOMER BOL_IS_ACTIVE 1007 WARN TEST LIVE MIX Indicates that the or a customer specified in the request cannot be used considered because his test status see database CUSTOMER BOL_IS_TEST is not the same as the transactions te INFO WARN WARN 1011 WARN ENTITY NOT UNIQUE Indicates that an entity that was about to be created conflicts with an already existing entity 1101 ERROR AUTHENTICATION MISSING Indicates that the authentication data is missing 1102 FATAL AUTHENTICATION INVALID Indicates that the authentication data is invalid malformed 1111 WARN UNKNOWN USER Indicates that no customer could be found for the specified identifier 1112 INFO INACTIVE USER Indicates that the customers status is inactive see database CUSTOMER_STATUS BOL_IS_ACTIVE 1113 WARN INVALID CREDENTIALS Indicates that the specified credentials are wrong credentials have been specified CUSTOMER ID_BLACKLISTREASON as of now blacklisted as of now 1121 INFO CREDENTIALS EXPIRED Indicates that the specified credentials have expired 1131 WARN IP_ BLOCKED Indicates that the IP specified in the request is blocked for a certain time 1201 ERROR NO AGENT DATA Indicates that no agent customer data could be found 1202 ERROR INACTIVE AGENT Indicates that the agent customers status is inactive see database CUSTOMER_STA
26. Development Manual Version 1 2 September 2011 79 See also the Login state This is the recommended state instead of the Login state Also see the Customer Has PIN state Scenario 1 use to challenge the customer with the PIN for extra security This can be done once at the beginning of the workflow or repeat anywhere in the workflow as necessary prior to performing sensitive action such as money transfer etc PROMPT PIN MOBILISER PROCEED WITH LOGIN CHECK ACTION PIN Send SMS Maney Mobiliser Send SMS ABORT OR RETRY PIN Scenario 2 allowing PIN retry on fail login COUNTER STATE COMPARE TYPED PROMPT PIN MOBILISER PROCEED WITH VARIABLES LOGIN CHECK ACTION COUNTER PIN Variable Varlable Send SMS Send SMS ABORT amp BYE Send SMS 80 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Money Mobiliser State Security AA amp Blacklist a Descriptions Create a new or update an existing Identity of the current customer Identity is also known as Identification Input Variables Identity type The identity type ID integer The default preconfigured IDs are listed in Appendix B5 Additional identity types may be added during customization Please check the customization specification document Identification The string value of the identity type to set Follow up State OK New identity has been added or update is successful Follow up State Fail Po
27. If the Identification type is by customer id or by username the Identification of the customer is mandatory Text to be evaluated This text is used for reference LJ vy Name New Mobiliser Txn Authorise Transaction 30 Notes v Input Variables Showing 1 3 O Selectanenty Identification type Identification of the customer overrides session SMS_TEXT Text to be evaluated v Follow up States Showing 1 1 Fail Select a follow up state Select a follow up state v Add Follow up Brand Mobiliser Development Manual o Version 1 2 September 2011 Money Mobiliser State Transaction Service Name PresAuthorize Send Money Descriptions Send money transaction should be conducted using a two step transaction involving Pre Authorization and Commit as follows e Pre Authorization checks whether there is enough money available for the transaction followed by reserving the money so that it is not accessible for other transactions The Pre Authorization also retrieves the fees that will be charged to perform the transaction The fees are modeled using different Use Case IDs that are implemented in Money Mobiliser The Pre Authorization is performed using this State e Commit proceed the actual transaction of debiting the money and fees This state is used in conjunction with the Send Money state Input Variables Currency of transaction The currency for the
28. MOBILISER MOBILISER SHOW COUNTER SOTO MENU COUNTER COUNTER STATE OPTIONS APPLICATION Money Mobiliser Send SMS Go To Application Start Application Ul SHOW COUNTER R Figure 11 Dragging a State in the Application Composer View Note The canvas will not allow absolute free form positions and each state will be snapped to a specific grid position as highlighted when being dragged Releasing the left mouse button while positioned over a target grid position will cause that state icon to be moved into that grid position and all transition lines into and out of that state will be automatically re drawn The figure below shows the outcome of moving a number of the states in the figure above into different grid positions Mobiliser Counter APPLICATION DETAILS Kevworns APPLICATION COMPOSER APPLICATION EDITOR Application Actions 7 SAVELAYOUT REVERTLAYOUT TA Zoom 100 v A MOBILISER MOBILISER COUNTER COUNTER STATE APPLICATION Vaney Mobiliser SHOW COUNTER send SMS Start Application Lill SOTO MENU OPTIONS Go To Application Figure 12 Moved State in the Application Composer View The SAVE LAYOUT button and the REVERT LAYOUT button will be enabled when state has been moved or there are layout changes The SAVE LAYOUT button will save the layout to the database The REVERT LAYOUT button will reload the last saved layout 18 m Brand Mobiliser Development Manual V
29. Name Check Identification 35 Notes v Input Variables Showing 1 2 C Select an entry J identification type Identification of the customer overrides session v Follow up States Showing 1 3 4 4 All A OK Existing Consumer Prompt PIN A Fail Error Handling Target Blacklisted Advice needed action a Expression 1 Assign To m Target Goto Application Registration Expression 2 Assign To Select a follow up state 7 Add Follow up Save Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Security AA amp Blacklist Descriptions Input Variables Perform additional verification based on the customer PIN and the identification value This is an extra security verification in addition to the MSISDN The PIN number was set by the customer during the signup process Also see the Login state that performs the same function We recommend to use this state instead of the Login state Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification v
30. Notes v Input Variables Showing 1 1 W CUST_BALANCE Source v Output Variables Showing 1 1 PRE_REMIT_BALANCE Destination v Follow up States Showing 1 2 7 OK Txn Authorise Transaction z A Fail Get Customer Balance I gt Select a follow up state ix Add Follow up Storing customer balance prior performing remittance The pre and post remittance balance will be sent to the customer after the transaction See scenario 1 below for details Fail follow up state will most likely occur due to non existence of the source variable This allows the application to retry in setting the source variable There are several mechanisms that session variable is set as described on the followings Session variable can be set in the Follow up States by using the bracket in the Expression field and specify the variable name in the Assign To field All return values from a state are set into the session variables so that they are accessible by the follow up states CAUTION setting an existing session variable will overwrite the value For example if a previous state returned a value in the session variable X and the follow up state set variable X the return value is lost Scenario 1 The Get Balance state will be called twice in the application pre transaction and post transaction The customer balance is returned by a Get Balance state and stored in the session variable called balanc
31. VAR_CURRENCY Currency of the selected PI VAR_SELECTED_KEY Variable name ofthe selected KEY VAR_SELECTED_VALUE Variable name ofthe selected VALUE v Follow up States Showing 1 2 7 OK it Sele ct a follow up state Fail Select a follow up state Brand Mobiliser Development Manual 107 Version 1 2 September 2011 Money Mobiliser State Customer Management Descriptions Add or modify the customers full name The full name is saved as the customer display name Also the full name text is split based on spaces to get a separate first middle and last name If the split results in only one entry it is used as the last name If the split results in more than three entries the third and the rest are set to the last name Input Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the
32. Var 6 Get Languages 0 Back 21 12 2010 Mobiliser Menu 11 22 46 POSER T p 123456 5 21 12 2010 smapp Mobiliser Tester 123456 4 Test Ident 447977257100 1 Get Cust Values 2 Set Cust Values 3 Wallet Fns 4 Money Fns 5 Misc Fns 6 11 18 45 Login Set alt test MSISDN 0 End 21 12 2010 Mobiliser Tester 1118 41 smapp Login 123456 1234 21 12 2010 Mobiliser Tester al P 11 18 36 smapp Login 123456 Mobiliser Tester Login Enter your credentials oe tie smapp Mobiliser Tester 123456 mobiliser Login 21 12 2010 11 18 31 21 12 2010 11 18 31 Timestamp Dir Msg menupage Startpage 123456 4 Startpage Welcome to Mobiliser Tester send mobiliser to continue menupage Startpage 123456 hello Figure 33 Application Simulator With Interaction One of the menu options is the Mobiliser Counter application as described in a previous section and is visualised in the figure below 36 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Mobiliser Counter vee Mi eae eee taal APPLICATION COMPOSER E E Wiel ea iets Application Actions v a MOBILISER MOBILISER SHOW COUNTER SOTO MENU COUNTER COUNTER STATE OPTIONS APPLICATION J M ay Mobili ver SMS To Applicati tart Applic Ul Figure 34 Mobiliser Counter Application Overview The main logic of the counter application is to use a state to increment a session variable acting as the counter display the value to the user then to eithe
33. entry x identification type 7 Identification ofthe customer overrides session v Output Variables Showing 1 4 NAME Customer name PASSPORT_ID Passport no LANGUAGE Index of language LANGUAGE _A2 Two digit language code v Follow up States Showing 1 2 OK Select a follow up state Fail Select a follow up state 96 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Money Mobiliser State Customer Management Check if customer exist and has PIN Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Follow up State OK Customer exists and h
34. from the blacklist Follow up State Fail Possible reasons are e Attempt to blacklist the customer failed e Web service internal error LJ Name New Mobiliser Set Blacklist Reason state 3o Notes v Input Variables Showing 1 4 O Selectanentry Identification type Identification of the customer overrides session BLACKLIST_REASON ID ofthe blacklist reason PIN The PIN from the MSISDN Y Follow up States Showing 1 2 OK Select a follow up state Nec A Fail Select a follow up state Select a follow up state v Add Follow up The default preconfigured blacklist reason IDs are listed in Appendix B1 Additional reasons may be added during customization Please check the customization specification document 86 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 Scenario 1 The most common usage of the Set Blacklist Reason state is when the retry of providing password or PIN exceeds the maximum allowable limit as shown below The blacklist can also be set by the Money Mobiliser platform Brand Mobiliser Development Manual Version 1 2 September 2011 87 Money Mobiliser State Security AA amp Blacklist Descriptions This state is used to block the customer Define the time for which the customer should be blocked If you wish to inform the customer of the block you can provide this information using the Contact Notification textbox pOL SA
35. in getting the transaction details and stored in the output variables Follow up State Fail Possible causes Fail to get the transaction details Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found Unexpected error 122 m Brand Mobiliser Development Manual Version 1 2 September 2011 Mobiliser Get Transaction Details State Input Variables Showing 1 3 Select an entry vy Identification type O IDENTIFICATION Identification ofthe customer overrides session TXN_ID Transactionld v Output Variables Showing 1 5 6 10 11 13 All TXN_AMOUNT Amount TXN_CURRENCY Currency TXN_AUTHCODE Authcode ERROR_CODE Error Code STATUS_CODE Status Code v Follow up States Showing 1 2 OK Get Transaction Detail OK Fail Get Transaction Detail FAILED Select a follow up state v Add Follow up Scenario 1 this state requires a transaction ID as an input The transaction ID is return by the Get Transactions state The customer needs to remember the number and send it back to use it in the Get Transaction Details state In the future the Get Transactions List using the menu list will be provided allowing the customer to select a transaction from the menu item without retyping the tran
36. instrument used for the payee This could be Stored Value Account Bank Account Credit Card or External Account Output Variables Transaction ID Internal system reference number that identifies the transaction Authorisation code This code identifies the transaction It is the customers reference to the transaction in the system and appears on the receipt The customer can use this code to track the transaction and request assistance from customer support if there are any problems Follow up State OK Send Money completed successfully Follow up State Fail Possible reasons e Missing Payer and or Payee Identifications e Unknown Web service error e Web service connection error Follow up State DYN Error Codes See Appendix B9 Money Error codes 136 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 LJ v Name Send Money state m v Input Variables Showing 1 5 6 10 11 13 All EUR Currency of transaction 193 Use Case ID Optional PIN for Bank Accounts or other Pls O O AMOUNT Amount O By mobile no v Payer Identification Type v Output Variables Showing 1 2 TXN_ID Transaction ID AUTHCODE Authorisation code v Follow up States Showing 1 2 OK Get Latest SVA Balance A Fail ERROR Send Money Select a follow up state v Add Follow up Usage Scenario 1 a typical send money flow with a two step transaction is shown bel
37. no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory PIN The PIN of the customer chosen during the registration Follow up State OK Successful login Follow up State Fail Possible reasons are e System Error Unexpected Internal Error Follow up State DYN 1010 System Error Invalid session ID 1121 Credential has expired 9935 System Error Unexpected Internal Error w v Name Mobiliser Login State R v Input Variables Showing 1 3 C By mobile no v Identification type Identification of the customer foverrides session PIN PIN ofthe customer vy Follow up States Showing 1 2 OK New Mobiliser Get Customer Information state v A Fail Mobiliser Login Fail Select a follow up state v Add Follow up Notes Use the Check Credential state instead of this Login state Usage Scenario 1 use to challeng
38. not unique 1098 Access to customer is not allowed for the current agent 1221 Agent object not found 88 m Brand Mobiliser Development Manual E Version 1 2 September 2011 LJ vy Name New Mobiliser Block Until state Tul Notes v Input Variables Showing 1 4 F Select an entry v Identification type Identification of the customer overrides session MINUTES Time to block customer in minutes Contact Notification v Follow up States Showing 1 2 T OK Select a follow up state A Fail Select a follow up state Select a follow up state v Add Follow up Scenario 1 this is used for temporary blocking of a customer See also Set Blacklist Reason state for blocking until released by customer supports Brand Mobiliser Development Manual aa Version 1 2 September 2011 Money Mobiliser State Security AA amp Blacklist Descriptions Delete the specified customer from the current customers network Note network is hierarchy relationship graph of customers The ID of the to be deleted customer needs to be provided Currently this state is not very usable unless the ID is available Additional state s will be added in the future release to retrieve the customer network list in the form on menu list The ID will then be available to this Delete Network Entry state Input Variables j Identification type The type of customer identification to use The choices a
39. of the customer is mandatory Attribute ID attribute id Attribute ID needs to be obtained from the configurations customization or specifications documents Customer ID customer ID Attribute value the variable name to store the retrieved attribute value The attribute is retrieved successfully and stored in the variable name specified in the Output variables Attribute Value field 1010 ATTRIBUTE Attribute not found 101 Security policies have not been defined for customer yet 1303 System error Session not found 1304 System error Session has timeout 1010 Customer not found 1011 Customer is not unique 1098 Access to customer is not allowed for the current agent 1221 Agent object not found Brand Mobiliser Development Manual Version 1 2 September 2011 v Name New Mobiliser Get Customer Attribute state Ta Notes v Input Variables Showing 1 3 Select an entry v Identification type Identification of the customer overrides session j W ATTRIBUTED Attribute ID v Output Variables Showing 1 2 CUSTOMER_ID CustomerID ATTRIBUTE_VALUE Attribute Value v Follow up States Showing 1 1 gA OK S Select a follow up state I Select a follow up state M Add Follow up Save See the Get Customer Information for other customers information See the Get Customer Address state for the customer main address See the
40. or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory List of Invoice types a list of invoice types this needs to be obtained from the Money Mobiliser setup Follow up State Fail Possible reasons are Web service internal error e Web service connection error Follow up State DYN where N is the number of item in the returned list NOTE if N 0 the output variables will not be populated U v Name New Mobiliser Get Invoice Configurations 20 Notes v Input Variables Showing 1 3 O Selectanenty Identification type Identification of the customer overrides session List of Invoice types Example 12 123 456 v Output Variables Showing 1 3 VAR_LIST_NAME Variable name for list VAR_NAME_FIRST_KEY First K
41. parameters are a states response to an action All output parameters are available as variables e Checkbox The output parameters checkbox will always be ticked because the output is always stored in a variable The checkbox is not editable e Entry field This is the session variable into which the output is stored The entry field is editable For a newly added state a default variable name is provided However the developer needs to ensure that the same variable name has not been used elsewhere in the application to avoid over riding the same session variable unintentionally e Description A short description of the output type 6 m Brand Mobiliser Development Manual E Version 1 2 September 2011 The figure below shows an example state that has a single output In this case the session variable AMOUNT_FORMATTED is assigned the output value of this state Y Output Variables Showing 1 1 AMOUNT FORMATTED The formatted amount Figure 7 Example State with Output Parameter 2 1 3 Transitions Transitions define which state follows the current state The above Keywords and Variables section describes how transition is determined by matching pattern of text with the keyword supplied by the user In some states such as Mobiliser and 3 party states there may also be a specific e OK or success transition e Fail or failure transition or e Dynamic transition based on a keyword match These transitions defin
42. payer This could be Stored Value Account Bank Account Credit Card or External Account Payee Identification Type The identification type of the payee This could be by mobile No by customer ID or by user name Payee Identification The identification of the payee Payee PI ID The identification of the payment instrument for the payee Payee PI class The class of the payment instrument used for the payee This could be Stored Value Account Bank Account Credit Card or External Account Output Variables i The fee for the payer This fee is debited to the payer The fee for the payee This fee is the commission paid to the agent for the Cash Out service The id of the pre Authorisation txn the ID generated for the pre Authorisation The amount for the payer the total amount charge to the payer including the actual remittance amount the fee and converted the payer currency The currency of the payer the currency used by the payer Follow up State OK Voucher remittance has been pre authorized with all the authorized information stored in the output variables Follow up State Fail Possible reasons e Unknown Web service error or Web service connection error Follow up State DYN Error Codes See Appendix B9 Money Error codes Brand Mobiliser Development Manual 141 Version 1 2 September 2011 New Mobiliser Txn Start V
43. receives back in clear text in the message logs This is a security feature to allow passwords and PINs to be restricted 5 Editor Closer Clicking on this icon will close the state editor popup window If you have pending changes that havent been saved you will be prompted to either save or discard these changes as shown in the figure below If you discard the changes you will continue with the close If you saved the changes you will have to repeat the close action You have unsaved changes to your state which you will lose if you continue Do you want to save or discard your changes Figure 18 Pending Changes Save Discard Message 6 State Type Notes Each state type has the ability to describe its function its required inputs and outputs and any follow up state transitions that are expected By clicking on the Drop Down Notes Brand Mobiliser Development Manual 5 Version 1 2 September 2011 10 11 12 24 icon you will see this text An example is shown in the figure below Clicking on the icon again will cause the text to be hidden LJ v Name Get agent information JE Notes Mobiliser Get Customer information Loads a customer and returns tems of user information If the Identification input is not set the current customer is used Use the following follow up states OK If everything is ok Dyn Mobiliser error code v Input Variables Showing 1 3 Figure 19 State Type Notes Drop Do
44. shown in the Application Composer but still exists in the system Detached portions of the application are never reachable by the customer through the application flow To re attach that portion into the application you can add a new state or add a transition that flows into a state in the detached portion Removing a Follow up Transition Removing a transition will permanently delete that transition but will not remove the follow up state that it was associated with To re attach the follow up state into the application add a new transition using the follow up selector 28 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Click on the remove follow up icon next to the follow up state to remove the transition as shown in the figure below w v Name New Send SMS state Bol Notes Message Reply with again to see this again 38 160 characters v Follow up States Showing 1 1 Target My First Application Expression again Assign To Remove link to follow up My First Application v Add Follow up Figure 28 Remove Follow Up Transition Brand Mobiliser Development Manual Version 1 2 September 2011 29 4 Example Application Brand Mobiliser offers a unique and highly personalised cashless way to manage financial services more efficiently It allows customers to conveniently redeem vouchers on any phone remit money domestically pay bills automatically manage their accounts remotely
45. the application or state is shown as an image on the canvas tagged with its name The canvas has gridlines displayed to show where a state may be located States are described in more detail in the next section The state icon shows e the name of this state instance centered on the icon e the type of the state in the bottom bar of the icon and e awatermark pattern to also help signify the type of the state Mobiliser Counter APPLICATION DETAILS APPLICATION COMPOSER A Application Actions i A MOBILISER MOBILISER SHOW COUNTER SOTO MENU COUNTER COUNTER STATE OPTIONS APPLICATION Start Application Money Mobiliser Go To Application Figure 9 Example Application Composer View 16 m Brand Mobiliser Development Manual E Version 1 2 September 2011 The transition between one state and the next is shown as a directional arrow between the two related states In more complex applications transition lines may overlap others The buttons specific to the Application Composer view are SAVE LAYOUT stores any changes made to the layout back to the database REVERT LAYOUT re loads the stored application layout Gridlines Allows the option to display all the grid lines a partial grid line or none at all Zoom Allows the option to zoom the Application Composer view panel both out and in so that applications with a large number of states can show the complete workflow on one page see example in figure belo
46. the state editor window to take up a large amount of space and go beyond the viewable area on the page Outputs Section This is an optional and works the same as the Inputs Section described above Variables Paging for Outputs Section There are separate paging options for the output variables and they work the same as the Paging Options for inputs described above Follow ups Section This area is displayed for most types of state but not all and allows the configuration change and test of follow up states It also allows the collapse of the follow up states section When this section is collapsed the Exit Nodes are shown on the follow up sections header as shown in the figure below m Brand Mobiliser Development Manual E Version 1 2 September 2011 gt Follow up States Select a follow up state v Add Follow up Figure 22 Collapsed Follow up States and Exit Nodes 13 Follow up Paging Paging through the follow up states works the same as the Inputs and Outputs paging except there are only three follow up states shown per page because of the amount of additional vertical space used by Follow up state Expression and Assign To fields 14 Exit Nodes An exit node identifies a link to another state that flows FROM this state Exit Nodes are click sensitive and if you click on it you will open the state editor for the state that this transition relates to Mouse over on an exit node will show the state name
47. to Event Application The keyword send by subscriber to initiate the interactive application The application may allow multiple keyword as configured in the Keyword tab The DYN enables custom flow based on the incoming keyword v Name Start Application State m v Follow up States Showing 1 1 Target Send SMS Welcome and Menu x Expression Assign To Select a follow up state A Ada Foiiow up Start Application with a single follow up state i e Send SMS state There must be at least one follow up state otherwise the application will do nothing and terminates Scenario 1 common implementation Scenario 2 Handling multiple Keywords using different flows START SEND SMS APPLICATION WELCOME AND STATE MENU START SEND SMS APPLICATION WELCOME AND Start Application Delete STATE MENU Start Application Send SMS INITIALIZE VARIABLE Delete 48 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Base State Used whenever text is to be sent to the mobile subscriber via SMS Example welcome message menu list or instructions Descriptions Input Variables Send the message and do one of the followings e lf there is at least one follow up state then pause the workflow to wait for response from the subscriber Otherwise terminate the application Message the text to be sent via SMS If the length of the text exceeds 160 characters the text is truncated and multip
48. transaction Use Case ID The Use Case ID identifies the type of transaction For a CashOut transaction the Use Case ID is 1005 Amount The amount of the transaction Payer Identification Type The identification type of the payer This can be either by mobile No by customer id or by user name Payer Identification The payer identification Normally this is retrieved through the mobile No so this field can be left blank Payer PI ID The payment instrument used by the payer is identified here Payer PI class The class of the payment instrument used by the payer This could be Stored Value Account Bank Account Credit Card or External Account Payee Identification Type The identification type of the payee This can be by mobile No by customer ID and by user name Payee Identification The identification of the payee Payee PI ID The identification of the payment instrument for the payee Payee PI class The class of the payment instrument used for the payee This could be Stored Value Account Bank Account Credit Card or External Account Output Variables The fee for the payer This fee is debited to the payer The fee for the payee This fee is the commission paid to the agent for the Cash Out service The name of the payee The name of the payee Follow up State OK Pre Authorization is successful and the information are stored in the output variables Follow up State Fail Possible reasons
49. v Add Follow up Figure 36 Show Counter State Detail If the user responds with the keyword again to the message sent from Show Counter the application will loop Any other input will cause this application to end and revert to the menu The interactions to get to the counter application are shown in the figure below On this first entry to the application the counter value is displayed as 1 alongside the text to indicate the expected response Refresh message log i i Client Timestamp Message Receiver MSISDN Dir Msg 21 12 2010 Mobiliser Menu Misc cae ints Sannin 11 44 21 smapp Fineons 123456 4 1 Send back to continue again to re run 21 12 2010 Mobiliser Menu Misc i 11 44 20 SmaPP Functions 123458 4 21 12 2010 smapp Mobiliser Menu Top 123456 Test Ident 447977257100 1 Check Identification 2 Check Credential 3 Change Credential 4 Counter 11 44 17 5 Copy Var 6 Get Languages 0 Back 21 12 2010 11 4417 smapp Mobiliser Menu Top 123456 5 21 12 2010 i Test Ident 447977257100 1 Get Cust Values 2 Set Cust Values 3 Wallet Fns 4 Money Fns 5 Misc 11 44 12 smapp Mobiliser Tester Login 123456 4 Ens 6 Set alt test MSISDN 0 End rer 0 smapp Mobiliser Tester Login 123456 4 1234 21 12 2010 ai g E 11 44 08 smapp Mobiliser Tester Login 123456 4 Mobiliser Tester Login Enter your credentials i JEA 0 smapp Mobiliser Tester Login 123456 lt amp mobiliser 21 12 2010 er _ i Bene 11 44 03 menupa
50. very sophisticated so the list needs to be presented to the customer for manual selection as shown below Name Send SMS Issuers Bo E Note GET INVOICE CHECK LIST SIZE NO INVOICE 2 ISSUERS Message Select an issuer VAR_LIST_NAME Morey Mobiliser Jariable Send SMS 33 160 characters Follow up States Showing 1 1 Target Get Invoices x Expression Assign To ID_INVOICE i Select a follow up state BA Add Follow up Save v Input Variables Showing 1 4 Select an entry identification type Identification of the customer overrides session Status Filter one number only Example 42 ID_INVOICE Variable name for the ID invoice ID gt Output Variables Y Follow up States Showing 1 1 Fail Select a follow up state r Select a follow up state M Add Follow up Save 126 Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Customer Management Name Get Invoice Configuration List Descriptions Note the state name is a bit misleading The actual functionality is to compile the list of Issuers from the current customers invoices In the future this state will be replaced with a more sophisticated menu list similar to the Get Wallet state Input Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id
51. you wish to export a group of applications together maitaining links and dependencies between applications then use the Grouped Export feature as described below 42 m Brand Mobiliser Development Manual E Version 1 2 September 2011 6 2 Export a Group of Applications To export a series of application you must use the Assets page to select which applications are to be included then use the Group Export Applications button to export all the applications into a single export file The example screen shot below shows a number of applications that have been selected but using the checkbox next to the application name On clicking the Group Export Applications button an export file will be created and downloaded containing the definitions of each of selected applications Assets Create Interactive Application Create Event Application Create Asset Activate Applications Display Interactive Applications Event Applications Enter application name Search gt Advanced Showing 21 27 27 Total Assets 4 1 gt Assets per Page 20 Select Name Type Assigned to Event Schedule Actions Mobiliser SUBFLOW Select Interactive es Start Sep 11 2010 18 10 BST ACTIVE Currency End Sep 11 2012 18 10 BST Acione 7 Sample Called Application Interactive Start Jul 5 2011 12 45 BST Active End Jul 6 2012 12 45 BST Actions Sample Calling Application Interactive es Start Jul 5 2011 12 45 BST A
52. 10 44 08 12 2010 44 08 12 2010 44 03 12 2010 44 03 smapp MobiliserMenu Top 123456 4 TTFN smapp Mobiliser Menu Top 123456 0 Test Ident 447977257100 1 Get Cust Values 2 Set Cust Values 3 Wallet Fns 4 Money Fns 5 Misc 123456 Fns 6 Set alt test MSISDN 0 End 123456 0 Test Ident 447977257100 1 Check Identification 2 Check Credential 3 Change Credential 4 Counter SmaRp Mobiliser Countar 123456 5 Copy Var 6 Get Languages 0 Back smapp Mobiliser Counter 123456 back smapp Mobiliser Counter 123456 4 2 Send back to continue again to re run smapp Mobiliser Counter 123456 again 123456 4 1Send back to continue again to re run 123456 4 smapp Mobiliser Menu Top 123456 5 Test Ident 447977257100 1 Get Cust Values 2 Set Cust Values 3 Wallet Fns 4 Money Fns 5 Misc smapp Mobiliser Tester Login 123456 lt gt Fns 6 Set alt test MSISDN 0 End smapp Mobiliser Tester Login 123456 1234 smapp Mobiliser Tester Login 123456 4 Mobiliser Tester Login Enter your credentials smapp Mobiliser Tester Login 123456 mobiliser menupage Startpage 123456 amp Startpage Welcome to Mobiliser Tester send mobiliser to continue menupage Startpage 123456 hello Figure 39 Mobiliser Counter Simulation 3 Brand Mobiliser Development Manual Version 1 2 September 2011 39 Note This sample simulation shows the testing of an application through a menu system which is
53. 11 e Changes to input variables e Changes to output variables e Changes to follow up state Expression and Assign To values 3 2 4 Removing States and Transitions To change any state configuration you click on the state in the layout view to highlight that state and open the state editor popup Applications may have states and transitions removed from them It is important to understand the different implications of removing either a state or a transition and the resulting changes made to application Removing a State Removing a state will permanently delete that state and any transitions that were associated with it To remove a State click on the area of the state icon in the layout view that is marked as Delete You are prompted to ensure you know the implications of deleting the state and can continue or cancel the delete action My First Application APPLICATION DETAILS APPLICATION COMPOSER iJ 8 MY FIRST NEw SEND SMS APPLICATION STATE alias ax Deleting the state will permanently remove it and any transitions to and from it Are you sure you want to the delete the state Figure 27 Delete State and Confirmation States that transitioned INTO the deleted state will have effected transitions Note Deleting a state that had its own follow up transitions may also then detach that portion of the application from the application flow itself A portion of the application that is detached is not
54. 21 Agent object not found 1301 System error Maximum number of allowed sessions reached 1303 System error Session not found 1304 System error Session has timeout 9935 System Error Unexpected Internal Error Brand Mobiliser Development Manual Version 1 2 September 2011 83 Usage s4 oi Name Mobiliser Change Credential State JE Notes Input Variables Showing 1 5 Select an entry vy Identification type IDENTIFICATION Identification of the customer overrides session Credentialisa PIN Credential Type OLD_CRED The customer s old credential value NEVWW_CRED The customer s new credential value vy Follow up States Showing 1 3 QO OK Change Credential OK Fail Change Credential FAIL Target Change Credential FAIL Expression gt Assign To Select a follow up state v Add Follow up Scenario 1 change credential is typically started by checking the exiting credential followed by prompting the new credential and the re prompt for the credential again for verification prior to submitting to the Change Credential state as shown below APPLICATION CONFIRMATION CALL CHECK CREDENTIAL Application Ca Send SMS The Application Call Check Credential is calling the sub application kind of subroutine to promote reusability See the base states Application Call and Application Call Return for description on how t
55. 5 29C a e u T Proce r name Cars TOE Process version ld i gt lt states gt lt state 10 1595 Brand Mobiliser Development Manual Version 1 2 September 2011 smappStateTypeName Send SMS encrypted false 41 mtChargingitemsFkId 0 moChargingItemsFkId 0 chargingItemsFkId 0 smappAuctionTypesId 0 subscribeAFriend false forwardMessageReceiversId 0 sendiIntermediateResult false last 0 mmsSmilMessagesId 0 smappStateTypesId 1901 name Wrong account PIN versionId 1 gt lt smappStateLang smsText The account PIN you entered was not correct Please re encter your PIN for your account SENDER ACCOUNT NUMBER Or press 0 to recurn te main menu version d 1 gt lt language unicode false default2 true description englisch name EN gt lt smappStateLang gt lt smappStateAttribute key gridposx versionId 1 gt lt intValue gt 13 lt intValue gt lt smappStateAttribute gt lt smappStateAttribute key gridposy versionId 1 gt lt intValue gt 1l lt intValue gt lt smappStateAttribute gt lt Stakes Note This file is not expected to be manually edited or created Note If the application you are exporting contains references to other applications through the Goto Application or Application Call states then details of the application being called will be included in the export however the link to the other application is not guaranteed to be re established on import If
56. A set of sample applications that use and manipulate session variables and the Goto Application and Application Call states Reports Subscriber Report Traffic Report p i i fa Figure 44 Quick Start Templates List template you wish to import Brand Mobiliser Development Manual Version 1 2 September 2011 45 Create From Quick Start Template Create new application s from a template Choose Template Sample Applications Create from template was successful Application names are Sample Called Application Sample Calling Application Sample Goto Application Sample Using Variables View Application Details Figure 45 Quick Start Templates List To define a new Quick Start Template refer to the Brand Mobiliser State Developers Guide 46 m Brand Mobiliser Development Manual E Version 1 2 September 2011 A Appendix States Catalog This appendix section lists and describes the states that are available by default in Brand Mobiliser in the following order base states subscriber states and money states They are presented in the catalog format so that they can be printed out and used as reference cards Brand Mobiliser Development Manual Version 1 2 September 2011 47 Base State Initial entry point to Application This state is created automatically and cannot be deleted me e omae tire Follow up State DYN Applicable to Interactive Application Not Applicable
57. ANGUAGE Language COUNTRY Country DISPLAY_NAME Display Name Y Follow up States Showing 1 2 A OK Set Identification From Customer Info A Fail Select a follow up state This state does not return all the customer information See the Get Customer Address state for the customer main address See the Get Customer Attributes for a specific customer attribute See the Get Customer Product state for the customer product ID Brand Mobiliser Development Manual 99 Version 1 2 September 2011 Money Mobiliser State Customer Management Get the customer main address Input Variables Output Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by us
58. An IVY com pany PRODUCT DOCUMENTATION DELE i AWW www sybase com Contents 1t SNE CIM ECON ea e uwaanosaatecnetaa Tencwssabassara A E 1 LI PROTO REI COS oes dan besausarcen E E cas viet isarpan E A eae succes aioe TE A AT wea T E E 1 2 States ama ADpliGatiOms ciiescd lacs sesicce A nee Hameo eed ace iakea ee 2 Ae Sd MCA aaa ne eee a OREO ee a ee a N 2 ZZ BIES ESen cece she nas uae sma ties neta late acts gas nee svac cies sce wee eeu necoigta gaa awe O 8 ZB SUDSCHIOSK SUA LCS 5 2ioGyiesccncs a eaeieg Ga nina ou buee sais ba aenraaiecle A E 8 Dl MODS Cle Stak e e a ae a a ce bata cas N 9 s E EE A EE P E A AA A A 14 3 Developing with the Application Composer cccccccsssececcesececceecceeesececsuececeuececseunceesausecetseneees 16 A Sha COs OU a T E E E O O 16 Bid SECETOS eaoneenea teagan es eecueaieeouenaomaees 22 4 SEMANTIC AD DIC ALO Meas stslret sadahecorseneseGraaiac gacaceewsssatancaseeausse sresuacuan ano sveesaguaag nec seeac orapans sowanaeeaua tans coesanies 30 ATE CASIO UE PROCESS sates cotces Secmery st coronene N O a a atten olan ee 30 AS ANOT ON Gee eee ne ne ee re a ae ne ee eee ee en eee 32 AS DAC bay OU Gsieraseckecees fosscuct eet a A cawaciahtltane hisses cla cin she woctad hss int Ueulh en anaes an abeamae 33 AA 2858 ol Glan a det eee ee ee ee ee 34 5 HOW tO Test APpIIGAtONS 4cladlaeiiadii th ccd toes ede die alee 35 5 1 Using the Application Sim
59. Credentials e One Customer can have multiple Addresses e One Customer can have multiple Privileges direct are assigned through Roles e One Customer can have a financial Limit 10 m Brand Mobiliser Development Manual Version 1 2 September 2011 e One Customer can have multiple Wallet Entries e Each Wallet Entry links a Customer with a Payment Instrument e ACustomer can use a Payment Instrument if it is linked into her his Wallet e There can be a financial Limit on a Wallet Entry e Each Payment Instrument has one owner Customer e There can be a financial Limit on a Payment Instrument A Payment Instrument can be of type SVA Voucher Bank Account Credit Debit Card External Account generic 2 4 3 Consumer Network Models Money Mobiliser supports consumer networking using the Network model Consumer Network is the network of related consumers using hierarchy relationships A consumer is related to other consumer either as a Parent or a Child The relationship can also be categorized by a type i e network type of for example Friends and Family 2 4 4 Invoice Models To support bill payment capabilities Money Mobiliser uses the Invoice models A consumer can be issued invoices that can be retrieved using for example the Get Invoice state The followings are the characteristics of Invoice e Invoice has a Status that is configurable with a unique name e Invoice can have additional Attribut
60. EY of list VAR_NAME_FIRST_VALL First VALUE oflist Y Follow up States Showing 1 1 A Fail Select a follow up state v Select a follow up state v Add Follow up Brand Mobiliser Development Manual Version 1 2 September 2011 127 128 Scenario 1 this state is typically used prior to the Get Invoices state in order to obtain the issuers ID as shown below as Get Invoice Issuers For more detailed description please refer to the usage of Get Invoices state scenarios 1 and 2 GET INVOICE CHECK LIST SIZE NO INVOICE ISSUERS Money Mobiliser Variable Send SMS GET INVOICES Send SMS Money Mobiliser Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Customer Management Descriptions Set the wallets Primary Payment Instrument of the current customer and also set the same primary PI to be used Primary debit and or Primary Credit Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value
61. For example If there are circular references which are common in menu based systems the application being imported will still be imported but a manual process of re linking applications is required before the application can be used For instances where a system is comprised of a number of dependent applications it is recommended to use the Group Export Applications feature as described above to export all the dependent applications into one export file so that they can be imported together When they are imported from a single export file all inter dependent references in states in these applications will be maintained after the import therefore not requiring any manual intervention to re link the applications Upload Application From Existing File Upload from an Application File You can enter new application name otherwise the existing name will be used Application Name Choose File PEIER E Upload Import Success Application names are Sample Called Application Sample Calling Application Sample Goto Application View Application Details Figure 43 Import a Group of Applications 6 4 Quick Start Templates Brand Mobiliser also provides the ability to create new applications from a pre defined quick start template The template is defined by the system configuration and effectively allows the import of a new system of applications by name 44 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Br
62. ID Attribute ID ATTRIBUTE_VALUE Attribute Value Y Follow up States Showing 1 1 A OK Select a follow up state k Select a follow up state v Add Follow up me S Brand Mobiliser Development Manual 109 Version 1 2 September 2011 Money Mobiliser State Customer Management Name Set Language Session amp Customer Input Variables Set the selected language of the customer in the Brand Mobiliser session context so that it is used for the rest of the session and update the Customer database Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory The selected Language The language to
63. K transition will be coded Possible causes Customer Product not found Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found Product ID the customer product id that is exactly the same as the output variable Product ID eS vy Name New Mobiliser Get Customer Product state jw M Notes v Input Variables Showing 1 2 Select an entry identification type m Identification of the customer overrides session v Output Variables Showing 1 1 CONSUMER_PRODUCT Product ID v Follow up States Showing 1 1 A Fail Select a follow up state x Select a follow up state Add Follow up See the Get Customer Information for other customers information See the Get Customer Address state for the customer main address See the Get Customer Attributes for a specific customer attribute Brand Mobiliser Development Manual Version 1 2 September 2011 C Brand Mobiliser Development Manual 105 Version 1 2 September 2011 Money Mobiliser State Customer Management Name Get Currency Menu Depracated Not usable in the current form Descriptions Send the list of currency based on hard coded business login to the customer as a menu list The USD US dollar is always included as a currenc
64. Language Session amp Customer Set Customer Attribute Get PI Balance Get SVA Balance Get Transactions Get Transaction Details Get Wallet Menu Get Invoices List Get Invoice Configuration List Set Primary PI Find Remittance Voucher Txn Authorize Transaction Format Amount Currency Txn Pre Authorize Send Money Txn Send Money Txn Change Fee Txn Pay Invoice Txn Start Voucher Remittance Txn Continue Voucher Remittance Txn Pickup Voucher 2 5 3 Party States Additional customised states are developed on an as needed basis to extend the functionality of Brand Mobiliser to implement client specific requirements Customised components are typically developed by e Sybase 365 to implement client specific requirements e Third parties as plug in applications to meet specific client requirements e g storing license plate data for an m Parking application 14 m Brand Mobiliser Development Manual E Version 1 2 September 2011 To integrate new custom states requires Java development to a provided API and customisation of the product to include new states package This customisation is described in a separate document called Brand Mobiliser State Developers Guide Brand Mobiliser Development Manual Version 1 2 September 2011 15 3 Developing with the Application Composer The key to effective development of Brand Mobiliser applications is the easy to use visualisation of t
65. N of the customer Although there is no internal customer list held in Brand Mobiliser it is expected the back end systems such as Money Mobiliser will do that validation of customer through the Mobiliser or other 3 party states This Cash Out process assumes we already have a validated customer session on entry to this application After successful customer validation it is normal to offer a series of menus through SMS where the user can choose from the options available to them In this case Cash Out would be one menu option related to the mobile financial services that may be offered to them Again this Cash Out process assumes we enter the process from an option on a menu and if there are problems or if the user wants to finish the process or at the end after a successful transaction we will revert back to the menu applications 30 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Brand Mobiliser enables you to configure the workflow of any application like the Cash Out process by creating a sequence of successive states You can create these states with just a few clicks and without any knowledge of programming However a knowledge of both the business process potential outcomes and how the states work to provide their individual functions is required The Cash Out process is a series of simple steps 1 2 3 4 5 6 7 Customer chooses an account to cash out from Enter the agent code who the custom
66. NARE Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Time to block customer in minutes The term for which the customer should be blocked in minutes Contact Notification The text that is sent to the customer Follow up State OK Successfully block the customer Follow up State Fail Possible reasons are e Unsuccessfully block the customer or adding note for the customer e Web service internal error Follow up State DYN 101 Security policies have not been defined for customer yet 1303 System error Session not found 1304 System error Session has timeout 1010 Customer not found 1011 Customer is
67. TE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory PIN The PIN of the customer chosen during the registration Customer is registered in the system and status is active so its OK to proceed with authorized actions Possible reasons are e System Error Unexpected Internal Error customer is not registered in the system customer is registered in the system but blacklisted LJ v Name Check Identification 30 Hotes v Input Variables Showing 1 2 O Selectanentry Identification type Identification of the customer overrides session v Follow up States Showing 1 3 4 4 All OK Customer Found Prompt PIN A Fail Service Unavailable Target Customer Not Found Expression 1 Assign To Select a follow up state v Add Follow up Brand Mobiliser Development Manual Version 1 2 September 2011 77 78 shown below CHECK EXISTING IDENTIFICATION CONSUMER PROMPT PIN BLACKLISTED ADVICE NEEDED ACTION GOTO APPLICATION REGISTRATION Scenario 1 Registration should always be preceded by checking the customer status as vy
68. TUS BOL_IS_ACTIVE 1211 ERROR AUTHORISATION FAILED Indicates that the agent customer lacks a privilege required for the current process 1221 WARN INVALID ACCESS Indicates that the agent attempted to execute an action he is basically allowed to do but ee with foreign data e g acknowledging a transaction of another merchant 1301 INFO SESSION ACTIVE WARN Indicates that a login failed because the customer has still an active session this ee prevents logging in multiple times with just one customer WARN INFO INFO INFO FATAL FATAL FATAL FATAL 2032 FATAL AMOUNT_EXCEEDS_ CAPTURE Indicates that the captureCancel amount exceeds the captured amount 2201 INFO UNKNOWN TARGET Indicates that the target customer is unknown 2202 INFO INVALID TARGET Indicates that the target customer is invalid i e not allowed able to participate in the TRANSACTION_EXPIRED The transaction was pending in initial state too long and invalidated automatically operation WARN INFO WARN INFO INFO INFO ERROR INFO FATAL WARN 150 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 2405 INFO NO COMM WITH MSG GW Send error indicates that the Notification Services are not going to send the specified message for whatever reason 2533 WARN PAYEE PAYER IDENTICAL Indicates that the transaction cannot be executed because payee and payer are identical 2534 WARN AMOUNT DIFFERS Indicates that the sub transactions amount
69. To DRIVER_LIC Fail Select a follow up state x Select a follow up state M Add Follow up Save Select a follow up state M Add Follow up Scenario 2 same problem can be modeled slightly differently as follow IDENTITY TYPES IDENTITY SET IDENTITY MENU NUMBER DRIVER LICENSE v Name Identity Types Menu a Notes Message Choose Identification types 1 DriveLicense 2 Passport v Input Variables Showing 1 2 56 160 characters 7 TYPE Identity Type Follow up States Showing 1 2 a Ried Identity Number DRIVER_LIC Identification Expression 1 Assign To TYPE 7 eo Showing 4 2 OK ara identity Number Success Proceed Expression Assign To TYPE Fail Selecta follow up state ae Select a follow up state M Add Follow up ave Select a follow up state M Add Follow up Se Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Security AA amp Blacklist Input Variables Change the credential of a customer Two types of credential are supported PIN or Password The customer credential is validated prior to changing the credential Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by
70. ables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Output Variables Name customer name Passport No password number of the customer if set Index of Language the ID of the language Two digit language code the two digits Follow up State OK Success in getting the customer information Follow up State Fail Possible reasons e Customer information cannot be retrieved e Web service internal Follow up State DYN Customer pre registered Customer not found Customer Blacklisted SE v Name New Mobiliser Check Customer state 8o Notes v input Variables Showing 1 2 Select an
71. ain specific purposes such as for CRM ERP etc However it is perfectly fine to use the storage as the system of record for small scale implementations and especially with regular and well housekeeping The Subscriber states include e Get Subscriber get a subscriber based on the MSISDN and all the corresponding attributes from the selected subscriber set e Add Subscriber add a subscriber and the provided attributes to the selected subscriber set e Update Subscriber update the subscriber attributes to the selected subscriber set and based on the MSISDN 8 m Brand Mobiliser Development Manual E Version 1 2 September 2011 e Process Subscriber process the selected subscriber set This state can be used in the event application only because it relies on the processing engine callback mechanism that is currently available to event application only These states are described in detail in the section Appendix States Catalog 2 4 Mobiliser States The Mobiliser States are domain specific states that consume the web services from the Money Mobiliser platform Typically the Brand Mobiliser applications provide the user interaction with the mobile subscriber to gather necessary information that will be sent to the web services or provide the business orchestration and integration layer 2 4 1 Money Mobiliser Overview The Money Mobiliser platform provides functionalities such as person to person money transfer top
72. al E Version 1 2 September 2011 LJ v Name New Mobiliser Delete Network Entry state BO Notes v Input Variables oO Select an entry NETWORK_ENTRY_ID v Follow up States Showing 1 3 identification type Identification of the customer overrides session The ID of the network entry to delete Showing 1 2 OK Select a follow up state A Fail Select a follow up state Brand Mobiliser Development Manual Version 1 2 September 2011 91 Money Mobiliser State System Management Descriptions Get a list of available languages supported by the system Also see the more advanced Get Language Menu for automatic sending of the language list to the customer as a menu list and facilitating the menu list paging interaction and proceed to the follow up states after the customer selects a Language from the menu list NOTE need additional Brand Mobiliser setup to be able to use this state See the notes below for how to setup the languages in the Brand Mobiliser system Input Variables p Identification type Not used Identification of the customer Not used Output Variables List of Language list of languages in the following format 1 englisch 2 B Indonesia 3 B M Follow up State OK Successfully retrieve the list of languages Follow up State Fail Possible reasons are e Web service internal error WU v Name New Mobil
73. alue If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Credential Type Currently not supported Only PIN credential is supported Credential The PIN credential value of the customer chosen during the registration Follow up State OK Valid credential Follow up State Fail Follow up State DYN Possible reasons are e System Error Unexpected Internal Error 101 Security policies have not been defined for customer yet 1301 System error Maximum number of allowed sessions reached 9935 System Error Unexpected Internal Error LJ v Name Check MPIN Credential Bol Notes v Input Variables Showing 1 4 C By mobile no v Identification type Identification of the customer overrides session Cl CredentialisaPIN v Credential Type PIN The customer s credential value v Follow up States Showing 1 3 4 4 All A OK Send Money state Fail ERROR Check MPIN Target Wrong MPIN Try again Expression 1113 Assign To Select a follow up state v Add Follow up Brand Mobiliser
74. amp Blacklist Descriptions Blacklist the current customer and provide the blacklist reason See also the Block Until state for temporary blocking of customer Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory ID of the blacklist reason The ID of the blacklist reason The default preconfigured IDs are listed in Appendix B1 Additional reasons may be added during customization Please check the customization specification document PIN from the MSISDN Not used Follow up State OK Customer has been blacklisted with the given reason Use the Customer Support Tool to remove customer
75. and Mobiliser contains a number of sample Quick Start Templates to demonstrate behaviour of the standard states and a basic Money Mobiliser test system These templates are shown on the Dashboard page on the right hand side of the page as shown below Schedule Start Encl Start Encl Start Encl Start Encl Start Encl Start Encl Start Encl Start Encl Start Encl Start Encl tive Application Clicking on any of these template names will take you to the Add Asset page where you can choose which Sep 12 2010 00 00 BST Sep 14 2012 00 00 BST Sep 12 2010 00 00 BST Sep 124 2012 00 00 BST Sep 12 2010 00 00 BST Sep 12 2012 00 00 BST Sep 12 2010 00 00 BST Sep 124 2012 00 00 BST Sep 12 2010 00 00 BST Sep 14 2012 00 00 BST Sep 12 2010 00 00 BST Sep 14 2012 00 00 BST Sep 12 2010 00 00 BST Sep 14 2012 00 00 BST Sep 14 2010 00 00 BST Sep 12 2012 00 00 BST Jul 27 2011 15 45 BST Jul 28 2012 15 45 BST Jul 20 2011 11 50 BST Aug 21 2011 11 50 BST Create Event Application Status Actions Actions Actions Actions Actions Actions Actions Actions Actions Activate Applications Workspace Short Long Codes 123456 Default Quick Start Templates MONEY MOBILISER TEST SYSTEM A system of applications that can be Used to test the standard functions and interface between Brand Mobiliser and Money Mobiliser SAMPLE APPLICATIONS
76. and enjoy financial benefits and other incentives as reward for their continued usage An example of one such financial service would be a Cash Out service This service is provided through a specialised mBanking and mPayment service that enables mobile subscribers to pay bills or services through any mobile phone The Cash Out service transfers money from the customers Money Mobiliser account to a Money Mobiliser representatives account The Money Mobiliser representative then pays this money as cash to the customer 4 1 Cash Out Process The Cash Out process is similar to many financial oriented processes that can be implemented easily using SMS or in USSD a kind of session based SMS Brand Mobiliser manages a unique user session throughout the process that maintains the context of the conversation the user is having with the application This Cash Out process would be one sub process provided through a number of interactive applications The applications are linked by either Goto Application states where the flow of control moves to the referenced interactive application or a Mobiliser Method Call state where the flow of control moves temporarily to the referenced interactive application before returning back to the application that called it A complete mobile service is a formed from a number of interactive applications that are normally fronted by a PIN or password entry stage so that we can somehow identify or validate the MSISD
77. anied by a short description of their functionality under Notes In general most states can be used by either application types However there are few states that are available to specific application types only because they relies on mechanisms that work for the application types For example the Process Subscriber state can be used for the event application only because it relies on the built in callback mechanism provided by the processing engine to the event type application only the Application Call and Application Call Return states can be used for the interactive application only because it is currently not supporting the callback mechanism The follow up selector filters out the states that are not intended for the application type 2 1 State Machine A state is an element of a system referred to as a state machine A state machine defines the flow of processes in an application for runtime execution In development the process flow is composed visually using the Application Composer When the application is activated the process flow is converted to the state machine An application usually has many states and can include different types of state A state usually has a previous state and a following state unless it is the initial state or the final state There can only be one initial state but many final states are possible depending on the interaction with the user The figure below depicts an initial state This i
78. arge fees to the customer for non financial transaction e g request account balance etc The fees to be charged is based on the pre configured Use Case IDs that are implemented on the Money Mobiliser Input Variables p Use Case ID The ID of the use case in which the fee is defined Currency The currency of the transaction Paymentinstrument ID Identifies the payment instrument that has the fee charged to it Output Variables Transaction ID The ID of the transaction Follow up State OK Fee charge transaction is successful The transactional ID is stored in the output variable Follow up State DYN Error Codes See Appendix B9 Money Error codes LJ Name New Mobiliser Txn Charge Fee state 8o Notes Input Variables Showing 1 3 USE_CASE_ID Use Case ID CURRENCY Currency Paymentinstrument ID v Output Variables Showing 1 1 TXN_ID Transaction ID v Follow up States Showing 1 1 g OK Select a follow up state v Select a follow up state v Add Follow up Scenario 1 a simple mechanism to charge for non transactional service such as balance or transaction history can be done using the Charge Fee state as shown below The fee structure is in the specified Use Case ID that is configured and implemented by Money Mobiliser for example 160 Usage NOTIFY FEE TO CHARGE FEE TO GET SVA BE CHARGED VIEW BALANCE BALANCE Send SMS Money Mobiliser 138 m Brand Mobiliser Dev
79. arget wallet Menu no entries Expression 0 Assign To Select a follow up state v Add Follow up Usage Scenario 1 a typical and minimal required implementation of this state is as shown below It is essential to implement the follow up states for both DYN 0 and 1 i e customer with zero and one PI because the menu list will be skipped in these two cases and immediately transition to the follow up state Otherwise the application will just terminate 118 m Brand Mobiliser Development Manual Version 1 2 September 2011 MOBILISER GET SAVE SELECTED WALLET MENU ERROR BYE NO PI SETUP SINGLE PI SAVE DEFAULT U v Name Mobiliser Get Wallet Menu Tj E Notes Message Wallet Menu E 12 160 characters gt Input Variables gt Output Variables v Follow up States Showing 1 3 4 4 All A OK Save Selected PI IF Fail ERROR Bye Target No PI Setup Expression 0 Assign To Target Single PI Save Default a Expression BH i Assign To i ESS Select a follow up state E ddFolowup save Scenario 2 show how to use the filter for the list of PI types and List of PI class For example transfer from PI to another PI When showing the menu list for the to PI need to filter the from PI to prevent transfer to the same PI Brand Mobiliser Development Manual Version 1 2 September 2011 119 Money Mobiliser State Customer Management Descriptions Re
80. ario 1 above a pickup code is generated The pickup code can be shown to the sender but behind the scene money mobiliser will send a notification message with the pickup code to the voucher receiver The receiver can redeem the voucher using the pickup voucher flow see Pickup Voucher state Usage Scenario 1 Send SMS Brand Mobiliser Development Manual Version 1 2 September 2011 Error Codes See Appendix B9 Money Error codes 143 Money Mobiliser State Transaction Service Descriptions invokes a Pickup Voucher transaction with the pickup code provided If the Payer MSISDN is not set the current user is used Input Variables The pickup code for the Voucher Pickup code Currency of transaction Currency code Use Case ID The use case of the transaction Amount Associated amount for the voucher Payer PI ID ID of Payer Processing Instrument Optional Transaction Text Text to describe the voucher transaction Output Variables j Transaction ID Unique ID for the transaction Authorization code Code for authorization Follow up State OK Pickup voucher transaction is successful with the transaction ID and authorization code stored in the output variables Follow up State Fail Possible reasons Unknown Web service error or Web service connection error Follow up State DYN Error Codes See Appendix B9 Money Error codes Input Variables Showing 1
81. as PIN Follow up State Fail Possible reasons e Customer does not exists or does not have PIN e Web service internal vy Name New Mobiliser Customer Has PIN state o EE Notes v Input Variables Showing 1 2 Select an entry identification type Identification of the customer overrides session Select a follow up state x Add Follow up Save Brand Mobiliser Development Manual 97 Version 1 2 September 2011 Money Mobiliser State Customer Management Name Get Customer Information Get customer information Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory
82. associated with it 15 Follow up Selector All states except the Go To Application state allow adding a follow up state All possible follow up states are available from this selector 16 State Actions The available actions for a state are shown here normally Add Follow up and Save The Save button is only enabled when there are changes that have been made to the state configuration 3 2 2 Adding States After creation of a new application there will always be the Start Application as the initial state New states are always added from the state editor of existing states therefore the initial state acts as the seed point of the application The figure below shows the Application Composer view for a new application after the My First Application state has been clicked and hence highlighted and the state editor has been opened My First Application APPLICATION DETAILS Kevworns APPLICATION COMPOSER APPLICATION EDITOR Application Actions bf SAVELAYOUT REVERTLAYOUT I Gridlines Al v 9 Zoom 100 A v Name My First Application JE Notes MY FIRST APPLICATION Select a follow up state v Add Follow up Start Application Lt Figure 23 Start Application State This state allows for two main actions identified by the icons on the state Remove this state Note The delete icon will appear once the state is selected by clicking on it The delete icon is not shown in t
83. ate is commonly used following the main or sub menu to better componentized the applications See Usage below Input Variables Application Select from a dropdown list showing all the available in service applications in the workspace An in service application is the one that has been activated and the start date is before the current date LJ Follow up State DYN v Name Goto Application m W Notes Application Pay Parking Can only go to the application within the same workspace There is limitation when used in event application and with the Process Subscriber state because this state discontinues the loop back mechanism provided by the engine The limitation is the Process Subscriber only processes one subscriber Usage Scenario common implementation of Menu and Goto Applications SEND SMS OPTION 1 GOTO WELCOME AND BANKING APP MENU Send SMS OPTION 2 GOTO PAYMENT OPTION 3 GOTO REMITTANCE 60 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Base State Descriptions Like the Goto Application this state also accesses a new application However in this case the user does not completely leave the current state flow The Application Call enables you to access another application and use it as a sub routine Input Variables Application Select from a dropdown list showing all the available in service applications in the workspace An in service appli
84. back to the application The matching of patterns to the supplied keyword is based on regular expressions Although regular expressions can be sometimes difficult to interpret they provide for a great amount of flexibility in matching patterns Name Enter agent code Message Please enter the 6 digit agent code of the agent you like to do the cash out transaction with PEET characters Follow up States Showing 1 2 Target Goto application main menu Expression Assign To Target Validate agent code format Expression i Assign To Select a follow up state z Figure 2 Example State with Keywords Variables and Transitions 1 See both http java sun com j2se 1 5 0 docs api java util regex Pattern html and Brand Mobiliser User Manual C Appendix Regular Expressions Brand Mobiliser Development Manual Version 1 2 September 2011 Note Brand Mobiliser version 1 1 introduces a regular expression tester called Keyword Tester which offers the ability to test your regular expressions during the development of the application A keyword can consist of any combination of characters Optionally the keyword input to the state may be saved in a session variable for later use Note In this case the keyword must be enclosed in brackets For example e Using the matching pattern of a simple match is conducted for th
85. be set e g en de etc Follow up State OK Successfully setting the language into session context and the Customer database Follow up State Fail Possible reasons e Unsuccessfully setting the language into the session context e Selected language does not exist in the system e Other unexpected error e Web service internal error while updating customer v Name New Mobiliser Set Language Session amp Ct ol Notes v Input Variables Showing 1 3 O Selectanentry Identification type Identification ofthe customer overrides session LANGUAGE The selected Language Expects a locale en v Follow up States Showing 1 2 ga OK Select a follow up state v A Fail Select a follow up state Select a follow up state v Add Follow up Scenario 1 this state is typically used following the Get Language Menu state that show the language menu list The customer selects the language from the menu list and the selected language code automatically populate the required field in this state as shown below See the usage of the Set Language Session state for example Money Mobiliser State Customer Management 110 m Brand Mobiliser Development Manual Version 1 2 September 2011 Descriptions Set the mode of how the customer opts in to receive the information message such as newsletter etc Input Variables j Identification type The type of customer identification to use
86. biliser Development Manual 35 Version 1 2 September 2011 To test the application you will only use button to Send to Brand Mobiliser and can ignore the Message Encoding drop downs and the Send to CUSTOMER button The button labeled Refresh Message Log allows all messages into and out of Brand Mobiliser for the entered Customer MSISDN to be displayed in the list below it You have to manually click this button after sending a message into Brand Mobiliser to see any response message returned The figure below shows a sequence of interactions using a series of applications that demonstrate integration with Money Mobiliser The message log shows messages in using a green arrows and messages out using red arrows In this case the customer has logged into the test system by entering their credentials and is then presented with a series of menus Simulate Incoming Outgoing Message Customer MSISDN 447977257100 ClientMSISDN 123456 send SMS Message Channel SMS Message Encoding normal 3 Message Text Send to Brand Mobiliser Send to CUSTOMER C Send with Acknowledge Send 100 Messages at max rate to CUSTOMER Simulate incoming Message from customer Simulate outgoing Message TO customer You better be aware what you do Refresh message log Message Client Receiver MSISDN 21 12 2010 Mobiliser Menu 4 Test Ident 447977257100 1 Check Identification 2 Check Credential 3 Change Credential 4 Counter 5 11 22 46 mae Top aon Copy
87. card bank account SVA etc Both types has unique ID Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory List of PI types The PI types to be excluded from the customer wallet PI list This is a comma separated list of PI IDs e g 23 45 33 List of PI classes The PI classes to be excluded from the customer wallet PI list This is a comma separated PI class IDs Max count of Pls The maximum number of Pls to retrieve Show Exit menu item This defines whether the Exit menu item 0 Back should be displayed O no 1 yes Currency of the selected PI The currency of the selected PI PI Type The type of the sel
88. cation is the one that has been activated and the start date is before the current date Follow up State DYN to follow WU Uses the returned value from the Application Call Return state to choose which transition v Name Validate agent code format g Application v Follow up States Target Get agent information Expression SUCCESS Target Invalid agent code format Expression FAILURE Cash Out Process Validate Agent Code Format Showing 1 2 Assign To Assign To Select a follow up state e This state can be used for Interactive Application only that identifies an agent This code must be validated Because this check is carried out frequently in various applications the validation procedure may be written as a separate application It returns STATUS code indicating the validation status Using multiple follow up states we can match to the returned value for the appropriate next state as shown below Usage Scenario 1 For example consider the case when the user must enter a 6 digit code Main Flow Name Application Call Check Agent Code D Notes MAIN MENU APPLICATION VALID AGENT H CALL CHECK PROCEED AGENT CODE Application A Manual Mob Sub z Send SMS Send SMS Follow up States Showing 1 3 Target Valid Agent Proceed INVALID AGENT CODE FORMAT Expression 0 Assign To Send SMS Target Invalid Agent Code Format Expression 1 Assign To Target Invalid Agent Goto Main Menu
89. ching pattern up or down the list Use the button with cross over a the transition line to remove a transition or matching pattern from the list Using the Keyword Tester The Keyword Tester is a pop up window that can be accessed by clicking the icon on the right hand side of each Expression and Assign To entry fields for a follow up state The tester will open and populate the Expression and Assign To fields of the tester to the values associated to the follow up state against which the icon is Expression Assign To AGENT_CODE Text To Test Result Variables Figure 3 Keyword Tester Popup 4 m Brand Mobiliser Development Manual E Version 1 2 September 2011 The tester allows you to assess the suitability of the expression and the assignment of matched parts of a text input to variable To test an expression you must enter arbitrary text into the Text To Test entry field then click the Test button The test result will be shown in the Result field either Matched if the expression matches against the entered text or No Match if there is a no match for the expression against the entered text Expression i Assign To AGENT CODE Text To Test any text Result Matched Variables AGENT _CODE any text Figure 4 Keyword Tester Popup Basic Expression The Variables field will show all matching groups and their assigned values The figure above shows this result for an a
90. constructed as shown below In this case the customer support number is customized based on the recipient s country PROCESS GET COUNTRY SUBSCRIBER SUBSCRIBER CANADA INFO SET CANADA TOLL NUMBER GOTO END SET MEXICO TOLL NUMBER SET DEFAULT TOLL NUMBER 66 Brand Mobiliser Development Manual Version 1 2 September 2011 Subscriber State Descriptions Get subscriber information from the selected subscriber list The subscriber MSISDN is retrieved from the session variable MSISDN by default Up to 20 subscribers attributes can be retrieved and assigned to the session Input Variables Subscriber Set the subscriber set to use The drop down list presents the subscribers in the workspace Subscriber MSISDN the MSISDN unique key of the subscriber to retrieve the attributes from Output Variables Attribute 1 20 The attribute values from the subscriber set is assigned to this session variable Follow up State OK The subscribers attributes has been retrieved successfully Follow up State Fail Error while retrieving the subscribers attribute due to one of the following possible reasons e MSISDN does not exist e Non recoverable system error such as database connection etc U v Name New Get Subscriber state 30 Notes v Input Variables testList MSISDN Showing 1 2 v Subscriber Set Subscriber MSISDN v Output Variables Showing 1 5 6 10 11 15 16 20 All
91. ctive End Jul 6 2012 12 45 BST Actions Sample Goto Application Interactive eS Start Jul 6 2011 17 50 BST ACTIVE End Jul 7 2012 17 50 BST Actions Sample Using Variables Interactive es Start Jun 20 2011 00 00 BST ACTIVE End Jun21 2012 00 00BST actions Sample Encrypted Login Interactive Start Jul 27 2011 15 45 BST ACTIVE End Jul28 2012 15 45 BST Actions Test Event Application Test Event Start Jul 20 2011 11 50 BST ENDED End Aug 21 2011 11 50 BST Actions Group Export Applications Figure 41 Group Export Applications 6 3 Importing Applications To import an application or a group of applications using the Upload button on the New application Add an asset page Note The import process can produce duplicate named applications Brand Mobiliser Development Manual Version 1 2 September 2011 New Application Create New Application New OR Upload from External File Application Name Choose File PTR Ea Aa Upload gt Import Success Application name is Cash Out Process Figure 42 Import a Single Application Note Importing single applications that have states that link to other applications require the applications linked to be created prior to the import in order for the import process to resolve the links For example a Go To Application state will require that the application being linked to exists prior to the import
92. d Also see the Get PI Balance state Input Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Currency associated with SVA currency Use Case id of fee to be applied use case id Follow up State OK Success in retrieving the balance Follow up State Fail Possible causes Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found Unexpected error Follow up State DYN 0 No SVA balance fou
93. dark grey surround as in the figure below Mobiliser Counter A COUNTER STATE Delete MOBILISER COUNTER APPLICATION Start Application Ul SHOW COUNTER GOTO MENU OPTIONS Go To Application Figure 14 State with Entry and Exit Transitions Highlighted Since the Mobiliser Counter Application state transitions TO the Mobiliser Counter State it is given a blue surround with that transition emboldened in blue The Show Counter state has a transition FROM the Mobiliser Counter State and is therefore has an orange emboldened transition line In this configuration it is more complex because the Show Counter state also has the configuration to transition back to the Mobiliser Counter State hence a second blue emboldened transition line into the Mobliser Counter State 20 m Brand Mobiliser Development Manual E Version 1 2 September 2011 So because the Show Counter state is both a transition TO and a transition FROM state for Mobiliser Counter State we show a part orange part blue surround Transition TO lines are always drawn to the left or top of a state hence the orange part surround in that area Transition FROM lines are always drawn from the bottom or the right of a state hence the blue part surround in that area Note To remove all the highlight surrounds and bold transition lines click again on the highlighted state The figure below shows the exit point to this applica
94. differs from the original transaction amount 2571 INFO PAYEE WALLET ABSOLUTE LIMIT EXCEEDED Indicates that the payees wallet absolute credit limit has been ee 2572 INFO PAYER WALLET ABSOLUTE LIMIT EXCEEDED Indicates that the payers wallet absolute debit limit has been ee 2573 INFO PAYEE WALLET MONTHLY LIMIT EXCEEDED Indicates that the payees wallet monthly credit limit has been Lae 2574 INFO PAYER WALLET MONTHLY LIMIT EXCEEDED Indicates that the payers wallet monthly debit limit has been Cl lesa a lama mmasanncaae exceeded Brand Mobiliser Development Manual 151 Version 1 2 September 2011 2576 INFO PAYER WALLET DAILY LIMIT EXCEEDED Indicates that the payers wallet daily debit limit has been exceeded exceeded has been exceeded exceeded has been exceeded has been exceeded 152 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 2969 ERROR EMPTY PLAY LIST 9901 WARN REMOVE COPIED TO 1311 NO COMM WITH MSG GW The error code indicates a problem that occurred in the communication with msg gw 9935 ERROR UNKNOWN DB ERROR An unknown database error occurred Please contact support 9999 ERROR UNKNOWN ERROR An unknown error occurred Please contact support 11001 ERROR CUSTOMER CONFIGURATION INVALID A customer setup is incomplete or invalid Brand Mobiliser Development Manual 153 Version 1 2 September 2011
95. e To avoid the pre transaction balance be overwritten by the post transaction balance we need to copy it into another session Brand Mobiliser Development Manual 53 Version 1 2 September 2011 54 variable prior to calling the Get Balance state again If the copy failed retry to get the customer balance as shown below GET CUSTOMER COPY TXN AUTHORISE SEND BALANCE CUSTOMER TRANSACTION CONFIRMATION BALANCE AND BALANCES Scenario 2 Create a global variable by setting the session variable CREDIT maximum allowable credit limit to 1000 The global variable can be used multiple times in the application NOTE the checkbox of the input variable Source is not ticked LJ v Name Set MAX Allowable Credit Limit po M Notes v Input Variables Showing 1 1 F 1000 Source v Output Variables Showing 1 1 CREDIT ji Destination v Follow up States Showing 1 2 Q oK Success Nextstep _ A Fail Error Handling state Brand Mobiliser Development Manual Version 1 2 September 2011 Base State Input Variables Compares for string equality the value of session variable 1 or constant value 2 to the value of session variable 2 or constant value 2 Name of variable 1 variable 1 Name of variable 2 variable 2 For both variables if checkbox is ticked the source entry is the name of session variable that needs to be retrieved from If it is not ticked the input value w
96. e Missing Payer and or Payee Identifications Web Service Connection Error e Web Service Unknown error Follow up State DYN Error Codes See Appendix B9 Money Error codes 134 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 LJ v Name Pre Authorise Send Money 2 v Input Variables Showing 1 5 6 10 11 11 All EUR Currency of transaction 193 Use Case ID AMOUNT Amountto transfer By mobile no v Payer Identification Type Payer Identification v Output Variables Showing 1 3 PAYER_FEE The fee for the payer PAYEE_FEE The fee for the payee PAYEE_NAME The name of the payee v Follow up States Showing 1 2 OK A Fail ERROR Preauthorized Send Money Select a follow up state v Add Follow up Scenario 1 See a typical send money flow with a two step transaction shown in the Usage Scenario 1 of the Send Money state Brand Mobiliser Development Manual ize Version 1 2 September 2011 Money Mobiliser State Transaction Service Descriptions Send money transaction should be conducted using a two step transaction involving Pre Authorization and Commit as follows e Pre Authorization checks whether there is enough money available for the transaction followed by reserving the money so that it is not accessible for other transactions Commit proceed the actual transaction of debiting the money and fees The fe
97. e customer select an entry from the list Also see the Get Language that returns the menu list in a variable NOTE need additional Brand Mobiliser setup to be able to use this state See the notes below for how to setup the languages in the Brand Mobiliser system Show Exit menu item This defines whether the Exit menu item 0 Back should be displayed O no 1 yes Variable of the selected KEY This parameter returns the identification ID of the PI that the customer selected Variable of the selected VALUE This parameter returns the name of the PI that the customer selected A Language has been selected and stored in the output variables Possible reasons are Web service internal error 0 zero item in the menu list 1 only one item in the list and it is automatically selected and stored in the output variables EXIT customer select the O Back U v Name Mobiliser Get Languages Menu 20 Notes Message v Input Variables v Output Variables VAR_SELECTED_KEY VAR_SELECTED_VALUE v Follow up States 0 760 characters Showing 1 1 Show Exit menu item 1 yes O no Default 1 Showing 1 2 Variable name ofthe selected KEY Variable name ofthe selected VALUE Showing 1 2 J OK Show language choice i A Fail Select a follow up state Select a follow up state v Add Follow up Brand Mobiliser Development Manual Version 1 2 September 2011
98. e string entered in the keyword field This pattern will match to any value in the keyword field e Using the matching pattern of the same pattern match will be done but the keyword field can also be assigned to a session variable In more complex cases the keyword may be broken into a number regular expression groups each of which can be assigned to a separate session variable The Target identifies the state that follows the current state if the entered keyword is matched Note The sequence of keyword matching is not random The first entry in the list is the first matching pattern that is checked continuing with other checks in the order in which they are shown in the State Editor but only if there are no previous matching patterns This means that specific matching patterns should be placed before more generalised patterns The example in the figure below shows that a specific response by the user of the single character O a zero is order before the more generalised pattern of match any input In the second list entry the input received is then also assigned to the session variable named AGENT_CODE since the matching pattern is surrounded with brackets This allows the user to either go to application main menu using a specific entry of 0 or to continue with the process by entering an agent code value which will be subsequently validated The arrow buttons on the left side of the dialogue box enable you to move a mat
99. e the customer with the PIN for extra security This can be done once at the beginning of the workflow or repeat anywhere in the workflow as necessary prior to performing sensitive action such as money transfer etc Brand Mobiliser Development Manual 75 Version 1 2 September 2011 76 PROMPT PIN MOBILISER LOGIN CHECK PIN ABORT OR RETRY PIN Scenario 2 allowing PIN retry on fail login COUNTER STATE COMPARE TYPED PROMPT PIN VARIABLES COUNTER ABORT amp BYE Brand Mobiliser Development Manual Version 1 2 September 2011 PROCEED WITH ACTION MOBILISER PROCEED WITH LOGIN CHECK ACTION PIN Money Mobiliser State Security AA amp Blacklist Name Check Identification Descriptions Input Variables Output Variables Follow up State OK Follow up State Fail Follow up State DYN Check the status of a customer The status can be one of the following e REGISTERED AND ACTIVE UNKNOWN BLACKLISTED Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NO
100. e which state follows the current state after a programmatic event that is a choice made directly in the state code regardless of any keyword match The OK and Fail transition do not use keywords or pattern matching to decide which transition to follow Which transition to use will be based on code in the state and validation provided by or events in the back end system being interfaced with The configuration of an OK or Fail transition is entirely based on the individual state being used and should be described in the states description or Notes area Some states will not require the configuration of one or either of these transitions Note If the state does require one or either of these transitions and a follow up state is not specified the application will terminate at that point For Dynamic transitions the state code has the option to return a keyword value which then provides the input to the pattern matching mechanism as described in the section above named Keywords and Variables This dynamic transitioning may be used as an alternative way of transitioning to different successful or a failure outcomes of the state and so may replace the OK or Fail transition Or the dynamic transitioning may communicate additional information back to the application on certain validation problems Y Follow up States Showing 1 3 a OK Mew Mobiliser Tan Pre Authorise Send Money state Ls Fail Invalid amount Target Amount too lowhigh Ea
101. ease re enter the 6 digit agent code of the agent you like to do the cash out transaction with Validate agent Validation Failed code format Validated OK 4 Get agent Unknown information Agent The agent code you entered is not valid Please re enter the 6 digit agent code of the agent you like to do the cash out transaction with OK Is applicable Agent Invalid Format The entered KSh amount is not valid Please re enter the KSh Please enter the KSh amount you like to cash out or amount you like to press 0 to return to the main cash out menu rormat Below Min Above Max Amount 4 The entered Ksh amount is not between KSh 100 and Ksh 50 000 Please re enter the KSh amount you like to cash out or Amount OK press 0 to return the main menu PreAuth Cash The KSh amount you entered exceeds your Out f current mobile account balance Please check Insufficient Funds your current balance and enter a lower KSh Agent SVA amount or press 0 to return to the main menu Pre Auth Limit Hit The transaction could not be processed at this time Please call customer support HOTLINE to get more information Press 0 to return to the main menu _ Please confirm the transaction of KSh AMOUNT_FORMATTED to agent Yes AGENT_CODE by entering your PIN for your account OK eed Account PIN You successf
102. ected PI PI Class The class of the selected PI PI Status The status of the selected PI Variable of the selected KEY This parameter returns the identification ID of the PI that the customer selected For example 10000634 Variable of the selected VALUE This parameter returns the name of the PI that the customer selected For example My Bank Customer selected a PI from the menu list The selected PI and all the PI attributes are stored in the output variables Possible reasons are e Web service internal error Brand Mobiliser Development Manual Version 1 2 September 2011 117 Follow up State DYN 0 zero item in the menu list 1 only one item in the list and it is automatically selected and stored in the output variables EXIT customer select the O Back LJ v Name Mobiliser Get Wallet Account Menu Jul W Notes Message 0 760 characters v Input Variables Showing 1 5 6 6 All O Selectanentry v Identification type IDENTIFICATION Identification of the customer overrides session List of Pl types Example 12 123 45 List of Pl classes Example 1 2 3 Max count of Pils v Output Variables Showing 1 5 6 6 All VAR_ CURRENCY Currency of the selected PI PILTYPE PI Type PI_CLASS PI Class PILSTATUS PI Status VAR_SELECTED_KEY Variable name ofthe selected KEY v Follow up States Showing 1 3 4 5 All A OK Wallet Menu selected item A Fail Wallet Menu failed T
103. elopment Manual E Version 1 2 September 2011 Money Mobiliser State Transaction Service frome Pima Pay the specified invoice Input Variables Output Variables Follow up State OK Follow up State Fail Follow up State DYN Usage Amount The amount to pay Currency The currency of the transaction Payer Payment Instrument ID The ID of the payers payment instrument Payee Payment Instrument ID The ID of the payees payment instrument Invoice ID The ID of the invoice Auth Code The authorization code for the transaction Transaction ID The ID of the transaction The specified invoice has been paid and the transaction ID and authorization code are stored in the output variables Possible reasons Unknown Web service error or Web service connection error Error Codes See Appendix B9 Money Error codes w v Name New Mobiliser Txn Pay Invoice state Jul Notes v Input Variables Showing 1 5 Amount you want to pay Currency lf Amountis set this field must be set Payer Paymentinstrumen ID Payee Paymentinstrumen ID INVOICE_ID Invoice ID you want to pay v Output Variables Showing 1 2 AUTH_CODE Auth Code TRANSACTION_ID Transaction ID v Follow up States Showing 1 2 A OK Select a follow up state v A Fail Select a follow up state Select a follow up state v Add Follow up Scenario 1 typically the Pay Invoice state is p
104. ency VOUCHER AMOUNT The vouchers amount Follow up States T OK Select a follow up state Fail Select a follow up state v Showing 1 2 Select a follow up state Scenario 1 the Find Remittance Voucher state is used in conjunction with the Pickup Voucher state See the application flow in the Pickup Voucher Usage Scenario 1 Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Transaction Service Name Authorize Transaction Depracated Not usable in the current form Not usable in the current form Please do not use this state OPHENenaies Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional
105. end SMS Brand Mobiliser Development Manual 51 Version 1 2 September 2011 This can also be accomplished using the tf i LJ Say Makigaies tate Namo Conover Alontesage E as Variable ALERT_MESSAGE v Name Set MAX Allowable Credit Limit WwW Hotes Value bev account no ACCOUNT_NO has exceed the allowable daily limit i i of CUSTOMER_LIMIT Call us immediately Variable CREDIT Value CUSTOMER_LIMIT Follow up States Follow up States 52 Brand Mobiliser Development Manual i Version 1 2 September 2011 Base State Copies the value of a source variable or constant to a destination variable Input Variables Source the source to copy from If checkbox is ticked the source entry is the name of session variable that needs to be retrieved from If it is not ticked the input value will be constant value as written in the field NOTE Please ensure that the session variable exists otherwise the state will fail Output Variables Destination the destination session variable name The destination variable may or may not exist If it does not exist it will be created Otherwise an existing variable will be overwritten Follow up State OK Successfully copy the source to destination variables Follow up State Fail Failed to copy the source to destination variables Most likely the failure will be due to non existence of the source variable Copy Customer Balance Ts M
106. er Double or Date Text Case Sensitive whether a text based comparison will be case sensitive or not The default is not case sensitive Left Variable the name of the first session variable or value to be compared Operator the comparison operator the variable types versus operators rules are as follows Text l and REGEX When REGEX is selected the REGEX expression is on Right Variable Integer lt lt gt gt Double lt lt gt gt Date lt lt Valid Date format dd MM yyyy HH mm ss 31 07 2011 00 00 00 Right Variable the of the second session variable or value to be compared For both left and right variables if checkbox is ticked the source entry is the name of session variable that needs to be retrieved from If it is not ticked the input value will be constant value as written in the field NOTE Please ensure that both session variables exist otherwise the state will fail Follow up State OK Left and Right Variables are equal Follow up State Fail Left and Right Variables are NOT equal or Left and or Right Variables are the name of session variables to retrieve value from but one or both variables do not exist Follow up State DYN Brand Mobiliser Development Manual 57 Version 1 2 September 2011 U Showing 1 5 v Variable Type Text Case Sensitive Default No TEMP Left Variable Operator
107. er Agent and a normal customer User Right ID The User Right ID can be ignored here because in this context it is the same ID as the Product ID Customer Blacklist Reason ID If the customer is blacklisted the ID of the blacklist reason as listed in Appendix B1 Customer Receipt Mode ID This mode defines whether the receipt should be sent by Email SMS both or not at all The ID mappings is presented in Appendix B6 98 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Customer Cancellation Reason ID The reason why a customer was cancelled In this state this can be ignored Is Customer Active true false Indicates whether the customer is active or not This flag can be used to filter the menu Follow up State OK Customer information was retrieved successfully Follow up State DYN Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found E v Name New Mobiliser Get Customer Information s Ts W Notes v Input Variables Showing 1 3 O Selectanentry Identification type Identification of the customer overrides session MAX length of display name v Output Variables Showing 1 5 6 10 11 15 16 18 All CUSTOMER_ID Customer ID BLACKLIST_REASON Blacklist Reason ID L
108. er wants to perform the transaction with Enter the transaction amount Validate and pre authorise the transaction by checking for sufficient funds in customer account the amount is between limits and the agents SVA is correct Customer enters their account PIN if required or confirms the transaction Perform the send money transaction from the customer to the agent Respond to other validation problems if the transaction then failed What follows in this section is an overview of the service using generalised workflow notation to visual the process and how the Application Composer allows visualising of this service directly in the web user interface after the application has been created or during the process of creating it Brand Mobiliser Development Manual Version 1 2 September 2011 31 4 2 Workflow The figure below shows the schematic workflow of the Cash Out process This workflow is typical of a single service or application that Brand Mobiliser can provide with many validations entries and actions to perform Please select the source account R 1 SVA 2 Current 3 Savings We are sorry We are experiencing technical difficulties Press O to return to the main menu Is selection Valid yes y Please enter the 6 digit agent code of the agent you like to do the cash out transaction with The agent code you entered does not have the correct format Pl
109. ername the Identification of the customer is mandatory Last name customer last name Customer ID customer ID First name customer first name Street customer main address street name Email customer email adress Gender customer gender HouseNumber customer main address street number Zip customer main address zip code City customer main address city County customer main address county Follow up State OK Customer main address retrieved successfully Follow up State DYN 101 Security policies have not been defined for customer yet 1303 System error Session not found 1304 System error Session has timeout 1010 Customer not found 1011 Customer is not unique 1098 Access to customer is not allowed for the current agent 100 m 1221 Agent object not found Brand Mobiliser Development Manual Version 1 2 September 2011 v Name New Mobiliser Get Customer Address state Ta Notes v input Variables Showing 1 2 Select an entry ie identification type E wv Output Variables LAST_NAME CUSTOMER_ID FIRST_NAME Street Email Gender HouseNumber Zip City Country v Follow up States Identification of the customer overrides session Showing 1 5 6 10 All Lastname Customer ID Firstname Street Email Gender HouseNumber Zip City Country Showing 1 1
110. ersion 1 2 September 2011 Note e Currently the transition lines are always automatically positioned and there is no way to move a transition line itself e To ensure that the current layout change is stored you must click on the SAVE LAYOUT button to persist the change to the database The layout change will be lost if not saved and you move off of the Application Composer view This includes selecting a different tab for the same application e Ifyou have zoomed out from the default 100 view you must reset the zoom level back to 100 before making any layout changes 3 1 3 Context and Dependency Highlighting As described previously states are linked in the application through directional transition lines In simple cases these lines clearly show the linked states the state from which the transition is from and to However in many instances there will be a series of lines coming out of and going into a single state To get a better sense of the context and dependencies of an individual state any state can be highlighted Highlighting a state allows all of its transition lines that go to it and go from it to also be highlighted along with the states they come from or go to It also opens the state editor popup for this state To highlight any states e move the mouse over the state icon you want to move and e _left click on the mouse and release The dependent states and transition lines are then highlighted in differe
111. es that are also configurable e Invoice has invoice details called Configuration that include Issued to Consumer Invoice Reference Billing Cycle Auto Pay delay Payment Instrument Authorized Threshold amount Last and Next Invoice Invoice Status Total Amount Maximum Allowable delay etc The Configuration can be retrieved using the Get Invoice Configuration state e Invoice has Type that reflects the following information Active status default Payment Instrument Invoice Type Group Use Case default Billing Cycle default Auto Pay Delay default Initial Delay default Currency default Fetch Cycle flags indicating who add the invoice etc 2 4 5 Transaction Models Transactions are only handled very basically in the Core system because they tend to be very specific to the product e Transaction Status Transaction Type Error Code these attributes are common to all transactions e Participants lists all customers together with the appropriate role that participate in a transaction e Money Transactions store all relevant data for financial transactions this is amount currency payer payee involved payment instruments Each activity on a transaction is stored as a Money Sub Transaction with status information fee and reference information Such activities are Authorization money is authorized from the payment instrument Brand Mobiliser Development Manual Version 1 2 September 2011 Captu
112. es are modeled using different Use Case IDs that are implemented in Money Mobiliser The Commit is performed using this state This state is used in conjunction with the Pre Authorized Send Money state Input Variables i Currency of transaction The currency for the transaction Use Case ID The Use Case ID identifies the type of transaction The Use Case for a CashOut transaction is 1005 Amount The Amount for the transaction Optional PIN for Bank Accounts or other Pls lf money is debited from a bank account the customer must enter the pin for the respective bank account Payer Identification Type The identification type of the payer This can be by mobile No by customer ID or by user name Payer Identification The payer is identified here Normally this ID is retrieved through the mobile number so this field can be left blank Payer PI ID The identification of the payment instrument used by the payer Payer PI class The class of the payment instrument used by the payer This could be Stored Value Account Bank Account Credit Card or External Account Payee Identification Type The identification type of the payee This could be by mobile No by customer ID or by user name Payee Identification The identification of the payee Payee PI ID The identification of the payment instrument for the payee Payee PI class The class of the payment
113. f transactions list of transactions in string format Follow up State Fail Possible causes Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found Unexpected error Follow up State DYN 0 No transaction found 120 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 v Input Variables Showing 1 4 Selectanentry Identification type Identification of the customer overrides session TXN_COUNT i Number of transactions Use case id of fee to be applied v Output Variables Showing 1 1 7 TRANSACTIONS The list of transactions v Follow up States Showing 1 2 T OK E Select a follow up state A Fail _ Selecta follow up state aa Select a follow up state M Add Follow up Save Brand Mobiliser Development Manual 121 Version 1 2 September 2011 Money Mobiliser State Customer Management Retrieves details of a transaction given the transaction ID that belongs to the customer Input Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as
114. follow 10 Open 11 Fully paid 12 Partial paid 13 Cancelled 14 Closed Variable name for the ID of the invoice The issuer ID of the invoice This is obtained from the Get Invoice Configuration state Output Variables p Variable name for list The name of the variable to which the retrieved invoices should be stored First KEY of list The first key of the retrieved list First VALUE of list The first value of the retrieved list Follow up State OK Follow up State Fail Possible reasons are Web service internal error Web service connection error Follow up State DYN where N is the number of item in the returned list NOTE if N 0 the output variables will not be populated 124 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 LJ v Name New Mobiliser Get Invoices List state Ta Notes v Input Variables ID_LINYOICE v Output Variables VAR_LIST_NAME VAR_NAME_FIRST_KEY VAR_NAME_FIRST_VALL v Follow up States Showing 1 4 Select anentry Identification type Identification of the customer overrides session Status Filter one number only Example 42 Variable name for the ID invoice ID Showing 1 3 Variable name for list First KEY of list First VALUE of list Showing 1 1 A Fail Select a follow up state k Select a follow up state Scenario 1 this state is slightly diffe
115. g will still work if you have zoomed out from the standard 100 zoom level 3 2 State Editor The Application Composer also provides facilities to create new states delete old states traverse through the workflow modify the configuration of a state and test keywords for a follow up transition All this is possible through a state editor popup window 3 2 1 The State Editor Popup The popup window will open automatically when a state has been highlighted as described in the previous section Depending on the type of the state that has been opened the state editor will show a number of options context sensitive hyperlinks and entry fields The figure below shows what a general Mobiliser or a8 Party Custom state may look like in the state editor popup This is a typical state only and different state types have differing configuration capabilities Each of the labels are annotated as follows 1 Entry Nodes An entry node identifies a link to another state that flows TO this state Entry Nodes are click sensitive and if you click on it you will open the state editor for the state that this transition relates to Mouse over on an entry node will show the state name associated with it 2 State Type Watermark and Icon Alongside the states name is a watermark icon associated with that state type The same watermark is shown as the back to a state icon on the layout view and is also shown in the Target of the Follow up States section
116. ge Startpage 123456 4 Startpage Welcome to Mobiliser Tester send mobiliser to continue 21 12 2010 11 44 03 menupage Startpage 123456 hello Figure 37 Mobiliser Counter Simulation 1 To test the keyword match for the loop back to the Mobiliser Counter State we enter the keyword again and refresh the message log to show the following additional interactions 38 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Refresh message log Client Timestamp Message Receiver MSISDN Dir Msg 21 12 2010 11 49 22 21 12 2010 11 49 21 21 12 2010 Mobiliser Menu Misc i PENIS 11 44 21 smapp F nctions 123456 4 1 Send back to continue again to re run 21 12 2010 Mobiliser Menu Misc 11 44 20 SmapP Functions 21 12 2010 11 44 17 21 12 2010 11 44 17 21 12 2010 11 44 12 21 12 2010 11 44 10 21 12 2010 11 44 08 21 12 2010 11 44 08 21 12 2010 11 44 03 21 12 2010 11 44 03 smapp Mobiliser Counter 123456 4 2 Send back to continue again to re run smapp Mobiliser Counter 123456 again 123456 4 Test Ident 447977257100 1 Check Identification 2 Check Credential 3 Change Credential 4 Counter 5 Copy Var 6 Get Languages 0 Back smapp MobiliserMenu Top 123456 E smapp Mobiliser Menu Top 123456 45 Test Ident 447977257100 1 Get Cust Values 2 Set Cust Values 3 Wallet Fns 4 Money Fns 5 Misc smapp Mobiliser Tester Login 123456 Eta Ens 6 Set alt test MSISDN
117. he Get PI Balance state you need to provide the Payment Instrument ID Typically this is done by getting in from the Get Wallet Menu state The Get Wallet Menu state may have been used earlier in the application flow and save the customer selected Payment Instrument ID in a variable the default variable name is called VAR_SELECTED_KEY This variable is used in the Get PI Balance state as shown in the example is shown below GET WALLET GET PI BALANCE MENU gt Money Mobiliser Brand Mobiliser Development Manual 113 Version 1 2 September 2011 114 LJ v Name Get PI Balance Tj EE Notes v Input Variables i j v Output Variables 7 BALANCE 7 CURRENCY v Follow up States Showing 1 2 Optional PIN for Bank Accounts or other Pls Showing 1 2 Balance of the PI Currency of PI Showing 1 2 oK New Send SMS state x A Fail Select a follow up state Select a follow up state M Add Follow up Save Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Customer Management Descriptions Retrieve the balance of the SVA type Payment Instrument of the customer This is sort of the shortcut of the Get PI Balance state because the Payment Instrument ID is not needed for input The system will find the SVA type if available Otherwise DYN 0 will be returne
118. he workflows involved in orchestrating the user interaction or the business processes that are to be mobilised This is the primary purpose of the web based user interface also known as Application Composer 3 1 State Layout The Application Composer state layout view is the primary way of visualising the processing steps of the application workflow by visualising the states and drawing the transitions between these states Much as a generalised visual workflow tool would do the Application Composer allows the application designer the ability to e visualise states in the application using an automatic layout e dragging and dropping of states to re arrange layout and to persist the modified layout e highlight the context and dependencies the transitions of states and e zooming in and out of the application composer view to see a complete or partial application layout The Application Composer also provides complete facilities to traverse through the workflow through a state editor popup window The state editor popups purpose is to allow configuration of the states settings and values This is described separately in the next section 3 1 1 Visualising States The example in the figure below shows the layout of an existing simple application called Mobiliser Counter This application uses a counter to increment a session variable which is shown to the user who responds with an instruction to repeat or to go back to a menu Each step in
119. he figure above because you cannot remove a Start Application state but it will shown on any other type of state Brand Mobiliser Development Manual Version 1 2 September 2011 Add a follow up state as selected from the follow up selector to the left of the button To add a transition from the Start Application state i e My First Application choose a state from the follow up selector and then click the Add Follow up button The figure below shows all the available follow up states My First Application APPLICATION DETAILS KEYWORDS APPLICATION COMPOSER APPLICATION EDITOR EDITOR Application Actions bd MY FIRST APPLICATION SAVE LAYOUT REVERT LAYOUT Gridlines Al v Zoom 100 v A vame TT E E Select a follow up state E Add Follow up Select a follow up state a Ul Mobiliser Block Until New Mobiliser Change Credential New Mobiliser Check Credential New Mobiliser Check Identification New Mobiliser Copy Variables New Mobiliser Counter New Mobiliser Delete Network Entry New Mobiliser Format Amount New Mobiliser Get PI Balance New Mobiliser Get Customer Attribute New Mobiliser Get Invoice Configurations List New Mobiliser Get Invoices List New Figure 24 Choose Next State Note For a new application you can add new instances of states When you have created some states
120. he n previously used credentials INFO CREDENTIAL WEAK ASCENDING Indicates that the credential to create or update presumably contains a 204 block of ascending characters INFO CREDENTIAL WEAK EQUALITY Indicates that the credential to create or update presumably contains a 205 block of equal characters INFO CREDENTIAL WEAK DESCENDING Indicates that the credential to create or update presumably contains a 206 block of descending characters INFO CREDENTIAL EQUALS IDENTIFICATION Indicates that the specified credential is the same as one of the 207 customers identifications INFO CREDENTIAL REGEX MATCH Indicates that the credential does or does not match one of the security aoe poilicies regular expressions and thus is invalid WARN INVALID CREDENTIAL TYPE Indicates that the type of the credential to create or update presumably is 209 invalid i e the customer is not allowed to have a credential of that type 1001 ERROR INVALID REQUEST Indicates that the request is either incomplete or invalid 1002 INFO INVALID MSISDN Indicates that one of the specified MSISDN s is invalid MSISDNs always have to specified as countryCodenetCodenumber 1003 INFO UNKNOWN TRANSACTION Indicates that the or a transaction specified in the request does not exist Brand Mobiliser Development Manual Version 1 2 September 2011 149 used considered in the requested context used considered due to its status 1006 WARN INACTIVE
121. iables Showing 1 3 O Selectanenty Identification type Identification of the customer overrides session O Selectanentry v Receipt Mode v Follow up States Showing 1 2 A OK Select a follow up state v A Fail Select a follow up state Select a follow up state v Add Follow up 112 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Money Mobiliser State Customer Management Get the current balance and the currency of a payment instrument Input Variables Name of the PI ID The payment instrument ID e g 10002570 Optional PIN for Bank Accounts or other Pls PIN for Bank Accounts or other Pls Output Variables Balance of the PI The balance of the PI Currency of PI The currency of the PI Follow up State OK Success in getting the balance and PI and set them to the output variables Follow up State Fail Possible reasons are e Update failure e Web service internal error U vy Name Mobiliser Get PI Balance State JE Notes v Input Variables Showing 1 2 PI_ID Name ofthe PI ID Optional PIN for Bank Accounts or other PIS v Output Variables Showing 1 2 BALANCE Balance ofthe PI CURRENCY Currency of PI v Follow up States Showing 1 3 A OK Mobiliser Get PI Balance show balance v A Fail Mobiliser Get PI Balance get balance FAILED Target New Send SMS state Expression Assign To MOB_ERROR Scenario 1 to use t
122. ill be constant value as written in the field NOTE Please ensure that both session variables exist otherwise the state will fail Follow up State OK Follow up State Fail Variable 1 and Variable 2 are NOT equal or Variable 1 or Variable 2 is the name of a session variable to retrieve value from but the session variable does not exist Variable 1 and Variable 2 are equal w v Name Compare Variables 20 Notes v Input Variables Showing 1 2 TEMP Name of variable 1 VAR2 Name of variable 2 vy Follow up States Showing 1 2 A OK Send Variable Values Equal v A Fail Send Variable Values Not Equal Select a follow up state v Add Follow up Scenario 1 Comparing the value of two session variables TEMP and VAR2 If the values are equal proceed to the Send Variable Values Equal state Otherwise proceed to the Send Variable Values Not Equal state Also if TEMP or VAR2 do not exist proceed to the Send Variable Values Not Equal state This state compare for string equality only For comparing other types use Compare Typed Variables state listed below Scenario 2 compare the value of a session variable to a constant string ACCOUNT to saving respectively If the values are equal proceed to the Send Variable Values Equal state Otherwise proceed to the Send Variable Values Not Equal state Also if ACCOUNT does not exist proceed to
123. is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Payment Instrument ID The ID of the payment instrument Is Primary Debit Defines whether the payment instrument should be used for primary debit Is Primary Credit Defines whether the payment instrument should be used for primary credit Follow up State OK Successfully setting the Primary PI Follow up State Fail Possible reasons No Pl in the customer wallet Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found Unexpected error Follow up State DYN Brand Mobiliser Development Manual 129 Version 1 2 September 2011 130 LJ v Name New Mobiliser Set Primary PI state Tu Notes v Input Variables Showing 1 5 Selectanenty Identification type Identification of the customer overrides session PID Payment Instrument ID Select an entry Is Primary Debit Select an entry Is Primary Credit v Follow up State
124. iser Get Languages state Bol E Notes v Input Variables Showing 1 2 Select an entry identification type m Identification of the customer overrides session v Output Variables Showing 1 1 LANGUAGES List of languages v Follow up States Showing 1 2 A OK Select a follow up state x Fail Select a follow up state Select a follow up state M Add Follow up For more advanced menu list please use the Get Language Menu state Languages are setup in Brand Mobiliser M_LANGUAGES table Currently setup is performed using DB script only Brand Mobiliser needs to be restarted to the changes to be available 92 m Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State System Management Descriptions Input Variables Output Variables Follow up State OK Follow up State Fail Follow up State DYN Send the list of supported Language on the system to the customer as a menu list Facilitate the menu list paging interaction and proceed to the follow up states after the customer selects a Language from the menu list This is a List based state The list is automatically truncated to fit one SMS message If the list is longer than one SMS message an option to see more is provided 9 More or an option to exit the list 0 Back This state facilitates the paging interaction and transition to the follow up state after th
125. itself an application It is possible to invoke an application logic directly depending on the keywords specified for an application 40 m Brand Mobiliser Development Manual E Version 1 2 September 2011 6 Importing Exporting Applications Brand Mobiliser provides the ability to create an exported copy of an applications configuration This is useful in order to e Move an application between instances of Brand Mobiliser installations e Make a back up copy of an individual application 6 1 Export a Single Application To export a single application use the Export button on the Application Details page Cash Out Process APPLICATION DETAILS kevworps APPLICATION COMPOSER APPLICATION EDITOR General Application Information Name Cash Out Process Category test Active From 121610 MA Active To 121712 fiz Session Settings Optional Timeout secs 450 Session Limit Response This produces an XML file that represents the configuration of the application A sample of the exported file is shown below appFlow xml Figure 40 Export Single Application lt xml version 1 0 encoding UTF 8 standalone yes gt lt root xmins http ipsquare at xsd mwiz gt Application Actions v lt smapp serviceMenuActionTypesId 3100 smappApplicationTypesId 102825 actiyerrom 2010 12 16T00 00 00 0007 actiyeTo 2012 12 17T00 00 00 0007 inicial sSrcarcesIrc 1268 ShortName S lA 2
126. la Expression MIM MAx Assign To Select a follow up state wt Add Follow up Figure 8 Example Success Fail and Dynamic Transition Brand Mobiliser Development Manual Version 1 2 September 2011 The example in the figure above shows a configuration of a state with an OK Fail and a single dynamic transition The dynamic transition uses the regular expression MIN MAX will match against the dynamic values of MIN or MAX that are returned by this state after unsuccessful validation of its input 2 2 Base States Brand Mobiliser currently offers a number of base states These states provide stand alone functionality without dependency or interaction with the external services The base states are the basic functionalities that are commonly needed when constructing the process flow The base states include e Send SMS Sends a text message to the customer identified in the current user session e Goto Application Causes the program to flow into another application e Set Variable Sets a session variable for the current user session e Compare Variables Simple variable comparison comparing the contents of two variables for equality e Compare Typed Variables Advanced variable comparison comparing the contents of two variables using specified data types and operators e Copy Variable Copy the contents of one session variable into another e Counter Increment a named counter e Application Call Retur
127. le ten v Follow up States Showing 1 2 T OK Select a follow up state A Fail Select a follow up state Select a follow up state v Add Follow up Scenario 1 this state is typically used following the Get Language Menu state that show the language menu list The customer selects the language from the menu list and the selected language code automatically populate the required field in this state as shown below GET LANGUAGES SET LANGUAGE PROCEED MENU SESSION ONLY Name Get Languages Menu J Notes Message Lang 4 160 characters input Variables Output Variables ing 1 D atk ah v Name Set Language Session only J Notes VAR_SELECTED_KEY Variable name of the selected KEY v Input Variables Showing 1 1 VAR_SELECTED_VALUE Variable name of the selected VALUE W VAR_SELECTED_KEY The selected Language Expects a locale en v Follow up States Showing 1 2 v Follow up States Showing 1 2 A OK Set Language Session only A OK Proceed Fail Select a follow up state Fail Select a follow up state Select a follow up state I Add Follow up Save Brand Mobiliser Development Manual Version 1 2 September 2011 95 Money Mobiliser State Customer Management Descriptions Check if the customer exists and returns some customers attributes NOTE this state has been deprecated Use Get Customer Information state instead Input Vari
128. le messages are sent To embed the value of a session variable into the text enter the name of the variable surrounded by and For example the text The value of the counter is INDEX would replace the text INDEX with the value of the session variable INDEX If no variable with that name exists the text is sent as is including the text INDEX NOTE When the Send SMS state is used in Event Application the Request SMPP Acknowledgement flag is shown enabling acknowledgement request from the SMPP gateway Follow up State DYN Continue the application when a response from subscriber is received Match the response to the follow up states Expression to determine the follow up state LJ v Name Change Credential Enter New Bol Notes Message Enter new credential value 26 760 characters Y Follow up States Showing 1 1 Target Mobiliser Change Credential State x gt Expression Assign To NEW_CRED Select a follow up state v Add Follow up One follow up state is specified The expression means any response from subscriber will match Also assign the response to the NEW_CRED session variable so that it can be used later in the workflow It may not be possible to determine the exact number of characters in the message prior to run time if session variable values are embedded into the message During runtime the Send SMS state results in a temporary suspension of the a
129. leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Attribute ID customer attribute ID This ID needs to be obtained from the configuration or customization specifications or documents Attribute Value customer attribute value Follow up State DYN Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found System Error DB Error or Invalid Attribute ID UW x Name New Mobiliser Set Customer Attribute state ol W Notes Y Input Variables Showing 1 4 O Selectanentry Identification type Identification of the customer overrides session ATTRIBUTE_
130. llow by the commit using this state Continue Voucher Remittance Upon successful transaction the pickup code will be generated The ID of the pre authorization D value The pickup code for the Voucher Pickup code Send Voucher Remittance complete successfully The pickup code is generated and stored in the output variable Possible reasons Unknown Web service error or Web service connection error New Mobiliser Txn Continue Voucher Ren v Input Variables Showing 1 1 The ID of the preauthorisation v Output Variables Showing 1 1 PICKUP_CODE The pickup code for the Youcher v Follow up States Showing 1 2 OK Select a follow up state v Fail Select a follow up state v Add Follow up Select a follow up state Scenario 1 the send voucher remittance flow is very similar to the send money flow Both involves a two step transaction pre Authorize and commit using the Start Voucher Remittance and Continue Voucher Remittance respectively The simplify flow is shown below with the error handling omitted for clarity VERIFY CREDENTIAL PIN START VOUCHER REMITTANCE PRE AUTHORIZE Application Call CONTINUE VOUCHER REMITTANCE COMMIT Money Mobiliser GATHER PAYER amp PAYEE INFORMATION SHOW PICKUP CODE Delete Scenario 2 the send voucher remittance is typically complemented by the pickup voucher remittance flow After a successful send voucher remittance see scen
131. llow up States Showing 1 2 A OK Select a follow up state v A Fail Select a follow up state Select a follow up state v Add Follow up Scenario 1 the Add Subscriber state can be used to store Opt In Opt out subscriber The following example show a common more info application A push message was sent to subscribers The message contains reply keyword e g more or info for interested subscribers When they reply with the keyword the application pull the subscriber information from the list used in the campaign Get Subscriber Information State and Brand Mobiliser Development Manual 69 Version 1 2 September 2011 then add the subscriber into the Opt In list Add Subscriber state before sending the discount coupon as a thank you gift for loyalty MORE INFO GET ADD SUBSCRIBER SEND SMS SUBSCRIBER STATE COUPON INFORMATION STATE UJ v Name Get Subscriber Information state JE E Notes v Input Variables Showing 1 2 LW v Name Add Subscriber state ww v Input Variables Showing 1 5 6 10 11 15 16 20 21 22 All Subscribers T Subscriber Set MSISDN Subscriber MSISDN BA TE suvscriver set v Output Variables Showing 1 5 6 10 11 15 16 20 All R E i Subscriber MSISDN J ATTRIB1 Attribute 1 Attribute 1 ATTRIB2 Attribute 2 BEVERAGE Attribute 2 ATTRIB3 Attribute 3 ATTRIB2 Attribute
132. mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Credential Type credential type Supported types are Credential is a PIN or Credential is a Password Old Credential Value The old credential value of the customer chosen during the registration New Credential Value The new credential value of the customer chosen during the registration Follow up State OK Customer credential changed successfully Follow up State Fail Follow up State DYN Possible reasons are e Invalid credential or customer is not registered in the system e Web service internal error 101 Security policies have not been defined for customer yet 204 Credential does not meet the required security policy 1010 Customer not found 1011 Customer is not unique 1098 Access to customer is not allowed for the current agent 12
133. much money can be spend on a daily or monthly basis independently of the overall limit of the payment instrument Usually the correct payment instrument is selected by the system during the time of transaction based on the wallet priority PI is classified into types and classes Example of PI types include Consumer Merchant etc Each types can have the following PI classes such as credit card bank account SVA etc Both types has unique ID Wallet has an assigned Primary Payment Instrument that can be modified by the wallet owner In addition the primary PI can be further assigned as the Primary Debit PI and or Primary Credit PI The following diagram provides a simplified overview of the customer centric part of the DB model SVA IDENTIFICATION PK IDIDENTIFICATION ID CUSTOMER Mobile Phone Number Email Username VOUCHER Account Ma BANK_ACCOUNT F CREDENTIAL PAYMENT INSTRUMENT WALLET_ENTRY CUSTOMER PK ID_CREDENTIAL IL E I0_CUSTOMER MAME iaia ford ID_ LIMIT Public Key ADDRESS Px Janos ID_ CUSTOMER PRIVILEGE PK ID_ PRIVILEGE PK FK1 1D CUSTOMER PK 1D WALLET ENTRY PK FK1 De PK joe ka FK1 iD PI FK2 ID_CUSTOMER ee ID_LIMIT LIMIT Pu Eee a Daily Monthly Absolute The following statements describe the customer related DB schema e One Customer can have multiple Identifications e Each Identification is unique in the system e One Customer can have multiple
134. n Calls into another application and returns to the called from application e Mobiliser Regex Match a session variable to a regular expression These states are described in detail in the section Appendix States Catalog Note prior to release 1 2 of Brand Mobiliser some of these states were included in the Mobiliser Core bundle and described as Mobiliser Utility States For these states they have now been moved into the Brand Mobiliser Base States bundle However they retain their old state id values and therefore references to these states in applications created with previous Brand Mobiliser versions will work in the same way The only difference is the name in the follow up selector will not be prefix with the Mobiliser word For example the Mobiliser Counter New will now be just Counter New 2 3 Subscriber States Brand Mobiliser version 1 2 introduced a general purpose data storage due to the need to store subscribers attributes that can be used to perform push campaign hence the name Subscribers The subscriber storage is available to application using the Subscriber states listed on the following Ideally this storage should be used as a non durable storage for purposes of staging or in transit storage pending batch transfer to the system of record The reason is the database schema used by this storage was designed to be very generic and therefore was not fully optimized for large scale and more dom
135. n CHECK EXISTS PIN IDENTIFICATION STATE v Follow up States Showing 1 3 OK Consumer Exists PIN x Fail Select a follow up state E 7 GOTO Target Goto Registration x REGISTRATION 3 7 7 Expression 1 Assign To Select a follow up state M Add Follow up Save Scenario 2 The Customer Registration state is typically called after gathering all the registration information through multiple interaction with the user as shown below Note error handlings are intentionally excluded for clarity T amp C CHECK PROMPT NAME amp PIN VERIFY PIN MOBILISER WELCOME NEW CUSTOMER USER amp MENU REGISTRATION 4 ff Brand Mobiliser Development Manual E Version 1 2 September 2011 Money Mobiliser State Security AA amp Blacklist ome Descriptions Perform additional verification based on the customer PIN and the identification value This is an extra security verification in addition to the MSISDN The PIN number was set by the customer during the signup process Also see the Check Credential state that performs the same function and is the recommended state to use instead of this Login state Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile
136. nd Brand Mobiliser Development Manual Version 1 2 September 2011 115 116 LJ v Name New Mobiliser Get SVA Balance state Ta Notes v Input Variables Showing 1 4 Select an entry v Identification type Identification of the customer overrides session CURRENCY Currency associated with SYA Use Case id of fee to be applied topt v Output Variables Showing 1 1 BALANCE The SVA Balance v Follow up States Showing 1 2 OK Select a follow up state A Fail Select a follow up state Select a follow up state v Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Customer Management Descriptions Input Variables Output Variables Follow up State OK Follow up State Fail Send the list of Payment Instrument PI that are available in the customer Wallet to the customer as a menu list Example 1 SVA 2 BCard 0 Back This is a List based state The list is automatically truncated to fit one SMS message If the list is longer than one SMS message an option to see more is provided 9 More or an option to exit the list 0 Back This state facilitates the paging interaction and transition to the follow up state after the customer select an entry from the list The PI has types and class Example of PI types include Personal Pl Merchant PI etc Example of PI classes include credit
137. ne every time the state is called Input Variables Variable Name the counter session variable name The value of the session variable is to be incremented The checkbox have to be ticked otherwise the state will fail Follow up State Fail Occurs when the variable name checkbox was not ticked or other internal error Follow up State DYN N the updated counter N is integer A ww v Name Increment Counter Bol Notes v Input Variables Showing 1 1 INDEX Variable name v Follow up States Showing 1 2 Fail Select a follow up state Target Reset To Variable A Expression Assign To FROM The counter state can be used as an index in the loop commonly used in allowing user to retry for a limited amount of times See scenarios below Counter is a session based variable and not a global variable Scenario 1 a simple and commonly used scenario of the Increment Counter state will be in prompting PIN with limited retry Please refer to Counter state Usage Scenario 1 Brand Mobiliser Development Manual m Version 1 2 September 2011 Base State Goto Application Descriptions Move to a different application from this state This is an end state for the current application and transfer of control to the goto application All the session variables will be made available to the goto application by selecting any one of the applications displayed in the drop down box This st
138. nt colours The highlighted state is shown with a dark grey surround e Any states that transition TO the highlighted state have a blue surround with the transition line emboldened in blue Any states that are transitioned FROM the highlighted state have an orange surround with the transition line emboldened in orange e n some cases a state has both a transition FROM and a transition TO another state In this case the highlighted state have a part blue part orange surround with associated transition lines coloured blue or orange The example below shows the simplest case where the Start Application state is highlighted and is shown with a dark grey surround In this case there are no states that transition back to the start state However the Mobiliser Counter State is transitioned TO and so is displayed with an orange surround and the transition line is emboldened in orange Brand Mobiliser Development Manual Version 1 2 September 2011 19 Mobiliser Counter APPLICATION DETAILS Kevworns APPLICATION COMPOSER APPLICATION EDITOR Application Actions v AAO A e E A v MOBILISER COUNTER STATE Money Mobiliser SHOW COUNTER Send SMS gt MOBILISER COUNTER APPLICATION Start Application Ul GOTO MENU OPTIONS GoT j To Application Figure 13 Highlighted Start State If we instead highlight the Mobiliser Counter State by clicking on it we will see that state given a
139. o use these states For the purpose of the discussion here the Application Call Check Credential returns a value that is stored in OLD CRED variable This variable is used in the Change Credential state as shown below v Name Compare New Credentials J Notes W v Input Variables v Name Application Call Check Credential tw Showing 1 2 CRED1 q Name ofvariable 1 Application Check Credential SUB App i CRED2 Name ofvariable 2 v Follow up States Showing 1 2 v Follow up States Showing 1 1 OK j Target Prompt New Credential x gt L as ees z Expression E Assign To l Fail Abort or Retry z Select a follow up state xl Add Follow up Save Select a follow up state M Add Follow up Save Brand Mobiliser Development Manual Version 1 2 September 2011 LJ v Name Change Credential o w Input Variables Showing 1 5 Select an entry Identification type Identification of the customer overrides session Credential is aPIN Credential Type I OLD_CRED J The customers old credential value W CRED1 The customers new credential value v Follow up States OK Fail Showing 1 2 Confirmation Error Handling Select a follow up state x Add Follow up Brand Mobiliser Development Manual Version 1 2 September 2011 85 Money Mobiliser State Security AA
140. on 1 2 September 2011 B Appendix Mobiliser Web Service Lookup Values This appendix section references lists of static values that are returned by the Mobiliser Web Services and the Mobiliser Web Service States B 1 Blacklist Reason oo w o ooo o o i feen OO Ce OOOO O C me OOS B 2 Card Types B 3 Customer Cancellation Reasons Brand Mobiliser Development Manual Version 1 2 September 2011 147 B 4 Identification Types MSISDN in international format e g 14155551234 491701234567 Customer ID IMEI Foreign customer ID Username Email B 5 Identity Types o reeeo OOOO ooo ron o B 6 Info Mode amp Receipt Mode B 7 User Rights Product ID 148 Brand Mobiliser Development Manual Version 1 2 September 2011 B 8 Errors C B 9 Errors ID TYPE Description 101 ERROR CONFIGURATION_CUSTOMER_INVALID Indicates that a customer is set up invalid or incomplete FATAL LICENSING 191 ee FATAL DATABASE INCONSISTENCY Indicates that some prerequisites on the database side are not fulfilled INFO MINIMUM CREDENTIAL LENGTH Indicates that the credential to create or update presumably exceeds 201 the minimum credential length INFO MAXIMUM CREDENTIAL LENGTH Indicates that the credential to create or update presumably exceeds 202 the maximum credential length INFO CREDENTIAL REPEAT Indicates that the credential to create or update presumably is the same as any of 203 t
141. oucher Remitta W Notes Y Input Variables Showing 1 5 6 10 All CURRENCY Currency oftransaction USE_CASE Use Case ID AMOUNT Amountto transfer E Payer Identification Type Payer Identification Payer FI ID Select an entry Payer PI class PavYEE_IDENTIFICATION Payee MSISDN Payee FI ID Select an enty Payee PI class Y Output Variables Showing 1 5 PAYER_FEE The fee for the payer PAYEE_FEE Thefee forthe payee PREAUTH_TXM_ID The Id of the pre Authorisation ten PAYER AMOUNT The amount for the payer PAYER_CURRENCY The currency ofthe payer Follow up States Showing 1 2 OK Select a follow up state Fail Select a follow up state l Select a follow up state Add Follow up Scenario 1 see Continue Voucher Remittance state for example of send voucher remittance flow 142 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Money Mobiliser State Transaction Service Name Continue Voucher Remittance Descriptions Input Variables Output Variables Follow up State OK Follow up State Fail Follow up State DYN Commit the send voucher remittance The send voucher remittance is a two step transaction process involving pre Authorization using Start Voucher remittance state fo
142. ove If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory The pickup code for the Voucher Pickup code Output Variables P The PI Id of the Voucher The Processing Instrument ID of the Voucher The vouchers currency The currency of the voucher The vouchers amount The amount of the voucher Follow up State OK The specified voucher is found and the vouchers attributes are set in the output variables Follow up State Fail Possible reasons Security policies have not been defined for customer yet System error Session not found System error Session has timeout Customer not found Customer is not unique Access to customer is not allowed for the current agent Agent object not found Unexpected error Follow up State DYN O Voucher with the specified Pickup code is not found Brand Mobiliser Development Manual 131 Version 1 2 September 2011 132 Mobiliser Find Remittance Voucher Input Variables Showing 1 3 Select an entry Identification type Identification of the customer overrides session PICKUPCODE The pickup code for the remittance Y Output Variables Showing 1 3 VOUCHER PLID The pild of the Voucher VOUCHER CURRENCY The vouchers curr
143. ow GATHER SEND PRE AUTHORISE SUMMARIZE AND RE VERIFY PIN COMMIT SEND CONFIRMATION MONEY SEND MONEY AGREE ON FEES MONEY TXN ID amp INFORMATION AUTHORIZATION Money Mobiliser CODE FAIL PRE NOT AGREE WITH ABORT WRONG FAIL COMMIT AUTHORIZATION FEES PIN SEND MONEY Send SMS Send SMS Delete Initially gather all the information needed for the send money This may involve several interaction with the customer Once all the information are collected proceed with Pre Authorizing the information including securing the money to be sent During the preauthorization the fees will be calculated and returned in the output variable The best practice is to communicate these fees to the customer and request an agreement to proceed with transaction Typically at this point a re verification of credential i e PIN should be performed This is the last step prior to commit the transaction Once the transaction is committed present the customer with the transaction ID and authorization code returned by this Send Money state Note the Pre Authorization does not need to be rolled back when the Commit is not performed for example when the PIN verification failed The money mobiliser will have the automatic rollback mechanism for non committed authorization Brand Mobiliser Development Manual 137 Version 1 2 September 2011 Money Mobiliser State Transaction Service Charge Fee Descriptions Provides a mechanism to ch
144. pplication flow to wait for the users response By default the wait also known as session timeout lasts for 7 5 minutes 450 seconds Once the session timeout the users response to continue the application flow will not be honored Depending on the setup the user may be presented with a guidance message or main menu The session timeout can be adjusted for each application using the Application Details screen Brand Mobiliser Development Manual Version 1 2 September 2011 49 Scenario 1 Welcome PIN Scenario 2 Menu Options SEND SMS SEND SMS PIN SEND SMS OPTION 1 SUB WELCOME WELCOME AND MENU MENU OPTION 2 PIN OPTION 3 GOTO BANKING MENU 50 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Base State Descriptions Input Variables Set a session variable with a specified string value It is allowable to enter numeric value but the value will be stored as string The consuming state is responsible for validating the type and performing appropriate conversion as needed NOTE there is no error checking in this state Even when the input variables are left empty this state will proceed to the next state The Copy Variable state is the recommended state to use in setting session variable because it performs input validations and it has the fail follow up state for error handling and debugging Variable the variable name to use Value the string value to be set to the va
145. quires to perform its task All input variables may be based on constant values or taken from a variable in the current users session For each input variable there is as follows e Checkbox If the checkbox for an input variable is ticked the text entry field expects the input of a session variable that has to be retrieved If it is not ticked the input value will be constant value as written in the field For example if you want to pass the value of a session variable named CURRENCY write the variable name CURRENCY in the variable entry field and ensure the checkbox is ticked In this case whatever value the session variable CURRENCY has at the point this state is reached is passed into this states processing e Entry Field Field for the input of a variable name or a constant value as determined by the checkbox e Description A short description of the input type The figure below shows an example state that has two mandatory inputs designated with the red mark next to the description These mandatory inputs are being provided by two different session variables i e AMOUNT and CURRENCY The other two inputs are not mandatory but in this instance are supplied as constant values Y Input Variables Showing 1 4 AMOUNT Amount to be formatted CURRENCY The currency of the amount C 10000 Minimum valid amount C 5000000 Wasimum valid amount Figure 6 Example State with Input Parameters Output Parameters Output
146. r loop back to the increment or to exit back to the menu The figure below outlines the first part of this application Mobiliser Counter 4 COUNTER STATE w E a Delete MOBILISER COUNTER APPLICATION SHOW COUNTER v Name Mobiliser Counter State Ta Notes v Input Variables Showing 1 1 tart Ap INDEX variable name Ul v Follow up States Showing 1 2 Ay Fail Show Counter v Target Show Counter Expression hy Assign To Select a follow up state W Add Follow up Figure 35 Mobiliser Counter State Detail The session variable named INDEX is used as the counter variable This variable is dynamically substituted into the text sent back to the user in the next step Brand Mobiliser Development Manual Version 1 2 September 2011 37 Mobiliser Counter APPLICATION DETAILS KevworDs APPLICATION COMPOSER APPLICATION EDITOR Application Actions x A MOBILISER MOBILISER SHOW COUNTER v Name Show Counter ga Hotes COUNTER COUNTER STATE APPLICATION Message Counter INDEX Send back to continue again to re run Start Applicatio MW 60 760 characters Follow up States Showing 1 2 Target Mobiliser Counter State Expression again Assign To Goto Menu Options Target Assign To Expression Select a follow up state
147. rbitrary piece of text The keyword tester will also indicate if there are e matching groups that are not associated with a variable or e if there is a variable that is not matched The following figure shows example expression values for both of these cases Expression and Expression and Assign To ITEM ITEM2 ITEM3 Assign To ITEM1 Text To Test bread and butter Text To Test bread and butter Result Matched Result Matched Variables ITEM1 bread Variables ITEM1 bread ITEM2 butter zno variable gt butter ITEM3 lt no matched group gt Figure 5 Keyword Tester Popup Non Match Groups and Variables To close the keyword tester click on the Cancel button or the popup closer icon on the top right of the popup window To close the keyword tester and to copy any values in the Expression and Assign To fields back into the state editor popup window press the Save button Brand Mobiliser Development Manual Version 1 2 September 2011 2 1 2 Input Output Parameters Some states such as Mobiliser and 3 Party custom states may optionally have input and output parameters The input variables allow these states to receive input from the user or from another state or application The output variables allow these states to save a parameter in session variables that can be used by another state or to another application Input Parameters Input parameters are the information a state re
148. re money is captured at the payment instrument transaction is ready for settlement AuthorizationCancel an open Authorization gets cancelled within the system CaptureCancel an already captured transaction gets cancelled reversed The Use Case of a Money Transaction determines the fees the type of authentication and which velocity checks apply The following diagram provides a highly simplified overview of the financial Transaction centric part of the DB model CUSTOMER PK ID CUSTOMER PAYMENT_INSTRUMENT SE MONEY_TRANSACTION PK DAN MONEY SUB TRANSACTION z FK1 ID_PAYER PK ID_TXN FK3 ID_PAYER_PI ID_REF_TXN ID_TXN Amount Reference FK4 ID_PAYEE PI Use Case Status Error Code Status Error Code All entities are tagged with timestamps and users for their creation and modification 2 4 6 Use Cases The Money Mobiliser transactions are fully configurable and these configurations are captured as business Use Case with unique IDs The use case model contains the following configurable attributes 1 eo sae PP Define the role of the payer for example O Agent 1 TopUp Merchant 2 Money Consumer 3 Money merchant 5 TopUp co user 6 Voucher Issuer 7 Money Voucher agent 8 Money Merchant agent 9 Money Beneficiary 99 System USSD gateway Define the role of the payee Setting the actor is the payee Setting the disabled limit checks and adaptions Y N Setting usage to be public
149. re by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory The ID of the network entry to delete The id of the entry to delete Follow up State OK The network entry is has been deleted successfully Follow up State Fail Possible reasons are e Unsuccessful in deleting the network entry Customer owner does not exist Web service internal error Follow up State DYN 101 Security policies have not been defined for customer yet 1303 System error Session not found 1304 System error Session has timeout 1010 Customer not found 1011 Customer is not unique 1098 Access to customer is not allowed for the current agent 1221 Agent object not found 90 m Brand Mobiliser Development Manu
150. receded by showing the customers a list of invoices with the corresponding Invoice ID see Get Invoice state Usage Scenario 1 The customer replies with the invoice ID to be paid and this ID is assigned to the Invoice ID you want to pay field Brand Mobiliser Development Manual 139 Version 1 2 September 2011 140 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 Money Mobiliser State Transaction Service Name Start Voucher Remittance Descriptions Starts a voucher remittance if the receiving customer does not exist it is created This is a two step transaction process for remittance and should be used in conjunction with the Continue Voucher Remittance state as shown in the Usage Scenario 1 below This is similar to the Pre Authorize Send Money state Input Variables Currency of transaction The currency for the transaction Use Case ID The Use Case ID identifies the type of transaction Amount to transfer The Amount for the transaction Payer Identification Type The identification type of the payer This can be by mobile No by customer ID or by user name Payer Identification The payer is identified here Normally this ID is retrieved through the mobile number so this field can be left blank Payer PI ID The identification of the payment instrument used by the payer Payer PI class The class of the payment instrument used by the
151. rent from most other states in handling the output The OK transition is not supported but the DYN is used instead The DYN reflects the number of items in the returned list However when the list is empty all the output variables will not be populated So the application flow needs to handle empty list separately as shown below Money Mobiliser Variable SEND INVOICE LIST v Input Variables INTEGER if Variable Type Selectan entry Text Case Sensitive Default No Left Variable z Operator 7 Right Variable v Follow up States U NO INVOICE z name J gt Input Variables Send SMS OK No Invoice Fail Send Invoice List gt Output Variables v Follow up States A Fail Error Target Check List size Expression Assign To N Showing 1 5 Showing 1 2 Select a follow up state p Add Follow up Save Scenario 2 the required input field for this state is the Variable name for the ID invoice ID that is really the invoice issuer ID The issuer IDs can vary between customers so the best practice is to get the issuer IDs using the Get Invoice Configuration state that Brand Mobiliser Development Manual Version 1 2 September 2011 125 returns the list of issuers from all the current customers invoices The current implementation of the Get Invoice Configuration state is not
152. riable To set the session variable with the current value of another session variable use the syntax of name where the name is the session variable name to copy from Follow up State OK Follow up state after successful processing The process will always be successful and move to the next state LJ Name Set MAX Allowable Credit Limit Bo Notes Variable CREDIT Value 1000 Follow up States Showing 1 1 A OK Get Customer Information Scenario 1 Create a global variable by setting the session variable CREDIT maximum allowable credit limit to 1000 The global variable can be used multiple times in the application This can also be accomplished using the Copy Variables state There are several mechanisms that session variable is set as described on the followings Session variable can be set in the Follow up States by using the bracket in the Expression field and specify the variable name in the Assign To field All return values from a state are set into the session variables so that they are accessible by the follow up states CAUTION setting an existing session variable will overwrite the value For example if a previous state returned a value in the session variable X and the follow up state set variable X the return value is lost Use the recommended Copy Variable state instead of this state Scenario 2 Set from other session variable Scenario 3 Set text for S
153. rs and as such are not described in this document 5 1 Using the Application Simulator This section describes how to test your applications using the built in application simulator To access the Application Simulator page choose the item on the drop down list titled Actions on the right hand side of the page header Alternatively when viewing the details of an application choose the item on the drop down list titled Application Actions On entry to the application simulator you must enter a test Customer MSISDN and choose an already defined client MSISDN or short code which identifies the workspace under which your application should be created as shown in the figure below If you havent created a client or default MSISDN refer to the Brand Mobiliser User Manual for more information The Customer MSISDN must be entered because Brand Mobiliser uses it to find the session If the application being tested has states that interface with back end systems such as Money Mobiliser for example it may be necessary to use an MSISDN that identifies a customer in those systems Simulation INTERACTIVE APPLICATION Ma s UF 144E vile Interactive Application Customer MSISDN Workspace Short Long 123456 v Code Message Encoding normal v Message Text Send to Brand Mobiliser Send to Customer With Ack Reload Message Log Send Date Direction Sender Application Receiver Message ACK ACK Date Figure 32 Application Simulator Brand Mo
154. s Showing 1 2 7 OK Select a follow up state A Fail Select a follow up state Select a follow up state WI Add Follow up Scenario 1 the Set Primary PI should be preceded by the Get Wallet Menu that lists all the available Pls that the customer can choose from The Get Wallet Menu state returns the selected IS of the PI that can then be set to the Payment Instrument ID of this state So the payment instrument ID is typically not hard coded in this state Brand Mobiliser Development Manual Version 1 2 September 2011 Money Mobiliser State Transaction Service Name Find Remittance Voucher Descriptions searches for a remittance voucher for a customer by the pickup code It returns the vouchers processing instrument ID amount and currency Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed ab
155. s the first state in an application and has no functionality The name of this state is Cash Out Process This state is created automatically when an application is created and cannot be deleted To add a follow up state choose a state from the Follow up Selector Select a follow up state drop down menu in the state editor as shown in the figure below and click on the Add Follow up button This adds a subsequent state When a new State is added the state editor will be refreshed to show the newly added state in the Follow up States List as shown below for the Get Wallet menu 2 m Brand Mobiliser Development Manual E Version 1 2 September 2011 Cash Out Process Follow up States Showing 1 1 Target Get Wallet Menu Assign To Expression Selecta follow up state Figure 1 Example Initial State 2 1 1 Keywords and Variables Some states expect input from the user for example a keyword in order to control the flow between follow up states The moving between states is known as a state transition and can be controlled by matching patterns of text with a supplied keyword The keyword may be supplied by the user in response to a Send SMS state Alternatively keywords may be provided as dynamic outputs from previous state such as Mobiliser or other 3 party custom states These dynamic values are the way external systems can communicate specific context information
156. saction id Brand Mobiliser Development Manual Version 1 2 September 2011 123 Money Mobiliser State Customer Management Descriptions Get the list of invoices that are issued to the customer and stored it in the output variable In the future this state will be replaced with a more sophisticated menu list similar to the Get Wallet state The bill payment capability is modeled as Invoices See Invoice models for detailed discussions Input Variables j Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Status Filter The status of the invoices to be searched for Typically the status ID is as
157. ss can be store with each customer e Privileges to customize the user management user roles and privileges can be attached to customers Together with the scope of each privilege the abilities of each single customer in the Core can be customized e Roles customers can have one or multiple Roles in the Mobiliser system Standard Roles are Money Customer Money Merchant Topup Merchant System Agent Depending on the Role the system stores additional data e Consumer is an extension of the Core Customer entity Beside administrative data the most important extension is the Wallet Brand Mobiliser Development Manual Version 1 2 September 2011 e Merchant is an extension to the Core Customer entity Similar to Consumer the Merchant also can have a Wallet with multiple payment instruments However usually the Merchant only has one payment instrument a bank account which is cleared on a regular basis daily weekly monthly e Wallet stores all available Payment Instruments for a Consumer and a Merchant The customers can prioritize the payment instruments in the Wallet There is a wide support for all kinds of payment instruments Credit Cards Bank Accounts SVA External Accounts Payment instruments can be added to multiple wallets There can be a Limit daily monthly absolute on a customer on a payment instrument and on the combination of both e g a father can assign one of his payment instruments to his son and determine how
158. ssible reasons are e Unable to find the current customer or customers existing identities in the system e Unable to create or update identity e System Error Unexpected Internal Error U Name Je ries v Input Variables Showing 1 2 Identity Type Identification v Follow up States Showing 1 2 OK Select a follow up state v Fail Select a follow up state The default preconfigured IDs are listed in Appendix B5 Additional identity types may be added during customization Please check the customization specification document Usage Scenario 1 typically in the application flow start with presenting the types of identification in menu list form supported by the system or approved by the business There will be one Set Identity state per types IDENTITY TYPES DRIVER LICENSE SET IDENTITY MENU NUMBER DRIVER LICENSE PROCEED Money Mobiliser Send SMS NUMBER PASSPORT Send SMS Delete Brand Mobiliser Development Manual Version 1 2 September 2011 81 82 psa rus Set Identity Driver License ja a v input Variables v Name Driver License Number JE Message Reply with driver license number Showing 1 2 E 0 Identity Type E DRIVER_LIC Identification 32 160 characters i vy Follow up States Showing 1 2 v Follow up States Showing 1 1 Target Set Identity Driver License Le K Success Proceed Expression Assign
159. t a follow up state v Add Follow up C Brand Mobiliser Development Manual 111 Version 1 2 September 2011 Money Mobiliser State Customer Management Set how the customer opts in to receive transaction receipts Input Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Receipt Mode The chosen mode The dropdown list choices are None SMS Email SMS and Email Follow up State OK The opted choice have been updated Follow up State Fail Possible reasons are e Update failure e Web service internal error U v Name New Mobiliser Set Receipt Mode state 8o Notes v Input Var
160. tates Showing 1 2 OK Goto END I5 Fail OK Send SMS state z Select a follow up state A Add Follow up J Save Brand Mobiliser Development Manual Version 1 2 September 2011 Subscriber State Descriptions Add a subscriber and attributes to the selected subscriber list The subscriber MSISDN is retrieved from the session variable MSISDN by default Up to 20 subscribers attributes can be set Input Variables Subscriber Set the subscriber set to use The drop down list presents the subscribers in the workspace Subscriber MSISDN the MSISDN unique key of the subscriber to add Attribute 1 20 The attribute values from the session variables are inserted into the subscriber set Output Variables Total subscriber count in the list the current total number of subscribers in the Subscriber Set after the insert Follow up State OK Successfully add the subscriber to the set Follow up State Fail Error while adding the subscriber and its attribute due to one of the following possible reasons e MSISDN already exist e Non recoverable system error such as database connection etc LJ Name New Add Subscriber state Bol Notes Input Variables Showing 1 5 6 10 11 15 16 20 21 22 All testList v Subscriber Set MSISDN Subscriber MSISDN Attribute 1 Attribute 2 Attribute 3 v Output Variables Showing 1 1 SUBSCRIBER_COUNT Total subcriber countin the list Y Fo
161. the Send Variable Values Not Equal state NOTE the checkbox of variable 2 is not ticked Brand Mobiliser Development Manual Version 1 2 September 2011 55 LJ v Name Compare Variable to String constant Ta E Notes Y Input Variables Showing 1 2 7 ACCOUNT l Name ofvariable 1 T saving o Name of variable 2 v Follow up States Showing 1 2 A OK Equal Proceed next step Iz Fail Not equal or Fail Alternate step B Select a follow up state Add Follow up Scenario 3 in scenario 2 above when the workflow proceeds to the fail follow up state it is possible to determine the cause if needed using the Copy Variable state by copying the ACCOUNT session variable to a dummy session variable If the copy fails then the ACCOUNT does not exist COMPARE EQUAL VARIABLE TO PROCEED NEXT STRING STEP CONSTANT afiabie VALIDATE NOT EQUAL ACCOUNT USING ALTERNATE COPY VARIABLES STEP NOT EXISTS ERROR HANDLING Brand Mobiliser Development Manual Version 1 2 September 2011 56 m Base State Descriptions allows a more advanced comparison of two variables or constant values You can define the variable type for comparison and the operator to be used to compare For text variable comparisons you can additionally choose if the comparison is case sensitive Input Variables Variable Type variable type used in comparison Choices are Text Integ
162. the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Transaction ID transaction id Output Variables Amount The amount of the transaction Currency The currency of the transaction Authcode The authorisation code of the transaction Error Code The error code of the transaction Status Code The status code of the transaction Type The type of the transaction Payee Name The name of the payee of the transaction Payer Name The name of the payer of the transaction Payee ID The ID of the payee of the transaction Payer ID The ID of the payer of the transaction Text The text of the transaction E g reference Payer Fee Amount The fee that is defined for the payer of the transaction Payee Fee Amount The fee that is defined for the payee of the transaction Follow up State OK Success
163. tion a Go To Application type state as highlighted with the only transitioned FROM state being the Show Counter state with a blue surround Mobiliser Counter APPLICATION DETAILS APPLICATION COMPOSER APPLICATION EDITOR Application Actions d SAVE LAYOUT REVERT LAYOUT Gridlines All v Zoom 100 v A MOBILISER COUNTER STATE MOBILISER COUNTER APPLICATION Mon Start Application ey Mobiliser SHOW COUNTER GOTO MENU OPTIONS Delete Send SMS Figure 15 Exit State Highlighted The final figure below shows how the context and dependency highlight helps in a more complex application with many states and overlapping transition lines Brand Mobiliser Development Manual Version 1 2 September 2011 Cash Out Process APPLICATION DETAILS APPLICATION COMPOSER MA Application Actions i SAVELAYOUT EE I Gridlines Al E A NEED PIN CONFIRM TXN CASH OUT SUCCESSFUL ACCOUNT PIN TXN Send SMS 4 ull TOO MANY WRONG PINS WRONG ACCOUNT PIN AGENT SVA LIMIT HIT INSUFFICIENT CONFIRM TAN INSUFFICIENT FUNDS PRE AUTH SVA FUNDS Send SMS Send SMS Send SMS Send SMS Send SMS Send SMS AGENT SVA LIMIT HIT PRE AUTH Send SMS soTo APPLICATION MAIN MENU Figure 16 More Complex Cash Out Application Note Context and Dependency Highlightin
164. trieves all transactions that belong to the customer To limit the results the number of transactions must be specified Example of the transaction list 11 07 17 05 10046966 EUR 10 00 P2P 11 07 17 04 10046938 EUR 10 00 P2P 19 04 16 10 10021857 EUR 200 00 P2P The format is date time TransactionID Currency Amount TransactionName There are three transactions shown above Input Variables Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory Number of transactions the number of the last transactions must be specified to limit the results Use case id of fee to be applied use case id Output Variables The list o
165. uccessfully Follow up State Fail Possible reasons e Registration Error all transactions were rolled back e System Error Web Service internal error Follow up State DYN Brand Mobiliser Development Manual Version 1 2 September 2011 73 New Mobiliser Customer Registration state v Input Variables Showing 1 5 6 10 All Select an entry Identification type Identification of the customer overrides session K CURRENCY 7 le Currency for new customer K COUNTRY Country of new customer K ORGUNIT Organisational unit of new customer K Credit limitto assign to new customer aK K NAME Name of new customer LANGUAGE Language of new customer K PASSPORT_ID Passport no of new customer K KS PIN PIN for new customer v Follow up States Showing 1 2 OK Selecta followup state B A Fail E Select a follow up state Select a follow up state W Add Follow up Notes e This registration should be equivalent to the Consumer Signup web page Usage Scenario 1 Registration should always be preceded by checking whether the consumer already exists Check Identification state using the following pattern a v Name Mobiliser Check Identification state o E Notes v input Variables Showing 1 2 Select an entry i Identification type MOSILISER CONSUMER F j Identification of the customer overrides sessio
166. ulator cccccccccsssscccesecccceneccceenececeaeccessuscesseeeessaeceessaecesseueeeseaesessaaseessansessaes 35 6 jlmipOrting EXDOriIne ADDICATIONS tixccccsssita senders stance r deters eae koe 41 6 1 Export a Single Application ariista aa a a a ai aa a E aa 41 62 Export a GOD Of APPICCATI A E A O 43 63 Importing AD DICATIONS ceiien e n E E EE A EEEE T ERSA 43 OA SOLUICK Stale eM laceS eaa A E E A A T at aie NRE 44 Ac Append States Catal OG nenons a a aa a 47 B Appendix Mobiliser Web Service Lookup ValUGS cccccccsssececesececcescceeeesececeeneceeeegeceetenseeeees 147 Brand Mobiliser Development Manual Version 1 2 September 2011 Principal Author Sybase Mobiliser Group Revision History Version 1 2 September 2011 Version 1 1 March 2011 Brand Mobiliser Development Manual Version 1 2 September 2011 1 Introduction Brand Mobiliser makes it very easy for companies to mobilise all aspects of their businesses including brand awareness CRM mobile banking and financial mobile payment commerce and much more Brand Mobiliser fulfills the increasing demand of mobile customers for more interactions with their mobile applications For partners Brand Mobiliser provides a plug in mechanism to develop components to enrich the Mobile Interactive Application experiences even more allowing integration of any 3 party systems The basis of Brand Mobilisers web interface is the tools to visually compose modif
167. ully transferred KSh AMOUNT_FORMATTED to agent AGENT_CODE Success Ref AUTH_CODE Cash Out LI Press 0 to return to main menu Too Many Times Wrong Account PIN Wrong Account PIN Insufficient Fu Agent SVA Limit Hit The KSh amount you entered exceeds your The KSh amount you entered exceeds your The account PIN you entered was not correct The account PIN you entered was not correct current mobile account balance Please check current mobile account balance Please check Please re enter your PIN for your account and you account has been blocked Please call your current balance and enter a lower KSh your current balance and enter a lower KSh SENDER_ACCOUNT_NUMBER or press 0 to customer support HOTLINE to get more amount or press 0 to return to the main menu amount or press 0 to return to the main menu retin te themainimenil information Press 0 to return to the main menu Main Menu Figure 29 Workflow Schematic for Cash Out Process 32 m Brand Mobiliser Development Manual FY Version 1 2 September 2011 4 3 State Layout The figure below shows the state layout of the Cash Out application as shown in the Application Composer This view is zoomed to 70 to show all the states on one page Sybase 365 Brand Mobiliser e Cid localhost 8080 brand x sVHt6g stRUSIN3Y mPkwig ZA SYBASE 365 Brano Mosiuser Wes Workspace default Logged inas admin Logout MyAccount Help
168. up pre paid recharged remittance view balance view transaction history etc These functionalities are available to the Brand Mobiliser application using the Mobiliser States A good understanding of the Money Mobiliser business domain models enables the application developers in composing advanced mobile Commerce mobile Money or mobile Payment applications The Money Mobiliser platform provides the state of the art money transaction capabilities and ease of integrations to other financial institutions The core is based on a sophisticated and extensible Customer and Transaction models and customizable business and validation rules In additions it is a highly extensible platform based on the dynamic component architecture based on OSGi The following sections provides a high level overview of the Customer and Transaction models that should provide sufficient information in understanding the mobiliser states and how to use them in composing applications 2 4 2 Customer Models Customers are represented through the following features in the Mobiliser e Identifications each customer can be identified through a number of unique identification attributes such as MSISDN username email IMEI IMSI card number passport ID the list is easily extensible e Credentials each customer can have one or multiple credentials such as PIN password etc e Addresses One main address and a number of secondary addresses e g delivery addre
169. user replies to the message with the response again they will see the message again otherwise the application ends My First Application APPLICATION DETAILS APPLICATION COMPOSER Waonle We baie Application Actions bai MY FIRST NEW SEND SMS APPLICATION STATE SAVE LAYOUT REVERT LAYOUT Gridlines Al v Zoom 100 v A LJ v Name New Send SMS state Bol Notes as oa F ii chart Aeeplicasica iiis Message Reply with again to see this again Lill 38 760 c aracters Y Follow up States Showing 1 1 Target My First Application LJ Expression again Assign To My First Application Add Follow up Figure 26 New Link to Existing State Added 3 2 3 Modifying State Configuration All states can be modified by clicking on the state in the layout view to open its state editor popup Some changes that are made on the state editor popup are immediately stored into the database These are e Adding a new follow up state and transition e Adding a transition to an existing state e Removing a transition to an existing state e Moving a transition up or down in the list of follow ups Other changes that are not immediately stored into the database require the user to click on the Save button in order to store the changes are e Change to state name e Change to state encryption option e Change to message text Brand Mobiliser Development Manual 27 Version 1 2 September 20
170. w Mobiliser Counter APPLICATION DETAILS APPLICATION COMPOSER MiB le Vile sine Application Actions SAVE LAYOUT REVERT LAYOUT Gridlines Al v Zoom 70 v a EE MO BILISER MO BILIGER SHOVY COUNTER GOTO MENU COUNTER COUNTER STATE OPTONS e C APPLICATION Figure 10 Example Zoomed Out Application Composer View 3 1 2 Re arranging State Layout On first entry to the Application Composer view any states that have been added to the application are laid out automatically on the canvas Occasionally it is worth to re arrange the layout of the states to get a better view of the transitions between the states particularly when transition lines are overlapping The state icons on the canvas are sensitive to drag and drop into fixed grid positions on the canvas To start a drag e move the mouse over the state icon you want to move e left click on the mouse and hold the click down and e drag to an alternative grid position The figure below shows that when being dragged the state icon will become transparent and target grid positions will be highlighted when the mouse enters that grid area Brand Mobiliser Development Manual Version 1 2 September 2011 17 E Mobiliser Counter APPLICATION DETAILS xevworns APPLICATION COMPOSER APPLICATION EDITOR Application Actions M SAVELAYOUT REVERTLAYOUT E Zoom 100 v A
171. wledgement flag is shown enabling acknowledgement request from the SMPP gateway Scenario 1 static message push campaign Assuming Subscriber set exists SIMPLE PROCESS SEND SMS CAMPAIGN SUBSCRIBER Event Subscriber Delete Start Application GOTO END 64 m Brand Mobiliser Development Manual E Version 1 2 September 2011 v Name Process Subscriber Ww mW v Input Variables Showing 1 1 C Subscribers 7 iS Subscriber Set v Follow up States Showing 1 3 B oK Fail Target Goto END Send SMS Goto END Expression COMPLETE Assign To Select a follow up state M Add Follow up Save Message We are offering a very attractive 1 year CD 10 APY 5 000 min balance Please stop by your local branch immediately J 119 160 characters v Input Variables Showing 1 1 Request SMPP Acknowledgement a Select a follow up state x Add Followup Save Scenario 2 pre staged message push campaign The message was customized at the external system and upload with the subscriber set The message is retrieved from the Attribute 1 and stored in the session variable MESSAGE PUSH PROCESS CUSTOMIZED SUBSCRIBER MESSAGE GOTO END g A ELE Get Staged Message JE F vote Showing 1 2 Input Variables Staged Discount Cam Subscriber Set MSISDN Subscriber MSISDN Output Variables Showing 1 5 6 10 11 15
172. wn Text State Collapser The state editor popup is always displayed on top of the layout view and can take up a large amount of space The state collapser can be used to show and hide the main contents of the state for example to temporarily minimise the amount of space taken up by the state editor popup as shown in the figure below w gt Name Get agent information Bol Notes Select a follow up state v Add Follow up Figure 20 Hidden State Inputs Section This is an optional area and is only shown for certain state types It lists the expected input variables as described in a previous section This section can be closed independently from the whole state or other collapsible areas by clicking the icon next to the Input Variables text The figure below shows this section collapsed w v Name Get agent information 20 Notes gt Input Variables Output Variables Showing 1 5 6 10 11 15 16 18 All Figure 21 Hidden Inputs Variables Paging for Inputs Section The inputs section can contain a varying number of entries depending on the state type Normally only five variables are shown at any one time to minimise the vertical space used by this section Therefore if there are more than five variables you can page through the others by clicking on the relevant page set Clicking the All link will cause all the variables to be displayed which should be used with caution because it may cause
173. y This is a List based state The list is automatically truncated to fit one SMS message If the list is longer than one SMS message an option to see more is provided 9 More or an option to exit the list 0 Back This state facilitates the paging interaction and transition to the follow up state after the customer select an entry from the list Sample menu list 1 EUR 2 USD 0 Back Lets say customer selects 1 the output variables show Key 1 the ID of EUR happens to be 1 Key is not the menu list index Value EUR Input Variables p Identification type The type of customer identification to use The choices are by mobile no MSISDN by customer id or by username The default when leaving the field empty i e Select an entry is the same as the by mobile no option NOTE even though the variable is shown as a required field but leaving it empty will not cause an error Identification of the customer The customer identification value If not set the current customer MSISDN is used NOTE the customer identification value is determined based on the combined setup of the Identification type and Identification of the customer fields listed above If the Identification type is empty or by mobile no the Identification of the customer is optional If the Identification type is by customer id or by username the Identification of the customer is mandatory The payees MSISDN
174. y and test these conversational services known as interactive applications These applications are then fulfilled by the Brand Mobiliser processing engine which allows for high throughput session management for customer interaction with these applications This document describes the steps and parts of the Brand Mobiliser Web Interface called Application Composer that allows development of applications To do this in the following chapters we introduce and describe e States and Applications e The Application Composer state layout view e The Application Composer state editor popup e Acomplete example large application e How to test applications e How to import and export applications between installations 1 1 References 1 Brand Mobiliser User Manual Version 1 2 September 2011 2 Brand Mobiliser State Developers Guide Version 1 2 September 2011 Brand Mobiliser Development Manual Version 1 2 September 2011 2 States and Applications In Brand Mobiliser states are the basic building blocks with a specific capability and they can be linked sequentially to model a process flow called Applications Using the Service Oriented Architecture SOA terminology states are well defined and self contained functionality States capability can be implemented natively stand alone state or it can be a proxy to another web service or aggregated web services that are exposed through an SOA layer service state
175. you can instead add a follow up to an existing state This will result in the applications control of flow going to the point of that existing state The following figure shows the Application Composer view after adding a new Send SMS state My First Application Application Actions v A v Name My First Application g v Follow up States Showing 1 1 APPLICATION EDITOR la ne ar ee tae APPLICATION COMPOSER MY FIRST NEW SEND SMS APPLICATION STATE nd SMS Target New Send SMS state x MW Expression Assign To Send SMS New Add Follow up 26 f Brand Mobiliser Development Manual E Version 1 2 September 2011 Figure 25 New State Added Note After a new state is added it is automatically assigned the name New lt type of state gt state This name is shown in the layout state icon and the follow up section It is recommended that you change the name of the state as soon as possible to something relevant as state names are not unique Note After a new state is added it is also automatically assigned the keyword pattern of match to any and all characters To open the New Send SMS state click on that state in the layout view to highlight it and allow adding of a follow up state from it The figure below shows what the application looks like after a follow up state has been added which is an existing state the initial state This application has been modified so that if the

Download Pdf Manuals

Related Search

Related Contents

Mobotix T25 video IP door station install  Administrador  Harbor Freight Tools 10000 lb. Capacity Weight_Distributing Hitch Product manual  P N E U M A T I C  電力デマンド監視ソフト（形式:SFDND） 取扱説明書 対応 - M  Kenroy Home 10061ORB Instructions / Assembly  User Manual - ADFWeb.com  HP S2 User's Manual  GSM Door User Manual（20150113）  Viewsonic LED LCD VX1932WM-LED  

Copyright © All rights reserved. Failed to retrieve file