Skip to Content

Applies to– 12.2 and Higher version of MII

Summery – The document demonstrate the use of Dynamic Transaction calls in MII 12.2.
The feature adds the object oriented concepts in MII. Even the common piece of object being used in another project can be used.

Author:  Shashank Shrimal

Created On: August 08, 2012.

Table of Content:

Initial Set up
Steps to be followed
Testing the scenario
Conclusion

Initial set up: Having two transactions named “TransactionToBeCalled” and “TrxToBeCalled”   created under the catalog tab.  These two transactions will be called dynamically based on some conditions.

Steps to be followed:

  1. Go to MII workbench and create a new transaction.

  2. Go to action Tab and Select”Dynamic Transaction Call” Action Block from Logic.

3. Define a new Transaction variable or a local Variable (Depend on the condition and requirement).  In       this example I defined a transaction variable “Country” and assign (Hardcode) it a value “US”.

                

         
          

  4.    Double Click the “Dynamic Transaction Call” action Block and Go to Configure link.

              

5.  Pass the transaction name you want to call. This transaction name can be called conditionally using Stringif.
In this example I am going to call two transactions defined in Initial Set up TransactionToBeCalled and TrxToBeCalled.  Calling the transaction on the basis of Country name i.e if the country is US call “TransactionToBeCalled” else call “TrxToBeCalled”.

Note: while calling the transaction name we need to give the full path of the transaction.

            

6.   Update the mapping and close the window.

Testing the scenario:  Insert a new “tracer” action block to trace the output of “Dynamic Transaction call” action Block. 


 

                     

Map the output of “Dynamic_Transaction_calll_0” with the Message of Tracer.
As the Output is not available in the list of available parameters, add the output parameters.

Make a note that this is case Sensitive (Output).

                                         

Final Output in tracer:

                              

Conclusion: The above scenario showcase us the use of Dynamic transaction call. Introduction of Dynamic transaction helps to avoid writing the same code again and again. Thus supports the concept of re usability.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Michael Appleby

    Dynamic Transaction Calls were initially available in 12.1, but your detailed instructions are specific to 12.2.  Is this what you meant at the top of your posting (very nice details, by the way).

    Regards, Mike

    (0) 
    1. Shashank Shrimal Post author

      Thanks Michael,

      I was working on 12.0 and never got a chance to explore the properties and new features in 12.1.

      Working now on 12.2 and  found dynamic call feature is of immense use.

      Regards

      Shashank

      (0) 
      1. Michael Appleby

        It is a feature that many long time MII folks were very happy to see.  Like you say, there is no reason to not reuse code.  However, most of us used conditions or switches to accomplish similar behavior.  It was just not as easy or efficient.

        Regards, Mike

        (0) 

Leave a Reply