In-Memory Workflows Impact on UI
In-memory workflows will have the following impact on the User Interface:
Checking Progress in the Event Log
When a workflow is run as in-memory, no event is generated. As a result, you cannot check the event details for operations triggered by an in-memory workflow. If you have configured in-memory workflows that should be persisted on success (saveonsucess flag has been set to true), you can see the result in the Event Log after the workflow has completed executing.
Intermediate event logs are available if the workflow contains a CheckpointWorkflow activity, async subflow, spawn workflow activity, or if the activity suspends. If a workflow errors out, the entire Event Log becomes available for debugging.
If a data source upload or an import operation triggers an in-memory workflow, the checkprogress link (which can be used to track progress in the case of regular workflows) redirects you to an appropriate page with a message that the operation is in-memory.
Checking Progress of Records for Workflows Run In-Memory
If you add a record in-memory, you can check the success of the workflow by searching for a record in the repository or checking the record count in the repository.
Record history does not contain any reference to events processed in-memory. The link to the event is disabled, and the event column shows a message "in- memory”.