Empty Parameter Handling: Introducing EMPTY/NULL like TRUE/FALSE in Decisions

[amitdange15]

Idea: Introducing the Use of EMPTY or NULL STRING in Functions for Handling Empty Parameters, Similar to TRUE or FALSE in Decision Functions.

Description: Context: Many functions encounter limitations when dealing with empty parameters. In such scenarios, it becomes imperative to incorporate the concept of EMPTY or NULL STRING, akin to the presence of TRUE or FALSE in decision functions.

Example: Let's take the case of the "Replace String" function. Often, there's a requirement to substitute a string with nothing or an empty string, but the function doesn't permit this action.

Illustration: Consider the string "ABC-4444333123356" and the desired outcome is "ABC-4444123356".

In the above instance, if the string "ABC-4444333123356" is dynamic, the aforementioned feature would prove exceptionally valuable.

When the option of leaving a field blank is disallowed, the availability of EMPTY or NULL becomes essential to generate the intended output.

In scenarios like the aforementioned example involving the dynamic string "ABC-4444333123356", the functionality described above holds significant utility.

[Karen_Hunter]

Idea added in Product Backlog for Design for prioritization.

BPMD-I-6