control - kcikcicorp.com/wp-content/uploads/2018/04/control_v10.2_release_… · table schema...

The next generation

VERSION 10.2RELEASE ANNOUNCEMENT

kcicorp.com

CONTROL®

CONTROL® 10.2 Release Announcement

© KCI Computing Inc. of 35 March 8, 2018

CONTROL®

10.2 – OVERVIEW ................................................................................................................ 3

ENHANCEMENTS FOR THE INFORMATION NAVIGATOR ............................................................................ 3

Analytic Custom Dimensions ............................................................................................................... 3

PowerPivot Table and PowerPivot Chart view styles .......................................................................... 6

Miscellaneous Enhancements ............................................................................................................... 8

ENHANCEMENTS FOR THE ADMINISTRATOR ............................................................................................. 9

Power Pivot Models .............................................................................................................................. 9

Create a Power Pivot Model ........................................................................................................... 10

Export a Power Pivot Model .......................................................................................................... 13

Microsoft Power BI Desktop Example .......................................................................................... 14

Script: Export Power Pivot Models ................................................................................................ 19

Application Menu: Export Power Pivot Models ............................................................................ 19

Keyword Collections .......................................................................................................................... 22

Mappings Worksheet .......................................................................................................................... 26

Support for Other Languages ............................................................................................................. 28

View Scope Improvements ................................................................................................................. 31

Utility Scripts ...................................................................................................................................... 32

Miscellaneous Enhancements ............................................................................................................. 33

ENHANCEMENTS TO UNIVERSE ............................................................................................................... 34



CONTROL® 10.2 – Overview

This release marks the next stage of evolution on the new release 10 architecture.

The most significant enhancements are:

• The integration of CONTROL data with business intelligence visualization tools, particularly the Power

BI products from Microsoft

• The support of new languages with different character sets, so CONTROL is more accessible to the

non-English speaking marketplace

• Implementation of a new Keyword Collection object, to facilitate the automation and management of

complex processes

Based on feedback from a number of clients who have upgraded to version 10.1, a number of features have been

refined to improve user experience, performance and functionality.

Enhancements for the Information Navigator

Analytic Custom Dimensions

There is now a very simple way to see the data in any computational view as a:

• Change in data

• % Change in data

• % of Group

• % of Total

• % of a defined member

For example, you may want to see monthly data as a percent of the full year, expense sub-totals as a percent of

total expenses, etc.

To accomplish this:

• Open the view and activate the view pane.

• Open the custom dimension node, locate an analytic custom dimension, and drag it to the row, column,

or page edge.

• Alternatively, if there are filters on the analytic custom dimension, select one of the filters.



Analytic custom dimensions work like any other custom dimension:

• You can add one to any computational view, including views that contain other custom dimensions.

• You can place the analytic custom dimension on any non-filter edge and nest it with other dimension-

branches on that edge.

• You can create filters, both permanent and ad hoc, on the dimension.

• You can use all navigation operations – hide, show, drill, etc.

• You can use them with updateable views to get immediate feedback of your changes based on percentage

metrics.

You should be aware of a few subtleties about this feature:

• There can be no more than one analytic custom dimension per view.

• The computations for the members of the analytic custom dimension are performed after the

computations on all other non-custom and custom dimensions.

• There will be some cases where the value of a member of the analytic custom dimension does not make

sense, such as when the base variable is itself a percentage.

With your 10.2 installation or upgrade, KCI will include one or more analytic custom dimensions that you can

use on any computational model, as well as the required supporting level and organization dimension.



You can modify the supplied custom dimensions or build your own. Below is an example definition of an

analytic custom dimension:

Analytic custom dimensions must include the “Base Data” member, which refers to the data values for all the

other dimensional combinations in the view. The other custom members are formulas based on the following

syntax:

Function customMemberID [whichMember ON dimensionID] IN [whichMember ON dimensionID]

The table below includes the current available functions:

Function Used to calculate a

PercentOf Simple ratio



Delta Data change from another member

PercentDelta Percent change from another member

BWDelta Data change from another member with variance convention applied

BWPercentDelta Percent change from another member with variance convention applied

BASE is the default member if you omit the customMemberID.

The table below includes valid definitions for whichMember:

Option Used to

%Group Select the parent member at the next level.

%Total Select the parent member at the highest selected level of the dimension-

branch.

%Prior Select the preceding member at the same level.

levelID memberID Select the specified level ID and member ID

memberID Select the specified member ID (if members are unique)

Note: The “%” used in the options above identify it as a CONTROL parameter and does not indicate a

percentage function.

The dimensionID can be a valid dimension ID or a subclass name (Variable, Organization, Scenario, or Time) or

Organization_n to select the nth organization dimension-branch included in the view.

Any referenced member(s) must be included in one of the view’s filters.

The view will display values for valid formulas; however, the view will display a zero value for any invalid

formulas, for example, a referenced dimension or member is not included in the view.

Any keywords included in the formulas are evaluated at view generation time in the scope of the view’s model.

PowerPivot Table and PowerPivot Chart view styles

With CONTROL version 10.2, you can leverage Power Pivot models, which is a powerful technology introduced

by Microsoft in Excel 2010 and greatly enhanced in Excel 2013 and 2016.

These models allow you to analyze very large multi-dimensional data sets within Excel, add Excel style

calculations, and rapidly navigate the data via pivot tables and charts.



Users who are comfortable with Excel features, or prefer to work off-line, can open any computational, or source

data, view as a Power Pivot model.

You can select these new view options from the view’s Style property:

When you open a view as a Power Pivot table or chart, it creates an Excel Power Pivot model in a new

workbook. The pivot table or chart is on the first worksheet, and the remaining worksheets include the model’s

fact and dimension tables:



CONTROL defines the fields in the table or chart based on the configuration of the dimension-branches in the

view. The levels of the dimension-branches on the view’s Pages edge define the slicers in the pivot table.

You can add, delete, and reorganize the fields in the pivot table. If you enable the Excel Power Pivot add-in, then

you can access and modify the Power Pivot model. Because the Power Pivot model is contained in the workbook,

you can save it as a file, and share it with other non-CONTROL users.

Unlike other view styles, you cannot open a new view window with a Power Pivot style – you must make a copy

of the view and change its style.

Miscellaneous Enhancements

• For any view you have write or limited write access to, you can delete your personal view scope. From the

CONTROL® Navigator tab, in the Views group, select Delete, and click the down arrow on the OK button

and click Delete View Scope:



Enhancements for the Administrator

Power Pivot Models

Power Pivot models make the integration of information managed in CONTROL with Microsoft’s Power BI

technology as simple as possible, so you can create dramatic visualizations, consumable on a desktop, a web

browser, or a mobile device.

Power Pivot models create relational table or view structures that integrate easily not only with Microsoft’s BI

products, but also with many other BI, reporting, visualization, and analytic products from various software

vendors.

For users of Microsoft’s popular Analysis Services (AS) analytic database, CONTROL can create an AS tabular

model used on a standalone basis for dashboards, scorecards, and reports, or integrated with a broader data

warehouse containing AS models from other applications.

Here is how it works:

• Create a Power Pivot model based on a computational, or source data, model; and optionally on a view from

that model. This specifies the data and levels of summarization that will be available to Power BI or other

tools.

• If you do not specify a pre-built view, you can create a view with the filters, branches, etc. that you want.

You can also include Custom dimensions!

• Specify the export options to integrate the CONTROL data with external systems, or use the default values,

which in most cases work fine.

• Use the Export button on the CONTROL® Model ribbon to export the data. You can also create a script to

run the export as a scheduled process, or to run it from your application Menu system.

• Access the data in your favorite BI tool!



Create a Power Pivot Model

Here is a simple example of creating a Power Pivot Model using expense budget data:

1. On the Object Navigation task pane, in the Structure group, click Model, right click Power Pivot, and then

click New.

2. On the New Model dialog, in the Model Templates pane, click Power Pivot Template.

3. In the Properties pane make the following entries and then click OK and Save.

• Name: Sample Expense Power Pivot

• ID: SAMPLEEXPENSEPOWERPIVOT

• Base Model: Expense

• Base View: Expense Analytic Example

• Analysis Services Usage: Exported to AS – CONTROL sourced

• Power Pivot Style: Dimension and Fact Tables (Star Join)

• Power Pivot Anchor: Variable

• Materialization Behavior: Materialize

• AS Database[AS Model]: SampleExpense

• AS Server: Bells



The table below lists the most important properties to modify:

Property Used to

Name Name the Power Pivot model.

ID ID the Power Pivot model.

Base Model Define the source computational or source data model.

Base View Define the source view based on the base model.

Analysis Services

Usage

Specify whether to export the model to an Analysis Services Tabular model, or if it is a

reference to an externally created and maintained AS model, or neither option.

Note: This is a very useful option if you have the required AS infrastructure and

knowledge; however, it is not required for use with Microsoft’s Power BI products, or

for other BI applications.

Power Pivot Style Specify whether you want to see all the data and meta-data in a single table, or organized

into dimension and fact tables (recommended).

Power Pivot Anchor Specify the dimension to anchor the Power Pivot model on – the members of this

dimension will be the fields of the fact table. Specify None to have a single data column

in your fact table.

Materialization

Behavior

Specify whether to create relational tables, views, or virtual tables.

Materialize will create relational tables when you export the CONTROL information.

The other options create relational views of the CONTROL data and meta-data, but there

are limitations to these options due to the dynamic character of CONTROL’s view

generation process.

Materialization Specify how to iterate on parts of the model/view for very large data sets.



Property Used to

Protocol

Table Schema Specify the relational schema where you want the exported table(s) created. If left blank

(default), then the &KCI_RDBMS_Schema keyword defines the schema.

Note: Processes external to CONTROL will access these tables, so you should be

sensitive to your company’s security policies.

Table Name or

Prefix

Specify the name of the relational table(s) that are created. For a star schema, this will be

the prefix and the tables will be named “prefix_Fact, prefix_Dimension1…”

If left blank, then the model and dimension names define the relational table names.

AS Database(AS

Model)

Specify the Analysis Services database and model in the format:

databaseID[modelName]

For CONTROL-Managed AS Power Pivot Model:

• If you leave this field blank, the database will have the same ID and name as the

CONTROL Power Pivot model.

• If you specify only the databaseID, then the AS model will have the same name

as the CONTROL model.

For an externally managed AS database and model:

• You must specify the databaseID.

• If you omit the model name, CONTROL will automatically use the name of the

AS model in that database.

AS Server Specify the name of the server where the Analysis Services tabular instance for this

model resides. For a CONTROL-Managed AS model, if you leave this server name

blank, then the &KCI_ASServer keyword defines the server.

Impersonation Mode Specify how SQL Server Analysis Services will query the supplied CONTROL data.



Export a Power Pivot Model

You can export a Power Pivot model manually, or create a script to export it based on a schedule. To export it

manually edit the Power Pivot model. On the CONTROL® Model ribbon, in the Construction group, click the

arrow on the bottom of the Export button. The table below defines the multiple export commands you can

select:

Export command Used to

Create Create new relational tables/views based on the CONTROL Power Pivot

model.

Create or Replace Create new relational tables/views based on the CONTROL Power Pivot

model, or if the tables/views already exist, then replace the data in the tables.

Reprocess Replace the data in the relational tables only.

Delete and Create Delete the relational tables/views and re-create them based on the CONTROL

Power Pivot model.

Below are the processes that run if you choose the Create or Replace command:

• The base model and view are validated for the user, based on CONTROL’s object and data access

privileges.

• The view meta-data and data are generated according to the view definitions and options, including

currency translation.

• The meta-data and data in the view are manipulated and the dimension and fact tables are written and

populated.

• CONTROL creates SQL data sources, one for each created table, so you can review the relational objects

using standard CONTROL capabilities. When you re-open the Power Pivot model’s edit book after the

export, each data source will have its own tab in the book.

• If the Analysis Services Usage property is set to Exported to AS - CONTROL-sourced, a connection

is made to the Analysis Services Server, and the AS objects are created and processed.

After the export is completed, you can make use of the exported data for visualizations using any of the following

options:

• In Excel, using the tables, or the AS model, as a source for a pivot table or chart, or in Power View

• In CONTROL, creating a Power Pivot Table or Power Pivot Chart style view on the AS model

• In Power BI Desktop, creating and publishing great visualizations

• In any number of other Microsoft or non-Microsoft tools



Microsoft Power BI Desktop Example

In this example, the Microsoft Power BI desktop is used to access our exported data and create some

visualizations. First, you will see how to access the data exported to the AS model, and later how to access the

information from the relational tables in the SQL server database.

SQL Server Analysis Services

1. Open your Power BI Desktop application and click Get Data.

2. Click Database > SQL Server Analysis Services database > Connect.

3. Enter the name of your SQL Server Analysis Services server and database, and click OK.

Note: You can find these in your Power Pivot model properties.



4. Once in the designer, you can easily create interesting visualizations that you can save and share, or publish

to either an on premise server or Microsoft’s Power BI cloud server.

Note the following facts about the exported structures:

• Each view dimension-branch has become a dimension table, and all the levels of its branch are available

for use in a visualization.

• The branch itself has become a “hierarchy” (in the Analysis Services sense), so you can navigate up and

down the levels of detail.

• CONTROL exports its numeric formatting, to the extent possible, to display in Power BI.



• CONTROL exports the member sequence to Power BI.

If you do not export to Analysis Services, but use the base relational tables, not all of these features are preserved.

SQL Server Database

If you do not use SQL Server Analysis Services, then you can get your data from the relational tables in the SQL

Server database.

1. Open your Power BI Desktop application and click Get Data.

2. Click Database > SQL Server database > Connect.

3. Enter you name for your SQL Server and Database.



4. Enter your user credentials for SQL Server.



5. Search for your tables by name or prefix, check the box next to each of them, and then click Load.

6. After the tables load, you can begin creating your visualizations.

Note: The export process will create foreign key relationships between the fact table and the dimension tables, so

you do not need define those in Power BI, if the tables are materialized.



Script: Export Power Pivot Models

To facilitate the periodic refresh of the relational tables and AS models, Export PowerPivot Model is now a step

for action scripts.

Application Menu: Export Power Pivot Models

To make the export easily available from the application menu, Export PowerPivot Model is now an option for a

static or dynamic menu item:



For a deeper discussion of the features available in various Microsoft products, please see the following

references:

Power BI https://powerbi.microsoft.com/en-us/

Analysis Services https://www.microsoft.com/en-us/sql-server/sql-business-intelligence



Excel PowerPivot https://support.office.com/en-us/article/Power-Pivot-Powerful-data-analysis-and-data-

modeling-in-Excel-A9C2C6E2-CC49-4976-A7D7-40896795D045

Note: The export to AS tabular requires SQL Server 2016.

A recommendation for the configuration of the CONTROL environment to support Power BI and SQL

Server Analysis Services is available from KCI in the document titled CONTROL and Microsoft Power

BI.



Keyword Collections

In the course of building large scale, robust applications for a broad spectrum of customers, keywords have

proven to be an invaluable tool for rationalizing and automating those applications. Version 10.2 takes this

feature to the next level by supporting collections of keywords and their corresponding replacement values as a

first-class CONTROL object.

A keyword collection is a succinct mechanism for setting all the keywords needed for the execution of a script,

mapping, or transform; selecting the data presented in a view, book, form, or sheet; or to capture a user’s

preference for a variety of options for their session.

A keyword collection is an ordered list of keywords, their replacement values, their durations (temporary vs.

permanent), optional model and user scopes, and commentary. To facilitate the use of common subsets of

keywords, a keyword collection may include other keyword collections, which simplifies maintenance and

readability.

Keyword collections may be associated with mappings, transforms, and script objects. You can specify the

keyword collection and a specific instance of that collection. When you edit the mapping, transform, or script, all

the keyword replacement values are automatically set for you. This lets you test and modify the object without

having to manually set your keywords. You can also modify the associated keyword collection and selected

instance on a separate tab of the edit book.

Here is an example of a keyword collection:

The keyword collection object view in the edit book makes it easy to copy and paste the contents of a “keyword

sheet” – an Excel spreadsheet-based mechanism that is currently used by many CONTROL customers.



It is very common to have a single process use the same set of keywords, but with a small difference in the

keyword replacement values. For example, an end of year script might set the values of the time period filter

differently from year to year.

To support these scenarios, a keyword collection can have multiple instances, each instance with its own set of

keywords and replacement values. For convenience, each collection has a “default” instance if no instance is

specified.

You can organize your keyword collections by setting the Used With property. For example, you can set this

property for a keyword collection used only with mappings or scripts.

We encourage you to transition your existing applications to use keyword collections wherever possible, as it will

make your application easier to understand and maintain. To help with the transition, there are three mechanisms

to create a keyword collection. You can access them from the Derive button on the Keyword Collections

ribbon:

Command Used to

Active Keywords Harvest all keywords that are temporarily set in the current session.

Script Harvest all keyword settings from a selected script and all its subscripts.

Job Log Harvest all the last set keyword values for a specified job.

You define the keyword collection and instance for a mapping or transform in their object properties:



Note that all existing applications will continue to run without modification, so you can introduce keyword

collections into your process incrementally.

Logging

Keyword collections have a Logging property that indicates how much information to log when the keyword

collection object is used. Possible values for the logging property are:

• None: There will be no logging of the keyword collection usage.

• Minimal: Only a single entry will be logged when the keyword collection is used.

• Normal: Log an entry for each keyword item in the keyword collection when the keyword collection is

used. (Logs the new replacement value for each keyword.)

• Verbose: Log an entry for each keyword item in the keyword collection when the keyword collection is

used and log the previous/current replacement value for the keyword item and the new replacement value for

the keyword item.



For normal and verbose logging, if a keyword collection contains a reference to other keyword collections, the items

in the referenced keyword collections will be logged as well using the specified logging level.



Mappings Worksheet

Every object that you can define with a mapping (models, levels, attributes, hierarchies, codes, custom

dimensions, and datasources) now includes a Mappings worksheet and task pane in the object’s edit book. This

will make it easier for you to review, validate, run, and maintain all the mappings for that object.

The mappings worksheet is generally the second worksheet of the edit book. Below is an example for a

computational model:

In the Mappings for Model task pane, the top pane organizes all the model’s mappings by subclass and

category, for example, Control Feed > JumpStart. The bottom pane includes two tabs: Properties and Target

Filters, which include information for the selected mapping in the top pane.

The mappings worksheet is a view based on the model, filtered by the target filters of the selected mapping. To

see the mapped data, unselect the Sample button on the CONTROL View ribbon.

If the Immediate update box on the task pane is checked, the view will regenerate automatically each time you

select a new mapping. If it is unchecked, you can select different mappings, review and update their properties or

filters, and then click the Update button to see the target data.

You can also add and delete mappings to the model using the controls at the top of the task pane.

If you want to see or change the map associations, edit the source role, or see the error log, right click on the

mapping and click Edit, and the mapping’s edit book will open.

You can also run or test any mapping using the right click menu:



The maximized form of the mappings task pane allows you to review the map associations for each mapping:



Support for Other Languages

This release of CONTROL introduces initial support for foreign language customers and more complete support

of non-Latin characters throughout the product.

Version 10.2 can have the following components presented in any language and character set:

• The object navigation task pane – object group, class, and subclass names

• Object property names and descriptions

• The information navigator ribbons – CONTROL Navigator, CONTROL View, and CONTROL Sheet



Below is an example of the object navigation task pane and CONTROL Navigator ribbon in Polish:



Below is an example of the property grid for a model in Polish:

To support the expanded character set used by non-Latin based languages, CONTROL will now create its

underlying tables with columns that accommodate Unicode, the widely accepted standard for extended character

sets.

CONTROL version 10.2 can accommodate different languages for each user of the same database. You define

this using the &KCI_Language keyword. You can create a user scope with a replacement value based on the

Language Codes located at https://msdn.microsoft.com/en-us/library/hh456380.aspx.

CONTROL supports each language with a set of CONTROL-managed datasources:

Datasource Used to

SystemNamesIn[languageName]

(e.g. SystemNamesInPolish)

Define phrases used in the object navigation task pane, property and

property category names, and phrases used in drop down lists.

PropertyDescriptions[languageID]

(e.g. PropertyDescriptionsPL)

Define the descriptions of each property for all first class objects and sub-

objects.

RibbonPhrasesIn[languageName]

(e.g. RibbonPhrasesInPolish)

Define any label, screen tip, or super tip phrase that appears on the

CONTROL Navigator, CONTROL View, or CONTROL Sheet ribbon.

When requested by a customer or partner, KCI will supply a CONTROL database with these datasources

initialized with automated translations (using the Microsoft Bing translator) for one or more languages. The

customer can refine the translations for terminology, style, and correctness by editing the information in the

datasources with a source data view.



Version 10.2 represents the first stage of our initiative aimed at multi-lingual support, and future releases will

incorporate localization of error messages, other dialogs and task panes, and dynamic translation of meta-data.

View Scope Improvements

While CONTROL’s capability to manage the preferences of a large number of view user scopes has proven

extremely valuable for many clients, the visibility and administration has been a challenge.

In version 10.2, several new improvements make it easier to manage view user scopes. The View Scopes dialog

is accessible from the View Design ribbon when you edit a view or by right clicking the view in the object

navigation pane and selecting Edit View Scopes:

• The Primary Scope is no longer identified. It was seldom used and generated confusion.

• You can now Copy, Paste, or Create and Paste a user scope definition using the three new buttons above

the active user scopes pane. These options update the user scope definitions including property and

dimension-branch assignments, along with their filter and branch specifications.

• The scope properties are now on a second tab on the right-hand side of the dialog, so you can see more

properties and easily navigate among scopes to compare them.

• Context menus include commands, for example, Promote Scope to All User.



Utility Scripts

This new feature makes it simple to provide navigators and administrators access to commonly used maintenance

functions used in your application.

You can designate a script with a utility function for objects or a general utility function. Using an object access

role, you specify which objects the script applies to, and then you can define which user type can use it:

When you open a referenced object’s edit book, the script will be accessible from the appropriate object ribbon,

or on the CONTROL Navigator or CONTROL Developer ribbons:



You could create utility scripts to archive data, analyze relational tables, delete unused hierarchy members,

export CONTROL data to Analysis Services, etc.

KCI will be providing customers with predefined scripts to meet various common customer needs over the next

several release cycles.

Miscellaneous Enhancements

• Level, hierarchy, and filter task panes, as well as, the filter editor will display very large lists and trees

(thousands of members) in the panes and dialogs more quickly and efficiently.

• Transform properties listed under Additional Properties in the transform task pane are now specific to the

selected transform function.

• A new, optional variable filter property is available for Control-Control and Control-External data

mappings that will limit which target organization members are populated based on the presence of non-

zero data for the selected variable members. For example, you may only want prices mapped to

customer/product combinations with non-zero volume.

• The Dynamic Definition book property of FullRollups (Hierarchy(hierarchyID)) will create a loose-leaf

book for the organization hierarchy of a complex organization dimension that facilitates the review and

maintenance of the reporting relationships across multiple branches.

• There is a new option for the dynamic hierarchy rollups view – HierarchyRollups

(CHOOSE,NOEXCELFORMULAS,Branch(Root(levelID)),AllReports) which will construct an optimal

view for maintaining the portion of a hierarchy from the specified root level to its parents, grandparents,

etc.

• There is a new Manifest object view that lets you review or build manifests in an Excel worksheet.

• You can now add additional pages to dynamic books. This could be useful if you wanted to add a sheet

with embedded graphics or instructions to an edit book. You can control the position of these pages with

the new book page property named Property overrides.



• Each book page has an optional Property Overrides property that can be used to specify:

o The position of an added page in a dynamic book (e.g. _Position=Front)

o To override simple properties of a view ([SampleOnly=TRUE] [ReadOnly=TRUE])

• Two new fields (TopScriptID and JobLogID) have been added to the data change log datasource tables

for computational models, which record the source of changes made by executing a script and a batch

job.

• New options were added to dynamic transforms to support Load, Spread, Forecast, Modify, Purge, and

Recalculate functions.

• Several refinements have been implemented to enhance the utility of model data object views,

particularly when the view is defined by a mapping.

• New properties were added to hierarchy and custom dimension object views to show members involved

in circular logic, precedents, and dependents to assist in debugging and performance analysis.

• We made several changes to the task panes in edit books to insure consistency of the options in the

context menus.

• Multiple user scopes for books are no longer supported so all scope related properties have been

removed. All books are available to all users who have an object access privilege for the book.

• Multiple model scopes for transforms are no longer supported. The transform’s model scope specifies

which model or models the transform can be applied to. The model scope may be specified when the

transform is created but may not be changed once it has been saved.

Enhancements to Universe

We made improvements to the visualization capabilities in the Universe:

• You can now undo or redo any changes you make to the canvas.



• Dynamic mappings are denoted by the suffix (Dynamic).

• The ordering of levels in a dimension visualization corresponds to the tree ordering (root level first) in

CONTROL.

• The order of steps in a script visualization is the same as the order of execution.

• The visualization of a transform has been improved to include the referenced model or models.

• The expanded visualization for a mapping now denotes the source and target.

• The visualization of a Keyword Collection is available and includes all contained keyword or keyword

collection objects.

control - kcikcicorp.com/wp-content/uploads/2018/04/control_v10.2_release_… · table schema...

Documents