Overview of the process


Look at an example message


Convert into a basic model


Choose a Test Data Catalogue

Model 3 of the variables

Model Template

Contains the Master File Controller & Generate CSV.

Decide which columns you care about (TRUE) in the parsed file


Create Model From File Template



The process to convert message to a template using VIP Executor features

The csv file drives the process

Job 1 - Do an Initial Scan (it’s the XML Create Template panel). Browse and locate the XML file, name it. Execute and now 2 files exist: control_Example.csv and Example1.xml. Copy the files to your working folder.

Open the CSV and see that all of the xml file has been parsed. This Initial Scan, allows you to modify the columns to only pick what you care about, use FALSE to TRUE. In the example ProfitNonFinancial_Income, Taxation_MLA_B1_IncomeStatement, RetainedProfit_MLA_B1_IncomeStatement have been set to TRUE.

Job 2 - Again in Template Management this time select Create Template (it’s the XML Create Template panel). Choose both XML and the CSV files and Execute. This creates a new file called Example1.template which needs to be copied down into your working folder.

Notice these 3 variables ProfitNonFinancial_Income, Taxation_MLA_B1_IncomeStatement, RetainedProfit_MLA_B1_IncomeStatement are now listed, each prefixed with data like so
{{ data.ProfitNonFinancial_Income }}

Job 3 - Now in Model Management choose Create Model From File Template. Browse the pick up filename.template. In the example it’s called Taxation and choose Core Test Date Catalogue from the dropdown options.

A Test Data Catalogue contains the Master File Controller & Generate CSV.

Finally prior to hitting Execute select a folder denstination in the directory hierachiy where to save the file. In this example it’s a folder called Messages.

Now to look at the model

Click Models in the Dashboard menu, [NOTE: in the recent UI version 1.16, Models are located by clicking Explorer in the Dashboard menu] and in the folder Messages select the model Taxation (as previously named). At this point Values can be Assigned to the Varibles in the Test Data pane.

At this point you can trigget the Automation.

at 4:29, automation options are limited to:

Select the Server and Process Name that server. Usually for creating Data or Messages it’ll be Find Test Data Chains and Execute. You’ll have Data but not yet Messages. You’ll see the Data in the .zip download in a folder called GENERAL_Find Test Data Chains > example1.csv.

Now to add in Messages - a post process (this allows you to call a final sweeper step)

Drag a new Start node onto the canvas and keeping it selected then go to the file hierarchy in the Project Explorer pane. In Data Catalogues drop to Core Test Data Catalogue > Master File Controller (String, String) and click Import. Saving then places a Master File Controller Waypoint onto the canvas, then connect it to an End node.

Check and change 2 of the Variable defaults

‘default message format’ - Do this via the Menu Ribbon under Test Data & Automation tab, and click the Variables icon. Click the edit cog of default Message format Variable. The Default Variable needs to be updated to testname{...}.xml.

‘The directory containing the templates’ - pay attention to assure the template path is aligned. THen regenerate.

Note: One additional change needs hande wrangling. In the Test Cases, click the one called MasterFileController. Edit via the cog icon and switch the Path Name to @Post - create messages.

Regenerate again. Execute. This creates a Message file called Repeaters-0.xml. Indiated as 100, 299 and 0.

Refining - make a more sophisticated model

Generate - a Covered set of message variations