-
Type: User story
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.8
-
Component/s: Automation
UI
I have on the api/automation/doc page a button "Activate the trace for automation" that, when I click on it, enables the trace for all. (This button is displayed only when I am member of administrators group)
And on each chain, I also have a button for activating specifically the trace for that chain, and one for stopping the trace for that chain (both are always displayed, for now)
Behind the scene it must do a post to an operation, so as to be able to leverage the logic in the javascript shell.
Operation spec
Signature
Category: Server Management
Label: Activate Automation trace
accepts: void
produces void
Parameters:
chainId, string, not mandatory
Disable: boolean , default value false
It can be called by a member of the administrators group only
Behavior
- When the operation is called, if there is no value in the chainId, then the trace mode is enabled for all chains, otherwise, it is limited to adding the referenced chain to the list of chains for which the trace is activated.
- If I call it twice for two different chains, then both will be added.
- If I set the Disable parameter to true, then the chain is removed from the list of chains that are debugged (if the current implementation of the traces allows this). If no chain is specified, then trace is completely disabled.
Acceptance:
I can test on the automation/doc page