Jump to: navigation, search

GVP MCP:msml:record-generatehash
 
(4 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|valid=Choose between: true or false
 
|valid=Choose between: true or false
 
|takeseffect=Immediately/session
 
|takeseffect=Immediately/session
−
|shortdesc=Specifies if MCP should generate the SHA256 hash of the recorded files. The generated hash is used to sign the payloads in case amazon posts are configured to use V4 signature, and it will also be added to the HTCC metadata. When set to 'true', MCP will generate the SHA256 hash of the recorded files. When set to 'false', MCP won't generate the recorded files hash.
+
|shortdesc=Specifies if MCP should generate the SHA256 hash of the recorded files. The generated hash is used to sign the payloads
 +
in case amazon posts are configured to use V4 signature, and it will also be added to the HTCC metadata.
 +
When set to 'true', MCP will generate the SHA256 hash of the recorded files.
 +
When set to 'false', MCP won't generate the recorded files hash.
 +
 
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

Latest revision as of 16:11, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

record.generatehash

Default Value: false
Valid Values: Choose between: true or false
Changes Take Effect: Immediately/session


Specifies if MCP should generate the SHA256 hash of the recorded files. The generated hash is used to sign the payloads in case amazon posts are configured to use V4 signature, and it will also be added to the HTCC metadata. When set to 'true', MCP will generate the SHA256 hash of the recorded files. When set to 'false', MCP won't generate the recorded files hash.

Draft Option

No draft option

This page was last edited on June 29, 2020, at 16:11.
Comments or questions about this documentation? Contact us for support!