TRANSFORMER
Use a Table source to extract data from the BMP system for use in an alternative media, such as a third party tool for consolidation and reconciliation.
A Table source can also be used to loop through different time periods and get the values that were current for that time. See the Repeat periods property below.
You can also use a Table source dynamically set the context in a Web Transformer job, e.g. to where the Action button that starts the job is located.
The data to be extracted must first be isolated into a separate table. The following table types can be referenced for extraction:
When using a Table source to export large amounts of data from BMPto SQL , (e.g. 500,000+ rows), you may experience memory issues. This may cause BMP to run out of memory in environments with low memory. We recommend splitting the export into smaller chunks or increasing memory in Control Center.
Right click in the Transformer design panel and choose Source -> Table source. Now double click the Table source icon to configure it.
General
Name - the name "Table source" is generated automatically but it may be changed
Description - an optional text describing the Table source object
Table resolution - the method to use to find the table name
Reference - refer to the table to use as the source
Table - select the table to use as the source; this can be a table in the Organization, Template, Strategic initiative, or Risk models
Token - use a token expression to refer to the table to use as the source
Table token - enter a token expression that resolves to a table
Table token must refer to a table object, either directly or through a reference property .
Example:
${this.object.ref}, where "ref" is a custom reference property where the user can specify the table that should be used; other token tags may also be used. In this example, ${this.object.ref} will only work if the current context object actually has the "ref" property. If the custom reference property is multi select, only the first element in the reference property will be used.
Context mode - how the context for the Table source should be set
Repeat periods - mark the box to repeat the query once for each period, in order to loop through different time periods and get the values that were current for each period
When Repeat periods is checked the properties Start,
End, and Period type are hidden and the properties Period, Next,
Previous, and Interval become visible.
Period - the period used by Next and Previous to define the total range
Previous - the number of past periods to include
Next - the number of future periods to include
Interval - used to specify the period that each interval in the range should be
Context object - the object table generation should be based on, when the selected table is in the Template model; if nothing is selected the current context object will be used
Examples:
Period = year, Next = 0, Previous = 0, Interval = month - will do a monthly period for
the current year
Period = year, Next = -1, Previous = 1, Interval = month - will do a monthly period
for last year
Period = year, Next = 0, Previous = 10, Interval = year - will do a yearly period for
the last 10 years, including this year
Specified context - use the context specified below (Start, End, Period type, Context object)
Start - date function that determines beginning of period, relative to the current time
End - date function that determines end of period, relative to the current time
Start and End are optional, but if entered they will override the default period property
Period type - the type of period to use as the context of the table
Context object - the object table generation should be based on, when the selected table is in the Template model; if nothing is selected the current context object will be used
Current context - allows the Transformer to run using the context selected in Configuration Studio or on the web
Current context cannot be selected when a project is scheduled.
An error message will appear if this is attempted.
Start - date function that determines beginning of period, relative to the current time
End - date function that determines end of period, relative to the current time
Start and End are optional, but if entered they will override the default period property
Period type - the type of period to use as the context of the table
Context object - the object table generation should be based on, when the table chosen resides in the Template model
Include RID - include the objects' unique repository IDs as the first column in the table, provided the objects displayed are Corporater objects. The intention of including RIDs is for validation and tracking of objects.
The Table source will transform all properties into one of the four types that Transformer supports: number, date, text, or boolean.
Status objects will be converted to the relvalue of the status
Trend objects will be converted to -100 (positive), 0 (unchanged), or 100 (negative)
References will be converted to text
Function properties will be converted to numbers (the calculated value of the function)
etc.
Status, Priority, and Trend with no values will be treated as "empty" strings.
If the table used as source contains multiple columns with the same headings, the names of the second, third, etc. columns will be appended with an underscore, e.g.
"Number property", "Number property_", "Number property__" etc.
Audit
Modified by - the name of the last user to make changes to the object.
Last modified - the date and time when the object was last changed.
Created by - the name of the user who created the object.
Created - the date and time when the object was created.
Version 5.1.2.0
This document contains confidential information. Not to be copied by third parties without written authorization.
© Copyright Corporater AS - All rights reserved.