[Security Solution][Detections] Rule Details show 'Activated' text regardless of if Rule is active or disabled

[spong]

The Rule Details Activate switch show the text Activated regardless of if the Rule is active or disabled.

Activated:

Deactivated:

Source:

kibana/x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/details/index.tsx

Lines 675 to 686 in 5f947c2

	<RuleSwitch
	id={rule?.id ?? '-1'}
	isDisabled={
	!isExistingRule ||
	!canEditRuleWithActions(rule, hasActionsPrivileges) ||
	!userHasPermissions(canUserCRUD) ||
	(!hasMlPermissions && !rule?.enabled)
	}
	enabled={isExistingRule && (rule?.enabled ?? false)}
	onChange={handleOnChangeEnabledRule}
	/>
	<EuiFlexItem>{i18n.ACTIVATED_RULE}</EuiFlexItem>

cc @elastic/security-design for intended copy/UX here. Should it switch to Deactivated, animate as Activating.../Deactivating... on state change, or is this text even necessary here?

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[mdefazio]

Deleted my previous comment...misread the suggestion in the issue 🙃 !

[peluja1012]

PR where we decided the current behavior is here #94010 (comment)

[yiyangliu9286]

PR where we decided the current behavior is here #94010 (comment)

The conclusion that has been decided in #94010 as using Activated as the toggle label works based on the EuiSwitch guideline. There is an updated guideline PR specifically talks around when / how to apply label to EuiSwitch.

For fwiw, just an fyi, in the future there might be thinkings around keeping the label consistent in Stack Rules and Connectors table as part of the RAC Rules sharing component to update the label to Enabled instead of Activated... so just wanted to give an fyi for the future label consideration (but "Activated" can work right now).

This view is still a proposed WIP design 👇

[spong]

Thank you for the clarification @peluja1012 and @yiyangliu9286, and apologies for the noise here since this is as designed. Going to close this issue as we'll handle the potential update to Enabled as an output of the re-worked designs. Thanks for the heads up on that @yiyangliu9286! 🙂