A developer uses Workflow Analyzer with the default rules to check if a project follows best practices. In one of the workflows, the Properties of a Click activity is shown in the following exhibit.
Which warning will be shown in the Analyzer output for this activity?
The warning shown in the Analyzer output for this activity will be about using hardcoded delays. 'DelayAfter' has a value of 3000 milliseconds, which is considered a hardcoded delay. It is important to avoid hardcoded values in workflows for maintainability and flexibility. The value should ideally be configurable or derived from a variable.
Since there is a writen value in either Delay Before or After, they are called "HardCord Delay", no matter what's the value of miliseconds.
Hard coded delay
Ans : B
Ans : B
Indeed B
Tested it in studio, B is correct
3000 miliseconds are 3 seconds - is not a hard coded delay value. I think the correct answer here is C
it is a hard-coded value. It is not considered a hard coded value if you put it in config in the constant sheet
Again you misleading people? How on earth 3 seconds HARDCODED value is not hardcoded??? Lol Your answer "Activity Click Calculator button has a default name" -> Click Calculator button is NOT a default name for f*** sake! You should be banned from commenting