[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eFindingName.ResourceNameType\u003c/code\u003e enum in the Security Command Center v2 API defines the possible formats for resource names associated with findings.\u003c/p\u003e\n"],["\u003cp\u003eThis enum supports various resource name patterns, including those for folders, organizations, and projects, each with or without a specified location.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eFindingName.ResourceNameType\u003c/code\u003e enum also includes an \u003ccode\u003eUnparsed\u003c/code\u003e option for handling resource names that do not fit any defined patterns.\u003c/p\u003e\n"],["\u003cp\u003eThe supported patterns are \u003ccode\u003efolders/{folder}/sources/{source}/findings/{finding}\u003c/code\u003e, \u003ccode\u003efolders/{folder}/sources/{source}/locations/{location}/findings/{finding}\u003c/code\u003e, \u003ccode\u003eorganizations/{organization}/sources/{source}/findings/{finding}\u003c/code\u003e, \u003ccode\u003eorganizations/{organization}/sources/{source}/locations/{location}/findings/{finding}\u003c/code\u003e, \u003ccode\u003eprojects/{project}/sources/{source}/findings/{finding}\u003c/code\u003e, and \u003ccode\u003eprojects/{project}/sources/{source}/locations/{location}/findings/{finding}\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
