Sha256: 51e01ff71493d48b9c083306e1102fe980821b3b6bb66b8f4a5db7bb56df30a0

Contents?: true

Size: 1.07 KB

Versions: 1

Compression:

Stored size: 1.07 KB

Contents

Submit control to second role of CAC

Endpoint request parameters/fields

Field             Data Type  Details
-------------------------------------------------------------------------------------------------
systemId          Integer    [Required] Unique system identifier 
controlAcronym    String     [Required] Control acronym associated with the POA&M Item. NIST SP 800-53 Revision 4 defined.
complianceStatus  String     [Read-Only] Compliance status of the control.
currentStageName  String     [Read-Only] Current role.
currentStage      Integer    [Read-Only] Current step in the Control Approval Chain.
totalStages       Integer    [Read-Only] Total number of steps in Control Approval Chain.
comments*         String     [Conditional] Comments related to package approval chain. 10,000 Characters.

*Comments are not a required field at the first role of the CAC but are required at the second
role of the CAC. Comments cannot exceed 10,000 characters.

Example:

bundle exec exe/emasser post cac add --systemId [value] --controlAcronym [value] --comments [value]

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
emasser-3.4.1 lib/emasser/help/approvalCac_post_mapper.md