Trigger in Flow Designer not working propperly with Changes on the table cmdb_ci_appl_sap_hana_db

AndreasRitter
Mega Guru

If the dicovery changes the values of the cmdb_ci_appl_sap_hana_db table, the trigger is not triggered in the Flow Designer.

We have an entry in the "Long SID" column that is identical to the name. The name of the CI is changed to "SAP Hana DB" by the Discovery and the trigger set up in the flow

Trigger: Updated
Table: cmdb_ci_appl_sap_hana_db

Condition:
Updated changes
and
Updated by id Mid_Server_Dev
and
Long_SID is not empty

The previously planned Condition:
Name chaned
and
Long_SIDis not empty

are not triggered when the table is updated by the discovery

If you change a field manually, the trigger is addressed
Does anyone have an idea or a hint as to what the problem might be?

 

Thanks

Andreas

1 ACCEPTED SOLUTION

AndreasRitter
Mega Guru

The solution here is to assign the role with the required rights to the Mid_Server_User.

View solution in original post

3 REPLIES 3

AJ-TechTrek
Giga Sage
Giga Sage

Hi @AndreasRitter ,

 

Refer below, Might help.

 

https://www.servicenow.com/community/now-platform-forum/flow-designer-trigger-of-record-created-not-...

 

https://www.servicenow.com/community/hrsd-forum/flow-designer-trigger-not-being-triggered-correctly/...

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

 

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

AndreasRitter
Mega Guru

Hi @AJ-TechTrek ,

Thank you for your reply.

 

In my case, the trigger was addressed, but the Mid_Server_User could not read the table, so had no read rights. As a result, he could not compare the values of the fields and stopped the flow.

Thanks to Cristina's support, we were able to track down this error.

Thank you again Cristina 🙂

 

AndreasRitter
Mega Guru

The solution here is to assign the role with the required rights to the Mid_Server_User.