This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
DB trigger syntax. Not updating field if it already contains string which is to be added
We have customized DB trigger to deduplicate events from multiple config items into one "master" event. To keep track of the config items for which problem was triggered. We have custom field "TsSMFIDList" where all config items are being added as a string. item1, item2, item3 ..... What we are looking for is when new event is deduplicated, trigger should look into the field and if the item of this new event is not there it should be added into list, or if it is already listed, event would be deduplicated without added second string of the same item. We had already case opened for this TS004603251. Conclusion was that there isn't currently syntax option to iterate through strings in the list.
Current syntax is: (TsSMFID - config item)
if (new.TsSMFID != '') then if (old.TsSMFIDList = '') then set old.TsSMFIDList = old.TsSMFID; end if; if (new.TsSMFID not in (old.TsSMFIDList)) then set old.TsSMFIDList = old.TsSMFIDList + ' ' + new.TsSMFID; end if; --set old.TsSMFID = new.TsSMFID;
Do not place IBM confidential, company confidential, or personal information into any field.