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
WAAPI method filter.createOrReplaceFilter not working as they expect, new feature or API method requested
The Customer is using the WAAPI method filter.createOrReplaceFilter.
They have found that if the filter that this is being run on is a dependency for another filter then the file.createOrReplace does not complete.
It has been confirmed that this is working as expected :
This is an expected behavior, if a filter (say FilterA) is dependent on another filter (say FilterB) then you cannot use the createOrModifyFilter method on FilterB. What the method actually does is delete the Filter and then re-create it. Since FilterA depends on FilterB then deleting FilterB fails as it invalidates the relationship.
There is no possibility to verify within one(!) waapi file, if the filter already exists and needs to be modified or if it needs to be created. This is what the name createOrReplaceFilter promises and what the method needs to do.
Instead of simply dropping the filter and creating it again, the method should be implemented as it's named: create the filter, if it's not yet existing, or modify(!) it, if it does. This would really improve the method.
Do not place IBM confidential, company confidential, or personal information into any field.