Name | Responsible | Description |
---|---|---|
View file history |
Application Consultant |
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
|
Use file explorer |
Application Consultant |
You can use the File explorer to quickly access and view the share as defined for the applicable Azure file storage connector. The File explorer offers limited functionality. You can only view, copy, move, or delete files. |
Solve errors - File actions |
Application Consultant |
Solve the file action errors that occurred during the message run. |
Re-run file actions |
Application Consultant |
On a message, you can use a connector of type Azure file storage. For a Azure file storage connector, you can set up several file actions. These file actions are run in the defined sequence. If one of the file actions fails, the next file actions are not run. After you have solved the errors that caused the file action to fail, you can re-run the file actions of the message.
|
Name | Responsible | Description |
---|---|---|
View file history |
Application Consultant |
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
|
Use file explorer |
Application Consultant |
You can use the File explorer to quickly access and view the share as defined for the applicable Azure file storage connector. The File explorer offers limited functionality. You can only view, copy, move, or delete files. |
Solve errors - File actions |
Application Consultant |
Solve the file action errors that occurred during the message run. |
Re-run file actions |
Application Consultant |
On a message, you can use a connector of type Azure file storage. For a Azure file storage connector, you can set up several file actions. These file actions are run in the defined sequence. If one of the file actions fails, the next file actions are not run. After you have solved the errors that caused the file action to fail, you can re-run the file actions of the message.
|
Related to | Notes |
---|---|
Analyze file history |
  |
Monitor file history |
  |
Monitor file history |
  |
Monitor file history |
  |