...
SCL-3458 Resolved issue with unintended moving of temp-table shapes on the canvas of the Business Entity Designer
Description:
We have resolved an issue caused by an issue in the Crainiate .NET Control used to implement the design canvas of the Business Entity Designer.
This issue has caused that in certain situations a temp-table shape on the design canvas has moved slightly to the top left after just clicking without moving the mouse.
The issue has been resolved by releasing a new version of the Business Entity Designer control.
SCL-3505 Fixed an issue with retrieving SmartMessages through the REST endpoint
Description:
We have resolved an issue that the SmartMessage REST endpoint might have not been able to retrieve messages from the Business Entity/Data Access class. The issue was reproducible in combination with updating a SmartMessage record through the web application. Issue was caused by a previous BY-REFERENCE request changing the value of the DatasetHandle property in the Business Entity.
We’ve now implemented a second read-only property with the OriginalDatasetHandle and a method RestoreDatasetHandle that can be used to restore the value of the DatasetHandle property.
New Feature
SCL-3502 Implemented Backend support for adding relations in the Business Entity Designer for the web
Description:
The following endpoint has been implemented for adding relations:
POST /web/BusinessEntityDesigner/Relations/Create
The POST payload consists of a JSON object:
| Code Block | ||
|---|---|---|
| ||
{
"dsBusinessEntity": ...
"parameter": {
"Questions":
[
...
]
}
} |
The response represents the record describing the new relation. The client is expected to use the response for inserting a new relation in the model.
SCL-3503 Implemented Backend support for "Validate Design"
Description:
The following endpoint has been implemented for validating a business entity design:
POST /web/BusinessEntityDesigner/Generator/Validate
The POST payload consists of a JSON object:
| Code Block | ||
|---|---|---|
| ||
{
"dsBusinessEntity": ...
"parameter": {
"ParentTempTableName": "eCustomer",
"ChildTempTableName": "eOrder"
}
} |
The request may return a JSON array of questions raised by the validation. Typically one question is “unanswered”-. Unanswered questions are expected to be presented to the user. After the user has answered the unanswered questions the client is expected to issue the same request and passing the array of questions along with the current model with the follow-on request.
Story
SCL-3501 Implemented REST endpoint to generate Business Entities
Description:
The following endpoint has been implemented for generating a business entity design:
POST /web/BusinessEntityDesigner/Generator/Generate
The POST payload consists of a JSON object:
| Code Block | ||
|---|---|---|
| ||
{ "dsBusinessEntity": ... "parameter": { "Questions": [ ... ] } } |
The request may return a JSON array of questions raised by the validation. Typically one question is “unanswered”. Unanswered questions are expected to be presented to the user. After the user has answered the unanswered questions the client is expected to issue the same request and passing the array of questions along with the current model with the follow-on request.
The request will also return status messages (console output) produced by the generator. The client is expected to visualize them so that the user can see the trace of generated code.