Known Issues in Corticon.js 1.4
- Last Updated: March 27, 2024
- Corticon.js
- Version 2.3
- Documentation
| Release Notes for Corticon.js 1.4.0.0 |
| Item | Details | Knowledge Base |
|---|---|---|
| COR-11515 | Importing invalid JSON into a ruletest in Corticon Studio may generate an "Index out of bounds" exception. This can occur when the JSON document is not properly structured JSON. Once corrected, the document can be imported. | |
| COR-11502 | Using the "now" operator in conjunction with the "isSameDate" operator in a rulesheet returns false even if the date component of the DateTime compared to is the current (now) date. | |
| COR-11499 | Within an expression in a
rulesheet, combining the "getMilliseconds" and "toString" operators on a
DateTime attribute will give erroneous behavior. An example expression would
be:
A workaround for this would be to split it into two expressions such as:
|
|
| COR-9093 | Given a vocabulary with CDTs defined of data type Decimal or DateTime, Corticon.js ruletests may indicate a warning when run due to the precision of attribute values. Suppose you defined a CDT of Decimal type to have "1.2" in its enumerated value set. A ruletest that sets this attribute may set the value to "1.200000". This will be flagged as a warning indicating the value is not in the enumerated value set. | |
| COR-9073 | Corticon.js does not support removing the Root entity by rules. Attempting to remove the Root entity will generate a "Circular reference" error when executed. | |
| COR-8667 | Rule statements containing double quotes characters
such as "My Text" are displayed with the characters escaped such as
\\"My Text\\" in rule messages in the Corticon.js
Tester. |
|
| COR-8413 | When deploying Corticon.js rules to Microsoft Azure as
Azure Functions, setting the property
is not logging Corticon rule
messages to the Azure console. The rule messages are only being returned as
part of the response payload. |
|
| COR-7867 | The installation of Corticon.js Studio will write the
exception: to
the post_install.log file. This exception can be ignored. |