ISAC 3.8
Web
Required Fields (Red Asterix)
Improving the User Interface and Experience by providing a way to highlight required fields through a red asterix. Solution developers will be able to mark components on a form as required and this will enable the feature.
Component Hover/Focus/Disabled State
We’re refreshing the way our UI looks in order to improve the user experience and help the user to know what the current state of the Forms and their components.
Previous | Current |
|---|---|
 Hover |  Hover |
 Focus |  Focus |
 Disabled |  Disabled |
Server
Logging Performance Metrics and ReIndexing ES
Provide metadata to store all the metrics like success, failure, latency etc for all the apis and execution like workflow, timer event, sandbox operation, solution bundle etc. The metadata will provide a reference to get the details of individual executions. This metadata and detailed logs help us to identify application state at any particular time.
Write logs in multiple indexes in Elastic Search storage. Keep only the recent logs in ES and complete logs in S3
More Details: Application Metrics and logging
Logging Performance Metrics and ReIndexing ES
Capture the resource consumption and time taken in executions for further analysis and improve their performance.
Store metrics and log reference for workflows and Timer events.
Integrate monitoring of Sandbox operation, Solution bundle operation and all async executions running in background in the application.
Monitor the current execution as well as check any past execution status and errors if any.
Get the current usage of the system which will help us to decide the infrastructure required with the growing load.
More Details: Workflow Execution Visibility HLD + LLD
Error response from the network node
Introducing a new capability for the network nodes to enable them to return the errorcode on an API Call. This will help the solution developer to be able to configure their workflows to handle not “happy paths”.
To preserve backward compatibility, the new feature will require a boolean flag in the node spec. The default value is false and it will ensure the current behavior is intact.
To see error response, set the returnErrorInfo node spec key to true.
Note: This flag will also require the continueOnError flag to be true
Related features