This article lists the names that have changed in Cloud Cruiser starting with version 4.0.0. For specific batch XML step and processor names, see New names for batch XML objects.
|assemble||import collections||You are importing the data from one or more collections into a flow where you can perform transformation on them.|
|context variable||system parameter||The system-level and process-level variables that you previously used to insert a value into a job (now into a flow). For example, |
|Data Mapping||Lookup Tables||The item in the navigation pane of the Cloud Cruiser Portal. Part of a consolidation of the terms data mapping, translation, and lookup to the single term lookup.|
|feed configuration||Advanced Configuration||The Advanced Configuration dialog lets you perform data mapping and other tasks that were previously part of a feed configuration bean in batch XML.|
|filter||condition||In transformation processors|
|fixed rate||fixed price||Previously specified when editing a resource. In version 4, specified for a service when editing a rate plan.|
|identifier||dimension||A term more familiar in the business intelligence world|
|job||collection, flow|| |
Previously, getting IT financial data into the Cloud Cruiser database from most data sources involved one batch job to collect the data (called a collection job) and another to transform it and apply charges (called a load job). In version 4, you use an ETL workbook to configure these actions. A collection serves the purpose of a collection job, and each worksheet contains a flow that serves the purpose of a load job.
A collection and a flow each generate a job that you can run from Data > Processing > Scheduling, though you cannot edit their XML. Also, some other product functionality requires jobs. So the concept of a job still applies in version 4, though not as prominently.
|job argument||workbook parameter||The variables that you previously used to insert any value into a job (now into a flow), often passing different values on different runs. For example, |
|load (verb)||publish||A Publish step in a worksheet's flow pushes that flow's data to a schema in the Cloud Cruiser database. The set of data added by one instance of publishing is still called a load.|
|process||workbook||An ETL workbook is the version 4 equivalent of a process, which you previously configured with the |
|resource||measure, service|| |
Previously, a resource served two purposes: it was a single collected amount of usage and it was also the item for which you charged your customers. In version 4, these purposes are separated into different objects:
|revision||effective date range|| |
In a rate plan, the pricing in effect for a given date range. In a lookup table, the source and target values in effect for a given date range.
In the Cloud Cruiser Portal, the Effective Dates menu shows which effective date range is displayed in the rate plan or lookup table below it.
In v3.x, revisions applied to a resource within a rate plan. In version 4, effective date ranges apply to a rate plan. A particular set of effective dates is referred to as an effective date range.
|translation table||lookup table||Part of a consolidation of the terms data mapping, translation, and lookup to the single term lookup.|
|variable rate||unit price||Previously specified when editing a resource. In version 4, specified for a service when editing a rate plan.|