Package Edition of Nebula Logger
Managed Package
Package Version of Nebula Logger
v4.18
New Bug Summary
This bug seems to have been introduced by salesforce via their UI change in Flows, which has a impact on the nebula logger that i cant seem to find a good fix for.
When i first open a action element in a flow that contains the nebula logger, it looks like this:
(but all inputParameters set to true)
Here i am able to set which inputParamtere the flow should respect, which is good.
However, after 1-2 seconds of load, it jumps to this:
This removes the option to ignore some inputParameters, which leads to System.NullPointerException error when the flow is running that hits the logger action. (as long as the inputParameters is set to true, where a value is not provided)
Note: this is tested on 4.16 aswell, as i think salesforce introduced this UI change at the same times as 4.16 or 4.17.
Package Edition of Nebula Logger
Managed Package
Package Version of Nebula Logger
v4.18
New Bug Summary
This bug seems to have been introduced by salesforce via their UI change in Flows, which has a impact on the nebula logger that i cant seem to find a good fix for.
When i first open a action element in a flow that contains the nebula logger, it looks like this:
(but all inputParameters set to true)
Here i am able to set which inputParamtere the flow should respect, which is good.
However, after 1-2 seconds of load, it jumps to this:
This removes the option to ignore some inputParameters, which leads to System.NullPointerException error when the flow is running that hits the logger action. (as long as the inputParameters is set to true, where a value is not provided)
Note: this is tested on 4.16 aswell, as i think salesforce introduced this UI change at the same times as 4.16 or 4.17.