Symantec dlp: incident timezone

[moishce]

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

Added a new parameter "Incidents Time Zone", which allows setting the timezone for incident timestamps.

Must have

• Tests
• Documentation

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
Packs/SymantecDLP/Integrations/SymantecDLPV2
SymantecDLPV2.py	496	141	71%	76–80, 99, 105, 109, 127, 129, 133, 170–171, 175, 184–185, 189, 194–195, 199, 286, 288, 325, 327, 329, 355–357, 393–394, 470–474, 676, 679, 701, 709, 711–713, 724–728, 730–731, 754–757, 760–763, 765, 791–803, 805, 816–817, 833, 876, 941–943, 945, 1115, 1117, 1156, 1173–1183, 1185–1189, 1191–1192, 1194, 1202, 1204, 1206–1211, 1214–1242, 1244–1245
TOTAL	496	141	71%

Tests	Skipped	Failures	Errors	Time
32	0 💤	0 ❌	0 🔥	3.416s ⏱️

[content-bot]

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

[content-bot]

Validate summary
The following errors were thrown as a part of this pr: ST111, DS108.
The following errors can be ignored: DS108.
The following errors cannot be ignored: ST111.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: ST111, DS108.

Verdict: PR can be force merged from validate perspective? ✅