Changelog
To administer the Changelog, select .
The extent to which you can configure the Changelog depends on the environment and whether the application is a commercial application or a custom application.
Commercial applications are supplied and installed on your behalf, or are built using Infor d/EPM tools. You can extend commercial applications with your own content, but you cannot change or delete the commercial content or any of the commercial roles. Commercial applications are versioned to enable control of updates.
Custom applications are those that are developed in-house by creating blank applications and then adding content. You can continue to add or remove content from custom applications as required. Custom applications are not updated by Infor, and therefore, there is no versioning of custom applications. For custom applications, the vendor is displayed as two dashes (- -) and the version number as 1.0.0.0 in the Manage Applications dashboard.
These rules apply:
- On premises - custom applications
Changelog is fully configurable for custom applications in on-premises environments.
- Commercial applications
For commercial applications in on-premises or cloud environments, you can only enable or disable Changelog. Some commercial applications, such as the Infor d/EPM business applications (DEPMAPPS), do not support Changelog. In these cases, Changelog cannot be enabled.
- Cloud - custom applications
Changelog is not configurable for custom applications in the cloud.
What Changelog does
One example of a write operation is splashing. When a splashing operation finishes successfully, one or more Changelog entries are recorded atomically to the log file. Information about the operation, such as the value, is logged. In some cases, the values are not logged as delivered but as the computed end value. For example, if you have the value 1 in a specific cell and the delta operation applies a delta value of 2, then the Database Worker writes 3 as the value.
Information on the date, time, user name, cube name, cell address, original value, and new value is included.
These options determine which operations are to be logged:
- All Cubes logs all client operations.
- Cubes with Enabled Transaction Log logs only those operations that are also logged in the transaction log.
- Log Splashing Operations logs splashing operations.
Changes to cell values are not logged if these events occur:
- The entire cube is deleted.
- The dimension element the cell belongs to is deleted.
- The cell type is changed from:
- S to N
- N to C
- S to C
These changes are not logged:
- Attributes
- Dimension
- Cell comments
- Cube structures
- Configuration settings
Logging to file
The string cell limit is up to 1,000,000 bytes.
Logging to database
If the Enable Changelog and Log to Database options are selected, data cell changes are logged to Alealog.txt and to a relational data connection. The content of Alealog.txt is written to the relational server every 10 seconds and is automatically emptied if the insertion to the database is successful.
If there is no table with the name defined in the Table for Cell Changes option in the relational database, one is created when the first write operation happens.
A table for splashing operations is required for the Log Splashing Operations option. If there is no table with the name defined in the Table for Splasher Operations option, one is created when the first write operation happens.
We recommend that you delete Alealog.txt before you select the Log to Database option.
The regional settings of the OLAP database must be compatible with the regional settings of the relational data connection.