- Fix bug: Similar process names caused component context to clear unexpectedly
- Fix bug: Recursive RunProcess call does not map DataIn values correctly
Linx uses an internal cache on some components to speed up execution, e.g. keep Excel open while writing in a loop. When calling another process using the RunProcess component, the cache got cleared unexpectedly if the name of the process that you are calling is a substring of the name of the process that contains the RunProcess component. E.g. process "ClearFiles_Outer" calls process "ClearFiles" using the RunProcess component. Thanks goes to Luka Milutinovic for finding this very obscure error.
The second bug fix relates to the DataIn mappings of a recursive RunProcess. If a process calls itself (using the RunProcess component), the DataIn values were not assigned while calling the process recursively. Thanks goes to Carmen Lawrence for discovering this.
If you have already installed the previous release (4.0.902.4134), it is advised that you upgrade to this version. If you have any additional questions, please do not hesitate to contact us.
Post a Comment