Attestation not created for control, even if control has an attestation associated

[SanjivMeher]

I have few controls for which attestations are not at all getting created.

The control is already associated to the attestation. I notice this happening, when I make some changes to the attestation in our dev environment and then commit those changes to the Test Instance. 

And then it stops working for some reason, even if it was working fine earlier. 

Anybody else had similar issue in the past? Any idea, what could be the reason?

[Notorious BFG]

Hi @Sanjiv Meher - mind if I ask how you're promoting your dev changes into test?  If you're using an update set are you making sure to grab the associated sys_ids for said attestations (if they're different from the baseline)?  If you recreated them in Test but didn't use an update set to move them between instances I'm wondering if those sys_ids are different?  Additionally is it just the Attestations that are not being triggered or is the control itself not being instantiated?  I'd check to make sure that the relevant Control Objective also has "Creates Controls Automatically" is set to TRUE.  Some things to check.  If it is none of those items perhaps we might be able to see a screenshot of the specific behavior?

Best!

Ben F.

ʕﾉಠᴥಠʔﾉ*:･ﾟ✧.   

[SanjivMeher]

Hi @Benjamin "Ben" Forrest 

I moved it using update set. We just have one attestation and it is there in all the instances. I just added a new field to the attestation. 

And it used to create attestation for the end user fine. So I am not sure, what happened after the changes.

The control is instantiated and has Creates Controls Automatically set to TRUE.

Below is a screenshot of the control.

[Phil Swann]

Check the logs. When you Attest, are there any errors generated?

Is Metric Type definitely published? 

Have you removed any questions?

Have you tried to attest with a different Metric Type? With a copy of that existing Metric Type (created in the TEST instance, dif update set!) ?

Check if the Control is listed as an assessable record.

[SanjivMeher]

Check the logs. When you Attest, are there any errors generated?

 No. I dont see any errors in the logs.

Is Metric Type definitely published?

Yes. It is in Published State. 

Have you removed any questions?

No. I have added a new question. But then it works for a control and it doesn't work for another. So I wanted to understand, what is the rootcause of this. Because this has happened more than once after making changes to the attestation. 

I debugged the code and confirm, it enters below function, but not sure, what happens after that. Because I dont have access to AssessmentCreation.

createAssessments: function(typeId, sourceId, userId, groupId) {
return (new SNC.AssessmentCreation()).createAssessments(typeId, sourceId, userId, false, groupId);
},

Have you tried to attest with a different Metric Type? With a copy of that existing Metric Type (created in the TEST instance, dif update set!) ?

With a different want, it will work. But i wanted to find out the rootcause of this. Because if we see this issue in prod, it will be a problem.

Check if the Control is listed as an assessable record.

Yes. It is.