- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2024 07:06 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2024 12:01 AM
The solution here is to assign the role with the required rights to the Mid_Server_User.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2024 11:51 PM
Hi @AndreasRitter ,
Refer below, Might help.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2024 11:59 PM
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 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2024 12:01 AM
The solution here is to assign the role with the required rights to the Mid_Server_User.