Highlights
Expandable Tasks #70
Instead of passing individual arguments per task, you can use the expandable assignment operator *=* (default is =)
to assign all elements from an MDX result to a parameter.
RushTI will then register one task per element in the MDX result set.
So this:
instance="tm1" process="export.actuals" pMonth*=*"{[Period].[Jan],[Period].[Feb],[Period].[Mar]}"
Is equivalent to this:
instance="tm1" process="export.actuals" pMonth=Jan
instance="tm1" process="export.actuals" pMonth=Feb
instance="tm1" process="export.actuals" pMonth=Mar
You can use expandable assignments on more than one parameter per line.
Expandable tasks can be used both in NORM and OPT execution modes.
The Result File #68
With this release, RushTI produces a result file with the below format.
| PID | Process Runs | Process Fails | Start | End | Runtime | Overall Success |
|---|---|---|---|---|---|---|
| 10332 | 8 | 0 | 2023-06-26 15:19:28.778457 | 2023-06-26 15:19:49.160629 | 0:00:20.382172 | True |
Unlike the rushti.log file, the result file is machine-readable and can be consumed with TI after the execution to gain information about the execution.
You can use the result file to raise an alert from TI when not all processes are successful.
By @MariusWirtz
Enhancements
- Added complete task validation before execution by @nicolasbisurgi in #65
- Only trigger execution of a task if predecessors are successful by @avanno in #57
- Read config with utf-8 encoding by @MariusWirtz in #52
- Make
chardetdependency optional by @MariusWirtz in #53 - Handle case that the TI process does not exist in TM1 by @ffonseca-dev in #61
- Handle Python DeprecationWarning by @grandryjn in #62
- Updated readme by @MariusWirtz in #70
- Show PID by default in each log statement by @MariusWirtz in #70
New Contributors
- @avanno made their first contribution in #57
- @ffonseca-dev made their first contribution in #61
- @grandryjn made their first contribution in #62
- @nicolasbisurgi made their first contribution in #65
Full Changelog: 1.3.0...1.4
