Quantcast
Channel: Discussion Forum > Connect Data Services
Viewing all articles
Browse latest Browse all 2504

CPM not able to destroy incident when saving incident in CPM (1 Comment)

$
0
0

Topic by David Riedel

Content

Hey,

 

I have created a very simple business rule to fire a CPM to delete an incident when the Subject equals "delete" (just for testing), it will be changed into a flag later on.

 

The really strange behavior is, this business rule gets fired and executes the CPM when the user in the console opens an incident with subject "delete" and then saves the incident. --> The incident gets deleted by CPM (lets call this CPM "CPM Delete").

 

In my scenario, though, this is not working: I have created another CPM (lets call it "CPM Update", which saves an incident with the subject "delete". I expect the mentioned business rule above will fire and destroy the incident via the "CPM Delete", after saving the incident in the "CPM Update" --> The incident gets NOT deleted by CPM.

 

For me, this is really a strange behaviour. 

In "CPM Update" I am doing the save like this:

 

$object->Subject = "delete";
$object->save();

RNCPHP\ConnectAPI::commit();

 

Before trying all this stuff of course I just tried simply to destroy the incident directly in the "CPM Update" without doing this what I described above, but this also doesn't work. That's why I wanted to do it like above to do a work around.

$object->destroy();   //destroy is not possible here.. do it in another CPM based on the field set above

 

In the end nothing is working :(

Is there any bug or similar why it's not possible to delete the incident? And why it is working OK when the user updates the incident manually in the system!? That's what so strange for me. User saves INC (working), CPM saves INC (not working) ...

 

Thanks for any help!

Regards

David

 

 

Version

OSvC August 2016, Connect 1.3

Viewing all articles
Browse latest Browse all 2504

Trending Articles